Introduction to Linked Data Linked Data: what cataloguers need to know #cigld CILIP Cataloguing and Indexing Group (CIG) 25 November 2013 Thomas Meehan tom@aurochs.org @orangeaurochs WHY LEARN ABOUT LINKED DATA Likely to be replacement for MARC (Bibframe) Even if not, is being used to openly publish bibliographic data on the web Being used by eg search engines for semantic results Because cataloguers can take some part in the discussion!

Linked Open Data Data Linked Open Term often taken to means linked open data: Linked: not just text strings, eg hypertext, you can find out more by clicking on links Open: Freely available, licensed, re-usable, re-purposable Data: not just text like HTML which is a marked up document.

linked open DATA 245 00 $a Models for decision : $b   $b a conference under the auspices of the United Kingdom Automation Council organised by the British Computer Society and the Operational Research Society / $c edited by C.M. Berners-Lee. 260 __ London : English Universities Press, 1965. 300 x, 149 p. : ill. ; 23 cm. 504 Includes bibliographical references. 700 1_ Berners-Lee, C. M. Structured Labelled In a recognised format But No links: all the data is in text strings. If you want to find out anything more about these things, you have to get out of the system and search google or the lc authorities site. Arguably, the 700 is a link if you follow a recognised authority scheme. However, it's not an actionable link like an 856 field. You cannot follow the contents of that and find out more. It would, in fact, be hard to construct a URL from that which would go to anything meaningful. You have to get out of the system and search google or the lc authorities site. Not (necessarily) open, or at least easy to get at. Record sharing is common in library cataloguing, but licences are rare and access is through a z39.50 gate or reconstructed web pages. Not data as such but actually a record. None of the bits make sense in isolation. I'll talk a little more about MARC in particular this afternoon. I

LINKED open data.. This is linked in that it's hypertext: you can find out more by clicking on links, although only internally in this case. These links are still aimed at people: difficult for a computer, e.g. a search engine, to assess value. If we look at the source for this…..

…LINKED open data <table border="0" cellpadding="0" cellspacing="0"> <tbody> <tr id="bib-author-row"> <th>Author:</th> <td id="bib-author-cell"> <a href="/search?q=au%3ABerners-Lee%2C+C.+M.&qt=hot_author" title="Search for more by this author">C M Berners-Lee</a>; <a href="/search?q=au%3ABritish+Computer+Society.&qt=hot_author" title="Search for more by this author">British Computer Society.</a>; <a href="/search?q=au%3AInstitution+of+Electrical+Engineers.&qt=hot_author" title="Search for more by this author">Institution of Electrical Engineers.</a>; <a href="/search?q=au%3AOperational+Research+Society.&qt=hot_author" title="Search for more by this author">Operational Research Society.</a? </td> </tr> <tr id="bib-publisher-row"> <th>Publisher:</th> <td id="bib-publisher-cell">London : English Universities Press, [1965]</td> … </table> This is a snippet of the HTML from the previous page, specifically the part listing the authors and the publisher. It is all document based. The table is a means of display only. The th for Author is merely for human readability. The links go to other searches. The publisher information is wholly textual and there is no attempt to even split the elements. Someone like Mr Google could attempt to extract meaning from a page like this but it is unreliable at best. This is the battle that Google has been fighting since it started: how to extract meaning from web pages. This is one reason why Google are keen on linked data! Furthermore, the links that there are merely perform another search. Looking at webpage from the previous slide, you'll also note the copyright notice at the bottom!

linked OPEN data Here is an example of some beautiful linked data but I can't let you see it, search it, or use it. We can discuss terms later. Open means several things: Freely available Licensed to minimise restriction (see the whole open access question). A lot of the Cambridge linked data work revolved around this. Re-usable. If you can't reuse other people's data, the whole idea of linked data falls down, even if you can search it. Re-distributable Re-purposable. You can use it for purposes beyond its original intention. "Open data is information that is available for anyone to use, for any purpose, at no cost. Open data has to have a licence that says it is open data. Without a licence, the data can’t be reused. The licence might also say: that people who use the data must credit whoever is publishing it (this is called attribution) that people who mix the data with other data have to also release the results as open data (this is called share-alike)"—The Open Data Institute.

The Web of Data Use URIs as names for things Use HTTP URIs so that people can look up those names. When someone looks up a URI, provide useful information, using the standards (RDF, SPARQL) Include links to other URIs so that they can discover more things. Tim Berners-Lee (2006) When people use the phrase Linked Data they are actually referring to a Web of Data compared to web of documents, using specific principles, i.e. open data in RDF. URI: URIs can be URLs or URNs. URLs can be http, ftp, etc. URNs are not web actionable HTTP: I.e. over the web. If you don't have http, you cannot easily go and look up more information. Useful info: Basically description, something about it, as on a web page you'd provide information in HTML, in linked data you provide information in RDF (of which more in a second). You can search it using SPARQL (of which more from Owen after lunch) Links: Crucial. You can find out more from other URIs, much as links on a web page allow references and explanations, and further information to be explored. Note: All this is independent of libraries and proceeds rather from the W3C. Linked data is not a formal W3C standard but RDF is, like HTML. The Web of Data is the basis of a semantic web, where meaning as well as text means that computers can make sense of it and act on it. Understanding RDF is important to understanding linked data and that's what I'm going to concentrate on for the rest of this session.

Brideshead Revisited was written by Evelyn Waugh. English sentence Brideshead Revisited was written by Evelyn Waugh. This is a simple English sentence. It has a subject "Brideshead revisited" (the book) It has an object "Evelyn Waugh" It has a predicate "was written by" This is text. How can we turn this into data?

Entities and Relationship Brideshead revisited created by Evelyn Waugh We'll start with dividing it into Entities and relationships, similar to the modelling behind FRBR: In this case, a Work, a Person and a relationship. These are still English text, ambiguous, unidentified, and not linked.

Adding URIs: Brideshead revisited http://id.loc.gov/authorities/names/no97080492 created by Evelyn Waugh Next, we can start to replace textual names of things with URIs. First, we'll give the book a URI. The book Brideshead Revisited is a resource, not in the RDA sense but anything that can be given an identity. We identify it in RDF using a URI.

Adding URIs: Waugh http://id.loc.gov/authorities/names/no97080492 created by http://id.loc.gov/authorities/names/n79049248 Second, the author Evelyn Waugh, the object.

Adding URIs: creator http://id.loc.gov/authorities/names/no97080492 http://purl.org/dc/terms/creator http://id.loc.gov/authorities/names/n79049248 Lastly we can add a URI for the predicate, the relationship. In linked data, even the relationships are established or authorised, not just names and works and subjects. Everything.

RDF Statement <http://id.loc.gov/authorities/names/no97080492> <http://purl.org/dc/terms/creator> <http://id.loc.gov/authorities/names/n79049248> . Third, the creator relationship. This is now a what is called a RDF Triple and, with some punctuation, a valid piece of RDF! However, it is split over three lines. To make this easier to read, especially when there are lots of triples, we can write this out in a different way: Turtle.

RDF (Turtle) @prefix lc_names: <http://id.loc.gov/authorities/names/> . @prefix dc: <http://purl.org/dc/terms/> . lc_names:no97080492 dc:creator lc_names:n79049248 . The first two lines are actually an attempt to make this easier to read. After the word @prefix, it gives a prefix (could be anything: it's just to make it easier to read; lastly is the base of a URI) The triple itself now all fits more easily on one line. This is a Triple, which is the foundation of RDF. It is an assertion (not necessarily a fact). Subject Predicate Object It is important and significant that this lone triple stands alone as a piece of data. It doesn't need to be part of a record as such. We can follow the URIs to find out more. Triples can get quite a lot more complicated. There are ways of saying more nuanced things. In fact, one problem some have with efforts like Bibframe is that the abstraction goes too far. There are also some obvious problems with this: Provenance. Without a record, how can we demonstrate who said this, how reliable it is. There are ways round this and initiatives to do so. Complexity. Redundancy. What if DC and LC shut up shop or change their minds? I promise not to put a lot of XML in this presentation but I will mention triples a lot in this format as they really are fundamental to RDF.

Brideshead Revisited @prefix lc_names: <http://id.loc.gov/authorities/names/> . @prefix lc_languages: <http://id.loc.gov/vocabulary/languages> . @prefix dc: <http://purl.org/dc/terms/> . lc_names:no97080492 dc:creator lc_names:n79049248 ; dc:created "1945" ; dc:extent "1 volume" ; dc:language lc_languages:eng ; dc:title "Brideshead revisited" ; dc:type <http://purl.org/dc/dcmitype/Text> . A fuller description using DCMI terms. Keep thinking of it being in three columns. The subject column is not repeated here because the subject is the same for all the triples. The predicates and objects change. This says…. {run through triples}

Brideshead Revisited @prefix lc_names: <http://id.loc.gov/authorities/names/> . @prefix lc_languages: <http://id.loc.gov/vocabulary/languages/> . @prefix dc: <http://purl.org/dc/terms/> . lc_names:no97080492 dc:creator lc_names:n79049248 ; dc:created "1945" ; dc:extent "1 volume" ; dc:language lc_languages:eng ; dc:title "Brideshead revisited" ; dc:type <http://purl.org/dc/dcmitype/Text> . Now, each of those URIs can of course be followed, and I've picked one out to follow. If we follow the link (or screenshot), we can see what information the URI gives us. As we are using a browser, the URI resolves to a HTML page. If we were a computer programme we could request this page as data. We can do so through the web page too by clicking on one of the links at the bottom. We'll get a page in what is called N Triples.

LC Authorities Linked Data in HTML (screenshot)

LC Authorities Linked Data in N Triples (screenshot)

LC Name Authority for Waugh (excerpt) @prefix lc_names: <http://id.loc.gov/authorities/names/> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix mads: <http://www.loc.gov/mads/rdf/v1#> . @prefix viaf: <http://viaf.org/viaf/sourceID/> . lc_names:n79049248 rdf:type mads:PersonalName ; rdf:type mads:Authority ; mads:authoritativeLabel "Waugh, Evelyn, 1903-1966"@en ; mads:hasExactExternalAuthority viaf:68937142 . This is an excerpt of the LC Name Authority linked data converted to Turtle.

RDF Serialisations N Triples <http://id.loc.gov/authorities/names/n79049248> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.loc.gov/mads/rdf/v1#PersonalName>. <http://id.loc.gov/authorities/names/n79049248> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.loc.gov/mads/rdf/v1#Authority>. <http://id.loc.gov/authorities/names/n79049248> <http://www.loc.gov/mads/rdf/v1#authoritativeLabel> "Waugh, Evelyn, 1903-1966"@en. <http://id.loc.gov/authorities/names/n79049248> <http://www.loc.gov/mads/rdf/v1#hasExactExternalAuthority> <http://viaf.org/viaf/sourceID/68937142>. N Triples: Simple. Easy to see the triples and how many there are. Hard to read each element. Hard to fit it on a page!

RDF Serializations Turtle and N3 @prefix lc_names: <http://id.loc.gov/authorities/names/> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix mads: <http://www.loc.gov/mads/rdf/v1#> . @prefix viaf: <http://viaf.org/viaf/sourceID/> . lc_names:n79049248 rdf:type mads:PersonalName ; rdf:type mads:Authority ; mads:authoritativeLabel "Waugh, Evelyn, 1903-1966"@en ; mads:hasExactExternalAuthority viaf:68937142 . Easy to read and fit on a screen although Longer for snippets due to the prefixes. Also, syntax can get more complicated to cope with abbreviation.

RDF Serialisation RDF/XML <?xml version="1.0"?> <rdf:RDF xmlns:lc_names="http://id.loc.gov/authorities/names/" xmlns:mads="http://www.loc.gov/mads/rdf/v1#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:viaf="http://viaf.org/viaf/sourceID/"> <mads:PersonalName rdf:about="http://id.loc.gov/authorities/names/n79049248"> <rdf:type rdf:resource="http://www.loc.gov/mads/rdf/v1#Authority" /> <mads:authoritativeLabel xml:lang="en">Waugh, Evelyn, 1903-1966</mads:authoritativeLabel> <mads:hasExactExternalAuthority rdf:resource="http://viaf.org/viaf/sourceID/68937142" /> </mads:PersonalName> </rdf:RDF> Originally the only RDF format Often confused with RDF itself Easy for computers to read Very hard for people to read!!

RDF Serialisation JSON-LD { "http://id.loc.gov/authorities/names/n79049248": { "http://www.loc.gov/mads/rdf/v1#hasExactExternalAuthority": [ "type": "uri", "value": "http://viaf.org/viaf/sourceID/68937142" } ], "http://www.w3.org/1999/02/22-rdf-syntax-ns#type": [ "value": "http://www.loc.gov/mads/rdf/v1#PersonalName" }, "value": "http://www.loc.gov/mads/rdf/v1#Authority" "http://www.loc.gov/mads/rdf/v1#authoritativeLabel": [ "lang": "en", "type": "literal", "value": "Waugh, Evelyn, 1903-1966" ] JSON (Javascript Object Notation) is increasingly favoured by programmers. It uses the same data structures as Javascript so can be dropped easily into a programme. It is also easy for other programming languages to use and is not even limited to RDF or even Javascript. {Curly brackets for Objects} [Square brackets for arrays]

RDF Serialisation RDFa <div xmlns="http://www.w3.org/1999/xhtml" prefix=" rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# mads: http://www.loc.gov/mads/rdf/v1# rdfs: http://www.w3.org/2000/01/rdf-schema#" > <div typeof="mads:PersonalName" about="http://id.loc.gov/authorities/names/n79049248"> <div rel="rdf:type" resource="http://www.loc.gov/mads/rdf/v1#Authority"></div> <div property="mads:authoritativeLabel" xml:lang="en" content="Waugh, Evelyn, 1903-1966"></div> <div rel="mads:hasExactExternalAuthority" resource="http://viaf.org/viaf/sourceID/68937142"></div> </div> I.e. for embedding into HTML pages

Microdata, RDFa, Schema.org OCLC Worldcat uses embedded Schema.org: http://www.worldcat.org/oclc/221944758

Schema.org RDFa on Worldcat Linked eg hypertext, you can find out more by clicking on links, although only internally. These links are still aimed at people: difficult for a computer, e.g. a search engine, to assess value. Copyright at the bottom!

Schema.org RDFa on Worldcat

Schema.org RDFa on Worldcat <div xmlns="http://www.w3.org/1999/xhtml" id="microdata" prefix="xml: http://www.w3.org/XML/1998/namespace skos: http://www.w3.org/2004/02/skos/core# library: http://purl.org/library/ gen-ont: http://www.w3.org/2006/gen/ont# pto: http://www.productontology.org/id/ madsrdf: http://www.loc.gov/mads/rdf/v1# void: http://rdfs.org/ns/void# schema: http://schema.org/ oclc: http://www.worldcat.org/oclc/ rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# umbel: http://umbel.org/umbel# bibo: http://purl.org/ontology/bibo/ foaf: http://xmlns.com/foaf/0.1/ cc: http://creativecommons.org/ns# awol: http://bblfish.net/work/atom-owl/2006-06-06/# owl: http://www.w3.org/2002/07/owl# dct: http://purl.org/dc/terms/ blterms: http://www.bl.uk/schemas/bibliographic/blterms# rdfs: http://www.w3.org/2000/01/rdf-schema#"><div resource="http://www.worldcat.org/oclc/221944758" typeof="http://schema.org/Book"><<a href="http://www.worldcat.org/oclc/221944758">http://www.worldcat.org/oclc/221944758</a>><table border="0" cellspacing="0"><tr><td><a href="http://purl.org/library/oclcnum">library:oclcnum</a></td><td>"<span property="library:oclcnum">221944758</span>"</td></tr><tr><td><a href="http://purl.org/library/placeOfPublication">library:placeOfPublication</a></td><td><div property="library:placeOfPublication" typeof="http://schema.org/Place"><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Place" property="rdf:type" resource="http://schema.org/Place">schema:Place</a></td></tr><tr><td><a href="http://schema.org/Place">schema:name</a></td><td>"<span property="schema:name">London</span>"</td></tr></table></div></td></tr><tr><td><a href="http://purl.org/library/placeOfPublication">library:placeOfPublication</a></td><td><div property="library:placeOfPublication" resource="http://id.loc.gov/vocabulary/countries/enk" typeof="http://schema.org/Country"><<a href="http://id.loc.gov/vocabulary/countries/enk">http://id.loc.gov/vocabulary/countries/enk</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Country" property="rdf:type" resource="http://schema.org/Country">schema:Country</a></td></tr></table></div></td></tr><tr><td><a href="http://www.w3.org/2002/07/owl#sameAs">owl:sameAs</a></td><td><<a href="info:oclcnum/221944758" property="owl:sameAs" resource="info:oclcnum/221944758">info:oclcnum/221944758</a>></td></tr><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Book" property="rdf:type" resource="http://schema.org/Book">schema:Book</a></td></tr><tr><td><a href="http://schema.org/Book">schema:about</a></td><td><div property="schema:about" typeof="http://schema.org/Intangible"><table border="0" cellspacing="0"><tr><td><a href="http://www.loc.gov/mads/rdf/v1#isIdentifiedByAuthority">madsrdf:isIdentifiedByAuthority</a></td><td><<a href="http://id.loc.gov/authorities/subjects/sh85042288" property="madsrdf:isIdentifiedByAuthority" resource="http://id.loc.gov/authorities/subjects/sh85042288">http://id.loc.gov/authorities/subjects/sh85042288</a>></td></tr><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Intangible" property="rdf:type" resource="http://schema.org/Intangible">schema:Intangible</a></td></tr><tr><td><a href="http://schema.org/Intangible">schema:name</a></td><td>"<span property="schema:name">Electronic data processing.</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:about</a></td><td><div property="schema:about" resource="http://dewey.info/class/658.4033/" typeof="http://schema.org/Intangible"><<a href="http://dewey.info/class/658.4033/">http://dewey.info/class/658.4033/</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Intangible" property="rdf:type" resource="http://schema.org/Intangible">schema:Intangible</a></td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:about</a></td><td><div property="schema:about" resource="http://id.worldcat.org/fast/1081992" typeof="http://schema.org/Intangible"><<a href="http://id.worldcat.org/fast/1081992">http://id.worldcat.org/fast/1081992</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Intangible" property="rdf:type" resource="http://schema.org/Intangible">schema:Intangible</a></td></tr><tr><td><a href="http://schema.org/Intangible">schema:name</a></td><td>"<span property="schema:name">Public administration--Data processing</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:about</a></td><td><div property="schema:about" resource="http://id.worldcat.org/fast/906956" typeof="http://schema.org/Intangible"><<a href="http://id.worldcat.org/fast/906956">http://id.worldcat.org/fast/906956</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Intangible" property="rdf:type" resource="http://schema.org/Intangible">schema:Intangible</a></td></tr><tr><td><a href="http://schema.org/Intangible">schema:name</a></td><td>"<span property="schema:name">Electronic data processing</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:about</a></td><td><div property="schema:about" typeof="http://schema.org/Intangible"><table border="0" cellspacing="0"><tr><td><a href="http://www.loc.gov/mads/rdf/v1#isIdentifiedByAuthority">madsrdf:isIdentifiedByAuthority</a></td><td><<a href="http://id.loc.gov/authorities/subjects/sh2008110032" property="madsrdf:isIdentifiedByAuthority" resource="http://id.loc.gov/authorities/subjects/sh2008110032">http://id.loc.gov/authorities/subjects/sh2008110032</a>></td></tr><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Intangible" property="rdf:type" resource="http://schema.org/Intangible">schema:Intangible</a></td></tr><tr><td><a href="http://schema.org/Intangible">schema:name</a></td><td>"<span property="schema:name">Public administration--Data processing.</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:contributor</a></td><td><div property="schema:contributor" resource="http://viaf.org/viaf/149407214" typeof="http://schema.org/Organization"><<a href="http://viaf.org/viaf/149407214">http://viaf.org/viaf/149407214</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.loc.gov/mads/rdf/v1#isIdentifiedByAuthority">madsrdf:isIdentifiedByAuthority</a></td><td><<a href="http://id.loc.gov/authorities/names/n79056431" property="madsrdf:isIdentifiedByAuthority" resource="http://id.loc.gov/authorities/names/n79056431">http://id.loc.gov/authorities/names/n79056431</a>></td></tr><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Organization" property="rdf:type" resource="http://schema.org/Organization">schema:Organization</a></td></tr><tr><td><a href="http://schema.org/Organization">schema:name</a></td><td>"<span property="schema:name">British Computer Society.</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:contributor</a></td><td><div property="schema:contributor" resource="http://viaf.org/viaf/130073090" typeof="http://schema.org/Organization"><<a href="http://viaf.org/viaf/130073090">http://viaf.org/viaf/130073090</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.loc.gov/mads/rdf/v1#isIdentifiedByAuthority">madsrdf:isIdentifiedByAuthority</a></td><td><<a href="http://id.loc.gov/authorities/names/n85076053" property="madsrdf:isIdentifiedByAuthority" resource="http://id.loc.gov/authorities/names/n85076053">http://id.loc.gov/authorities/names/n85076053</a>></td></tr><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Organization" property="rdf:type" resource="http://schema.org/Organization">schema:Organization</a></td></tr><tr><td><a href="http://schema.org/Organization">schema:name</a></td><td>"<span property="schema:name">Operational Research Society.</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:contributor</a></td><td><div property="schema:contributor" resource="http://viaf.org/viaf/137135158" typeof="http://schema.org/Organization"><<a href="http://viaf.org/viaf/137135158">http://viaf.org/viaf/137135158</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.loc.gov/mads/rdf/v1#isIdentifiedByAuthority">madsrdf:isIdentifiedByAuthority</a></td><td><<a href="http://id.loc.gov/authorities/names/n79063901" property="madsrdf:isIdentifiedByAuthority" resource="http://id.loc.gov/authorities/names/n79063901">http://id.loc.gov/authorities/names/n79063901</a>></td></tr><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Organization" property="rdf:type" resource="http://schema.org/Organization">schema:Organization</a></td></tr><tr><td><a href="http://schema.org/Organization">schema:name</a></td><td>"<span property="schema:name">Institution of Electrical Engineers.</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:contributor</a></td><td><div property="schema:contributor" resource="http://viaf.org/viaf/36887201" typeof="http://schema.org/Person"><<a href="http://viaf.org/viaf/36887201">http://viaf.org/viaf/36887201</a>><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Person" property="rdf:type" resource="http://schema.org/Person">schema:Person</a></td></tr><tr><td><a href="http://www.w3.org/2000/01/rdf-schema#label">rdfs:label</a></td><td>"<span property="rdfs:label">Berners-Lee, C. M.</span>"</td></tr></table></div></td></tr><tr><td><a href="http://schema.org/Book">schema:datePublished</a></td><td>"<span property="schema:datePublished">1965</span>"</td></tr><tr><td><a href="http://schema.org/Book">schema:inLanguage</a></td><td>"<span property="schema:inLanguage">en</span>"</td></tr><tr><td><a href="http://schema.org/Book">schema:name</a></td><td>"<span property="schema:name">Models for decision : a conference under the auspices of the United Kingdom Automation Council organised by the British Computer Society and the Operational Research Society</span>"</td></tr><tr><td><a href="http://schema.org/Book">schema:numberOfPages</a></td><td>"<span property="schema:numberOfPages">149</span>"</td></tr><tr><td><a href="http://schema.org/Book">schema:publisher</a></td><td><div property="schema:publisher" typeof="http://schema.org/Organization"><table border="0" cellspacing="0"><tr><td><a href="http://www.w3.org/TR/rdf-schema/#ch_type">rdf:type</a></td><td><a href="http://schema.org/Organization" property="rdf:type" resource="http://schema.org/Organization">schema:Organization</a></td></tr><tr><td><a href="http://schema.org/Organization">schema:name</a></td><td>"<span property="schema:name">English Universities Press</span>"</td></tr></table></div></td></tr></table></div></div> Here are the N-triples…

Worldcat Schema.org data for a book @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix schema: <http://schema.org/> . @prefix worldcat: <http://www.worldcat.org/oclc/> . @prefix library: <http://purl.org/library/> . @prefix viaf: <http://viaf.org/viaf/> . @prefix lc_authorities: <http://id.loc.gov/authorities/names/> . @prefix mads: <http://www.loc.gov/mads/rdf/v1#> . worldcat:221944758 rdf:type schema:Book; library:oclcnum "221944758"; schema:name "Models for decision : a conference under the auspices of the United Kingdom Automation Council organised by the British Computer Society and the Operational Research Society"; library:placeOfPublication _:1; schema:publisher _:4 . schema:datePublished "[1965]"; schema:numberOfPages "149"; schema:contributor viaf:149407214; schema:contributor viaf:130073090; schema:contributor viaf:137135158; schema:contributor viaf:36887201; _:1 rdf:type schema:Place; schema:name "London :" . _:4 rdf:type schema:Organization; schema:name "English Universities Press" . viaf:149407214 madsrdf:isIdentifiedByAuthority lc_authorities:n79056431; schema:name "British Computer Society." . viaf:130073090 madsrdf:isIdentifiedByAuthority lc_authorities:n85076053; schema:name "Operational Research Society." . viaf:137135158 madsrdf:isIdentifiedByAuthority lc_authorities:n79063901; schema:name "Institution of Electrical Engineers." . viaf:36887201 rdf:type schema:Person; schema:name "Berners-Lee, C. M." . (http://www.aurochs.org/rdfv/rdfv.html : click Get Sample Data (OCLC)) The viaf id for Berners-Lee is followable: click on it and you get the VIAF record. Choose the RDF view to see the underlying RDF.

Lots of Ways To Do It @prefix schema: <http://schema.org/> . @prefix dc: <http://purl.org/dc/terms/> . @prefix viaf: <http://viaf.org/viaf/> . @prefix rda_roles: <http://rdvocab.info/roles/> . @prefix cam: <http://data.lib.cam.ac.uk/id/entity/> . @prefix bnb_person: <http://bnb.data.bl.uk/id/person/> . @prefix foaf: <http://xmlns.com/foaf/spec/#> . example:book0001 dc:creator cam:cambrdgedb_eeacef63d900c2acffc3daa400f3d4e4 . example:book0001 dc:creator bnb_person:WaughEvelyn1903-1966 . example:book0001 schema:creator viaf:68937142 . example:book0001 rda_roles:creator viaf:68937142 . example:book0001 dc:creator lc_names:n79049248 . example:book0001 dc:creator _:bnode001 . _:bnode001 foaf:name "Waugh, Evelyn, 1903-1966" . example:book0001 example:author example:author0001 These triples or pairs of triples all make the same assertion but use different vocabularies and different uris to do so. The sixth one asserts the creator's name as a string. This can't be done directly as dc:creator needs a resource- a URI- not a literal string.

Blank Nodes @prefix lc_names: <http://id.loc.gov/authorities/names/> . @prefix dc: <http://purl.org/dc/terms/> . @prefix foaf: <http://xmlns.com/foaf/spec/#> . lc_names:no97080492 dc:creator _:bnode01 . _:bnode01 a foaf:Person . _:bnode01 foaf:name "Evelyn Waugh" . lc_names:no97080492 dc:creator [ a foaf:Person ; foaf:name "Evelyn Waugh" ] .

Introduction to Linked Data @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix dc: <http://purl.org/dc/terms/> . @prefix bibo: <http://purl.org/ontology/bibo/> . cigld_intro dc:creator _:bnode001 ; dc:created "2013" ; dc:title "Introduction to Linked Data" ; bibo:Series "Linked data: what cataloguers need to know" . _:bnode001 a foaf:person ; foaf:name "Thomas Meehan" ; foaf:mbox <tom@aurochs.org> ; foaf:account _:bnode002 . _:bnode002 a foaf:OnlineAccount ; foaf:accountServiceHomepage "https://twitter.com/" ; foaf:accountName "@orangeaurochs" .

References Worldcat record for Models for decision / C. Berners-Lee. http://www.worldcat.org/title/models-for-decision-a-conference-under-the-auspices-of-the-united-kingdom-automation-council-organised-by-the-british-computer-society-and-the-operational-research-society/oclc/221944758 What is open data? / The Open Data Institute. http://theodi.org/guides/what-open-data Linked Data : design issues / Tim Berners-Lee. http://www.w3.org/DesignIssues/LinkedData