4. Linked Data
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those
names
3. When someone looks up a URI, provide useful
information, using the standards
4. Include links to other URIs so that they can
5. Tom Scott of the BBC:
”...for those considering the
Linked Data approach we’d say
that 95% of the work is work you
should be doing just to build for
the (non-semantic) web. Get the
fundamentals right and the leap
to the Semantic Web is really
7. What do I have to do?
• What are the important things to describe?
• Identifiers
• Regular web pages AND data
• Describe the things using RDF
• Links to other data and datasets
• Licensing
• Publish (flat files, CMS, DB-backed web
app...)
8. Icing on the cake
• SPARQL end point
• Data dumps
• Semantic site map
• Update feed
16. Linked Data
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those
names
3. When someone looks up a URI, provide useful
information, using the standards
4. Include links to other URIs so that they can
17. Identifiers
Assign a URI in your domain:
http://www.bbc.co.uk/nature/species/
European_Water_Vole#species
http://data.ordnancesurvey.co.uk/id/50kGazetteer/
155254
http://education.data.gov.uk/id/school/135524
23. “When someone looks up a URI,
provide useful information, using
the standards”
24. Content negotiation
Tell me about .../id/school/1234 and I want it in RDF
you need to look up .../doc/school/1234.rdf (“303 See Other”)
OK, give me .../doc/school/1234.rdf
RDF document
25. Describe things with
RDF
@prefix owl: <http://www.w3.org/2002/07/owl#> .
Thing @prefix bbc: <http://www.bbc.co.uk/nature/species/> .
@prefix wo: <http://purl.org/ontology/wo> .
bbc:European_Water_Vole
owl:sameAs <http://dbpedia.org/resource/European_Water_Vole> ;
wo:order <http://www.bbc.co.uk/nature/order/Rodent#order> .
Attributes and values
26. Describe things with
RDF
• Existing common ontologies - collections of
properties and types
• FOAF, Dublin Core, SKOS, Admingeo,
Geonames...
• Or make up your own
27. Linked Data
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those
names
3. When someone looks up a URI, provide useful
information, using the standards
4. Include links to other URIs so that they can