+ Recogito annotation platform
Amy added http://recogito.pelagios.org/rhiaro to https://rhiaro.co.uk/bookmarks/
+ Recogito annotation platform
Amy added http://recogito.pelagios.org/rhiaro to https://rhiaro.co.uk/bookmarks/
🔁 https://twitter.com/philarcher1/status/778515246109646848
Amy shared https://twitter.com/philarcher1/status/778515246109646848
Vocabulary development and maintenance, W3C namespace control. 15:30 today, room 1.04 at TPAC2016- Phil
Oops on behalf of JSON-LD I apologise to github users @context @graph @value @id @type etc...
+ http://bblfish.net/tmp/2011/05/09/
Amy added http://bblfish.net/tmp/2011/05/09/ to https://rhiaro.co.uk/bookmarks/
+ http://kidehen.blogspot.cz/2015/09/what-happened-to-semantic-web.html
Amy added http://kidehen.blogspot.cz/2015/09/what-happened-to-semantic-web.html to https://rhiaro.co.uk/bookmarks/
Amy added http://rdfa.info/ to https://rhiaro.co.uk/bookmarks/
+ http://dig.csail.mit.edu/2009/presbrey/UAP.pdf
Amy added http://dig.csail.mit.edu/2009/presbrey/UAP.pdf to https://rhiaro.co.uk/bookmarks/
+ http://www.lsrn.org/semweb/rdfpost.html
Amy added http://www.lsrn.org/semweb/rdfpost.html to https://rhiaro.co.uk/bookmarks/
+ https://linkeddata.github.io/SoLiD/
Amy added https://linkeddata.github.io/SoLiD/ to https://rhiaro.co.uk/bookmarks/
Finally you can get my blog post content in a number of different formats. You'll notice alternative URLs (noted currently as 'Permalink') in the metadata section of a normal view of a post. Hit this up with no Accept header, and you'll get neat markdown (which is what I authored it in; the 'source', as it were).
Browsers automatically send Accept: text/html, in which case they are redirected to the rendered HTML version of the post you're probably reading now. But here are some alternatives you can try:
curl http://blog.rhiaro.co.uk/micropub-test-> plain markdown.
curl -H "Accept: application/json" http://blog.rhiaro.co.uk/micropub-testbecause there's obviously not enough JSON in the world. Note this isn't correct JSON-LD yet. I'll sort that out another time.
curl -H "Accept: text/turtle" http://blog.rhiaro.co.uk/micropub-testOhemgee! RDF! It's what you've all been waiting for, I know.
For those of you who like angular brackets, you could try:
curl -H "Accept: rdf/xml" http://blog.rhiaro.co.uk/micropub-testBriefly discussed with Tantek, Aaron and Bret at IWC Cambridge and on IRC about how a micropub client could fetch post content for editing. Many people aren't editing raw HTML as it's presented on the page, but maybe markdown or some other syntax, so a client needs to be able to discover this (the 'source') to present it to be edited. Now if someone makes their client check a post for a rel="source" or shoots off a request with Accept: text/plain (less likely, since static sites can't do conneg) then they'll get my markdown directly (uh, when I actually put rel="source" in my HTML, which I haven't yet).
As a related aside, I also return source="markdown" if a micropub client asks my endpoint q=source.
I'm serializing the microformats2 vocabulary into RDF; repo on github.
Disclaimer: This post is (not necessarily coherant) notes as I go along.
Useful notes by Tom Morris about mf2 to RDF mapping on the microformats wiki. I updated the namespace to use the one suggested there (http://microformats.org/profile/).
Everything starting with h- looks like it's a class. Typically RDF classes are capitalised so this makes me cringe, but I'll cope.
Woah, there are a lot of properties. Seventy unique properties. I didn't realise. On the wiki most don't have a description, many are duplicated in the list, and none of them seem to have their own description page (and thus no URIs to refer to them with). Pasting them into a spreadsheet was the quickest way to de-dup and alphabetise them. Now I'm working through one at a time, adding descriptions and mapping them to existing properties in FOAF (because many are obvious), VCard (because many (all?) are derived from this), ActivityStreams 2.0 (because SocialWebWG) and hesitantly Dublin Core and SIOC. Where they map to something well-described in RDF, I don't bother with rdfs:comment and domain and range of their own, but I'll add for those with no good sameAs mappings.
dt-reviewed same as dt-published? If not, why do reviews get special treatment with regards to differentiation between when they're written and published, and nothing else does?e-content? Couldn't find one on the wiki, so made one up that is compatible with AS2.0 content, with additional caveat about including markup, which is explicit on the mf2 wiki: "The contents of something like a post, including markup and embedded elements."e-description and e-instructions sub-properties of e-content?I keep getting caught out by AS2.0 terms that are in the JSON-LD document but are actually deprecated (the JSON-LD contains no information other than property and class names and sometimes types; I have to remember to check the written docs). Eg. as2:author -> as2:attributedTo.
category. Am I missing something? Oh wait, tag will do it.p-description from p-summary?p-education should contain a nested h-card (of school and location). Doesn't that mean it should be an e- or have I misunderstood that completely?p-education is "an education h-calendar event" but h-calendar doesn't exist, it's h-event. Probably just a typo? Ditto p-experience.name property for Actors (only displayName). Interesting.label 'new in vCard4' but vCard4 says it's deprecated, and in any case was for address labels, so not sure what use this is in mf2.p-note for specifically?p-reviewer not just p-author?sex and gender-identity are part of it, but all I can see is hasGender.AS2.0 has rating but it's explicitly defined as "a non-negative decimal number between 0.0 and 5.0 (inclusive) with one decimal place of precision". MF2 says it's a number between 1 and 5. I think even less specification is better, as ratings come in come in many forms. Anyway, because I'm not venturing into SKOS, I'm owl:sameAsing them for the time being.
Update: Dropped all domains and ranges because all properties in microformats2 are actually global.
Last modified:
Same as last year, but with twice as many students. Tirelessly answered student emails, made a few supplementary materials, mostly got the feedback sent on time; was nominated for a Best Teaching Award ^^ Oh, also organised a hands-on workshop this year, because I generally disagree with lectures.
Worked with an amazing team to boost the profits of Mr. Falafel in Shepherd's Bush and on the side helped with modelling the world as the BBC sees it, and learnt all of the corners to cut and ideologies to give up in order to develop linked data applications to improve the lives of people who don't know/care about linked data.
Key achievements include:
owl:sameAs David Bowie.So Slog'd got stuck for a little while because the fast, nice-looking, somewhat magical SPARQL endpoint provided by ARC2 stopped working for no discernable reason.
I thought I'd try leaving it alone for a few weeks to see if it started working again by itself, but alas, it has not.
Everything is fine until I try to query for a specific predicate. (Specific objects or subjects are fine). The query runs, it just returns no results. I know the data is in there, because I can get it out with less specific queries. Also because I can see it all in the MySQL database on which it is based. When I left it, it was working fine.
I'm going to kill the database and set it up again.
I did this by - and oh, it was joyous - going into the database settings and appending '2' to the name of the database. I then reloaded the endpoint page, and it set everything up by itself :)
I inserted two triples, and successfully queried for a specific prefix. So, it works. I wonder what will happen if I dump all my old data back in there? (I validated the raw file with all the triples in RDF/XML, and they're fine).
I inserted the rest the rest: LOAD <path/to/rdf.rdf> INTO <>
Ran a test query, aaaand... it's fine.
So what the hell was wrong with my other database? Perhaps I'll never know...
I had an idea for a tiny wee project to do with quantified self. More on that later.
Because I'm trying to use linked data for everything, for reasons beyond the scope of this post, the first thing I did was sketch out the data I need to store in a graph structure. I need to record emotions, so I did a quick search for ontologies that represent emotions, figuring psychologists and the like must have been at this for years already.
Sure enough I found a few, but the most convincing one, the HUMAINE Emotion Annotation & Representation Language (EARL) is in XML rather than OWL.
Yay! Time to convert a well structured and useful dataset into RDF. Always a Good Thing.
EARL comes as many files, and goes beyond what I need. But it's not huge, and with a little effort (and looking some stuff on Wikipedia) I think I can understand what's going on enough to convert the lot.
Note: There's apparently a lot of disagreement about terms and stuff in this area. Not something I'm invested in, so I'm just going to roll with this XML.
There are:
Emotional occurrences can have all of the above as properties, as well as probability and intensity. Complex emotional occurrences have times, and contain a minimum of two emotional occurrences with the above properties.
The terms are all taken from various different psychological experiments or schools of thought. There are alternative versions of some of these things from something called AIBO. Arbitrarily I'm ignoring everything prefixed AIBO for now.
I'm going through the files and writing everything relevant out, then drawing it as a graph.
First juncture: do I use all the attributes (like the list of 55 emotions) as properties (as they are demonstrated in the original XML) or use classes? Properties seems messy, and feels less extensible, even though technically I suppose it's not.
Maybe they should be properties. Except the categories, they all (or at least most) have corresponding DBPedia entries that it would be stupid not to take advantage of. But the dimensions, regulation and appraisal might be better suited to being properties, otherwise I'm having pointless identifiers or blank nodes everywhere. And nobody wants that.
I adjusted the Samples thing a bit, mostly to simplify it, and I may have got it wrong, but I think it makes sense.
Then I typed it all into WebProtege. As a result, I think quite a few things are overspecified. What do you think? Check it out: http://vocab.amy.so/earl.
Last modified:
Marked courseworks where undergrad/taught masters students had to convert an open dataset to linked data and query it and stuff. It was pretty fun. Also helped students understand the course materials by email.
Didn't have much success talking to the Dydra SPARQL endpoint yesterday. I was briefly worried as there are no docs describing how to write back to the SPARQL endpoint, so I thought that was write-off at once, but then I found a blog post from 2011 about how that has been introduced. Just not documented yet apparently.
But to start with, I imported some test triples using the Web interface, into dydra.com/rhiaro/about-me and tried to read them back.
With ARC2, along the lines of:
include_once("ARC2/ARC2.php");
$config = array(
'remote_store_endpoint' => 'http://dydra.com/rhiaro/about-me/sparql'
);
$store = ARC2::getRemoteStore($config);
$query = 'select * where {?s ?p ?o} limit 20';
$rows = $store->query($query, 'rows');But all I got back was an empty array. I tried with with the DBPedia endpoint, which fell over a couple of times, but I got results... except... they were different from the results I got when I queried the endpoint directly through their interface. They seemed sort of metadata-y, rather than actual triples from the store. But it's hard to tell.
So I had a go with Python's RDFLib to try to figure out who had the problem.
import rdflib
rdflib.plugin.register('sparql', rdflib.query.Processor, 'rdfextras.sparql.processor', 'Processor')
rdflib.plugin.register('sparql', rdflib.query.Result, 'rdfextras.sparql.query', 'SPARQLQueryResult')
g = rdflib.Graph()
query = """
SELECT *
FROM
WHERE {
?s ?p ?o .
}Limit 10
"""
for row in g.query(query):
print row And with that I got some triples... but not from the triplestore. It parsed, I presume, whatever semantic markup it could find in the page itself, the page you see when you visit dydra.com/rhiaro/about-me/sparql. Eg.
(rdflib.term.URIRef(u'https://s3.amazonaws.com/public.dydra.com/stylesheets/style.css?1337867890'),
rdflib.term.URIRef(u'http://www.w3.org/1999/xhtml/vocab#stylesheet'),
rdflib.term.URIRef(u'http://dydra.com/rhiaro/about-me/sparql'))Do I have to send an accept header? Surely RDFLib is supposed to take care of that for me... Whatever.
If that's how you're going to play it, I'll just make the request with CURL directly. (I used Python's Requests because the Web says it's nicer than urllib2):
import requests
import rdflib
q = "select * where {?s ?p ?o}"
url = "http://dydra.com/rhiaro/about-me/sparql"
p = {'query': q}
h = {'Accept': 'application/json'}
r = requests.get(url, params=p, headers=h)
print r.textBoom! Triples! Better yet... the ones in the triplestore! By default (with no Accept header set) they come through as RDF/XML, and it won't give me Turtle, so JSON seems to be the nicest looking option. That doesn't really matter though, as nobody really needs to look at it.
I guess I'll try CURL with PHP for Slog'd, and just parse it with ARC2. It seems a shame that ARC2's remote endpoint querying didn't Just Work with Dydra, but I don't have the time or energy to try to figure out why right now.
Then I need to figure out if I can write to it or not. If I can't... In the name of progressing, I'll have to ditch it and use ARC2's built in MySQL-based triplestore.
Because I want to understand exactly what Dyrda is giving back to me, I wanted to quickly parse the results and use them like I should be able to use a graph.
The XML that Dydra is returning is not straightforward RDF/XML that RDFLib can just understand. It's a 'SPARQL Result. It looks like this:
https://rhiaro.co.uk/about#me
http://xmlns.com/foaf/0.1/homepage
https://rhiaro.co.uk
...etc So later I either have to work out how to make RDFLib understand this, or make RDFLib understand the JSON alternative. I really don't want to have to write a custom parser to deal with it.
Turns out it's as simple as using CONSTRUCT instead of SELECT in the query. Rookie mistake? I don't know. I feel like RDFLib ought to be able to handle the SPARQL results format somehow though.
Last modified:
Thinking about the options for hosting the Linked Data for Slog'd implementations, and also thinking about hosting personal and shared Linked Data in general, and Linked Data authored by an Agent who isn't the subject, because this is likely to be appropriate in a lot if cases.
For Slog'd it's a bit easier, because people setting up a Slog'd implementation would have a bit of knowledge / interest in the Semantic Web and data ownership, in theory. Such people will probably have already a unique URI (like a WebID) or the ability to set one up. The data is also most likely to be authored by the subject.
I'm thinking about it in broader terms because (PhD-related) I want content creators (who don't know or care about the Semantic Web) to publish Linked Data about their involvement in the creation of different digital media and online creative works.
Where does this data live, to give them absolute and definitive control over it? If they can author data about anyone and anything (which of course, they can) how do we verify what they say when there are no conflicts, or deal with conflicts that arise? Is content attribution data stored in a giant graph that anyone can update?
How do we handle IDs? Is there a central service for generating URIs for people who can't use their own domains (like the MyProfile demo)? How do we link - or not - multiple identities of the same person, according to what they want other people to know?
Last modified:
What I want to create is a solution to allow the Every(wo)man to publish their blog (/whatever) 'on' the Semantic Web.
The Every(wo)man uses a cheap, perhaps archaically run, shared hosting environment, and has little to no control over what is installed there. The most accessible server-side language is PHP. The most likely default databases are MySQL. Files are uploaded using FTP (typically through a client with a GUI) or a web interface like cPanel. Maybe they'd like to change to a new host who would allow them to, say, experiment with Python and CouchDB, but they just renewed their two-year contract, and besides the customer service with their current account is really good, and they have so much content knocking about on that server space now, and they definitely can't afford to be paying for duplicate at the moment. And they also can't be bothered with the faff of remembering how to work with Heroku or something everytime they sit down to tinker, not to mention the worry that their limited understanding of such a system will suddenly start incurring costs.
Disclaimer: Previous paragraph may be based on actual events.
The solution for running a triplestore from shared hosting is the PHP ARC2 library, which can, wonderfully, drag a MySQL database kicking and screaming into the SPARQL world.
But I didn't really want to just use MySQL. It is a terribly practical, but inpure solution. I want a graph database, damnit, with a SPARQL endpoint, and I want somewhere for it to live that I don't have to pay extra for.
So what else is there?
I want to experiment with CouchDB anyway, so I checked that out. There are hosted instances - like Iris Couch that look pretty easy to deal with. Nobody seems to have optimised it as a triplestore though, so setting up a SPARQL endpoint and proper inferencing and stuff may be a bit beyond me right now.
There are lots of hosted triplestores I guess, but they all seem to be about 'Big Data'. I came across Dydra ages ago and signed up for their Beta and forgot about it. Then they called me at my office to find out what I wanted to use the Beta for. I bumbled that conversation because I'd forgotten what it even was (I think they introduced themselves with a different name, too), and I was generally dealing with the fact they'd actively Googled me (I asked) to get my office phone number (the University helpfully posts these on their website) which I had not given to them. And if I had figured out what was going on in time, I'm positive they would not have given me a Beta account for "maybe tinkering a bit to see what it does when I have time at some indeterminable point in the future".
UPDATE: The day after writing this I got an email with an invite code for the Dydra beta, and no personal contact from them. Crazy coincidence. I'll give it a shot.
Anyway, I'm sure I've come across hosted 4store services that didn't try to step on your toes about what you used it for, but I can't find any now.
Talis looks mega promising, aside from having an outdated site with broken links, but they're still allocating stores on a request basis. Grumble.
In the interests of moving forwards, I'm going to go with ARC2 and MySQL. But I'll make sure it's all modularised and stuff so it's easy to switch out the store for something else in the future.
Last modified:
It's easy to see why not many people do. I say not many, because I'm sure there are people using the various RDF Drupal or Wordpress plugin. But I don't really know if they count, because that's really just people annotating their content for SEO purposes, and maybe a bit of interlinking with DBPedia to let visitors find out a bit more about topics of interest.
But what I'm really talking about is the whole blog running from a triplestore, with a publicly accessible SPARQL endpoint.
All the publicly accessible SPARQL endpoints I can find are big 'useful' datasets that people might want to mash up with other things. Archives of data. Not live or frequently updated stuff. Certainly not the contents and metadata of a personal blog.
So what's the point?
There's not a lot else 'on' the Semantic Web to tap into. There's no hidden Semantic Blogosphere that would yield great worth if I could only tap into it. There are no smart agents traversing the Semantic Web and aggregating interesting blog content for intelligent readers (are there?).
And there never will be, if nobody publishes their content this way.
So I suppose I'd better get on with it.
My point is, it's easy to see why nobody does.
Last modified:
Tell Me Scotland publish public notices for things like traffic, planning permissions... And they have a SPARQL endpoint!
I'm hacking around with the ultimate goal of creating an interface that allows people to generate a GeoRSS feed for a particular area. Ally of GreenerLeith suggested this, so that they can use this to feed into their own apps. A stage beyond that is to smoosh the whole lot into a Wordpress plugin, to make it accessible to anyone (who uses WP).
So far I've got the notices on an OpenStreetMap. I haven't had a whole lot of time, but will make more soon.
I'm using the PHP library ARC2 to deal with the linked data.
NB. the TMS endpoint is, at the moment, flaky at best. I think they're working on this.
Last modified:
Yesterday I unexpectedly read two whole papers about ontology development methodologies. They were open in tabs I don't remember opening, but presumably did so during our weekly Ontologies With A View meeting last Friday. There are still a bunch more tabs open with papers or articles about the same thing, so maybe I'll read those later..
The notes are here more or less as I scribbled them down whilst reading, and I haven't expanded with any analysis or discussion as of yet.
Notes in purple are things I intend/need to investigate further; colour-coding is just for me, really.
Jean Vincent Fonou-Dombeu & Magda Husiman (2011) Combining Ontology Development Methodologies **and Semantic Web Platforms for E-government **Domain Ontology Development. International Journal of Web & Semantic Technology (IJWesT) Vol.2, No.2, April 2011
Says there's not sufficient practical research around existing technologies or ontology development guidelines that would allow non-experts in e-government domain to make ontologies.
Uses Protege and Jena to convert to OWL and RDF
Paper's goal is to produce guidelines for e-government developers to create semantic content AND strengthen adoption of Semantic Web technologies in governments (particularly developing countries).
Outlines RDF, OWL, Protege and Jena (described as leading platforms; mentions other platforms: WebODE, OntoEdit, KAON1, Sesame).
Very critical of other literature; either ontologies have been produced but no practical information given; they've been developed with proprietary platforms; or they're only conceptual and don't say how they could actually be constructed with existing technologies. other studies have not focused on a methodological approach, which means nothing is easily repeatable.
Detailed comparative studies of methodologies in:
Case study: Ontology for monitoring development projects in developing countries (OntoDPM)
Create with Protege:
*Mike Uschold and Martin King (1995) **Towards a Methodology for Building Ontologies. Workshop on Basic Ontological Issues in Knowledge Sharing, IJCAI-95.
Steps:
build ontology
Documentation
Case Study
Categorisation is fundamental to the human condition (Lakoff)
GENERAL
^
BASIC -> primary with respect to knowledge organisation
v
SPECIFIC
Last modified: