Downloaded 60 times
Uploaded byRichard Wallis
Identifying The Benefit of Linked Data
The document discusses the benefits of linked data and provides instructions for creating linked data. It describes how linked data allows for connecting and sharing information on the web through the use of URIs and RDF triples. The key steps outlined for creating linked data include establishing the entities in your data, giving them URIs, describing each entity, and linking to authoritative hubs. Schema.org is presented as a vocabulary that is widely used and can be extended for specific domains.
More Related Content
Similar to Identifying The Benefit of Linked Data
Identifying The Benefit of Linked Data
- 1. Identifying The Benefit ofLinked Data Richard Wallis! Technology Evangelist @rjw Melbourne - 2nd July 2015
- 2. https://www.wikidata.org/entity/Q937 Identifying The Benefit ofLinked Data Richard Wallis! Technology Evangelist @rjw Melbourne - 2nd July 2015
- 11. NO MAN ISJUST A NUMBER
- 12. NO MAN ISJUST A NUMBER https://www.wikidata.org/entity/Q937 https://viaf.org/viaf/75121530/ http://isni.org/0000000077040933 http://id.loc.gov/authorities/names/n79022889 http://www.imdb.com/name/nm0251868/ http://data.nytimes.com/49783928729941204213 http://www.researcherid.com/rid/I-6013-2012
- 13. NO MAN ISJUST A NUMBER https://www.wikidata.org/entity/Q937 https://viaf.org/viaf/75121530/ http://isni.org/0000000077040933 http://id.loc.gov/authorities/names/n79022889 http://www.imdb.com/name/nm0251868/ http://data.nytimes.com/49783928729941204213 http://www.researcherid.com/rid/I-6013-2012 }sameAs
- 15.
- 16.
- 17. Linked Data RDF Anyone cansay anything about anything
- 18. Linked Data RDF Anyone cansay anything about anything ..in Triples.. schema:name “Albert Einstein”.<http://viaf.org/viaf/75121530>
- 20.
- 21.
- 22. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; Hypothetical example
- 23. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; schema:alumniOf <http://ethz.ch>; Hypothetical example
- 24. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; schema:alumniOf <http://ethz.ch>; <http://ethz.ch> a schema:Organization ; schema:name “Swiss Federal Institute of Technology”; schema:url <http://www.ethz.ch>; schema:sameAs <https://www.wikidata.org/entity/Q11942> Hypothetical example
- 25. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; schema:alumniOf <http://ethz.ch>; schema:sameAs <http://isni.org/0000000077040933>; <http://ethz.ch> a schema:Organization ; schema:name “Swiss Federal Institute of Technology”; schema:url <http://www.ethz.ch>; schema:sameAs <https://www.wikidata.org/entity/Q11942> Hypothetical example
- 26. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; schema:alumniOf <http://ethz.ch>; schema:sameAs <http://isni.org/0000000077040933>; schema:sameAs <https://www.wikidata.org/entity/Q937> <http://ethz.ch> a schema:Organization ; schema:name “Swiss Federal Institute of Technology”; schema:url <http://www.ethz.ch>; schema:sameAs <https://www.wikidata.org/entity/Q11942> Hypothetical example
- 27. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; schema:alumniOf <http://ethz.ch>; schema:sameAs <http://isni.org/0000000077040933>; schema:sameAs <https://www.wikidata.org/entity/Q937> <http://ethz.ch> a schema:Organization ; schema:name “Swiss Federal Institute of Technology”; schema:url <http://www.ethz.ch>; schema:sameAs <https://www.wikidata.org/entity/Q11942> Hypothetical example
- 28. <http://ethz.ch/12345> a schema:Person ; schema:name“Albert Eistein” ; schema:alumniOf <http://ethz.ch>; schema:sameAs <http://isni.org/0000000077040933>; schema:sameAs <https://www.wikidata.org/entity/Q937> <http://ethz.ch> a schema:Organization ; schema:name “Swiss Federal Institute of Technology”; schema:url <http://www.ethz.ch>; schema:sameAs <https://www.wikidata.org/entity/Q11942> Hypothetical example
- 29.
- 30. • Create andconnect identifiers — URIs Link your data
- 31. • Create andconnect identifiers — URIs • Describe your resources Link your data
- 32. • Create andconnect identifiers — URIs • Describe your resources • Use what works for you Link your data
- 33. • Create andconnect identifiers — URIs • Describe your resources • Use what works for you • Expose / Publish to the Web Link your data
- 34.
- 35. Link your data Groundyour descriptions • Set your resources in context
- 36. Link your data Groundyour descriptions • Set your resources in context • Link to hubs of authority
- 37. One Hub toRule Them All?
- 38. VIAF.org One Hub toRule Them All? A web of authoritative hubs
- 39. VIAF.org One Hub toRule Them All? A web of authoritative hubs
- 40. Its not justabout people
- 41. person place object concept organizationwork Its not just about people
- 42. The library knowledge graph A graph of relationships person place object concept organization work Its not just about people
- 47. Dublin Core FOAF SKOS Bibo /OAD BIBFRAME RDA / Marc CIDOC CRM Bio / Geo OWL / RDF / RDFS Schema.org Ontology Project Vocabularies With Search Engine Recognition Selecting your vocabularies
- 48. Dublin Core FOAF SKOS Bibo /OAD BIBFRAME RDA / Marc CIDOC CRM Bio / Geo OWL / RDF / RDFS Schema.org Ontology Project Vocabularies With Search EngineRecognition Selecting your vocabularies
- 49.
- 50.
- 51. With Search Engine Recognition A generalpurpose vocabulary for describing things on the web.
- 52. With Search Engine Recognition A generalpurpose vocabulary for describing things on the web. • Backed by the Search Engines
- 53. With Search Engine Recognition A generalpurpose vocabulary for describing things on the web. • Backed by the Search Engines • W3C Community - Discussion, proposals, organisation, Github
- 54. With Search Engine Recognition A generalpurpose vocabulary for describing things on the web. • Backed by the Search Engines • W3C Community - Discussion, proposals, organisation, Github • A live evolving vocabulary
- 55. With Search Engine Recognition A generalpurpose vocabulary for describing things on the web. • Backed by the Search Engines • W3C Community - Discussion, proposals, organisation, Github • A live evolving vocabulary • Used by millions of domains
- 56. With Search Engine Recognition A generalpurpose vocabulary for describing things on the web. • Backed by the Search Engines • W3C Community - Discussion, proposals, organisation, Github • A live evolving vocabulary • Used by millions of domains • Expanding into domain specific extensions
- 57. Used by millionsof domains
- 58. Used by millionsof domains 640 Types (Classes) 988 Properties
- 59. Used by millionsof domains 640 Types (Classes) 988 Properties
- 60. Used by millionsof domains 640 Types (Classes) 988 Properties
- 61. Used by millionsof domains 640 Types (Classes) 988 Properties
- 62. Used by millionsof domains 640 Types (Classes) 988 Properties
- 63. Used by millionsof domains 640 Types (Classes) 988 Properties
- 64. Used by millionsof domains 640 Types (Classes) 988 Properties
- 65. Used by millionsof domains 640 Types (Classes) 988 Properties
- 66.
- 67.
- 68.
- 69.
- 70. Extending Schema.org www.w3.org/community/schemabibex Schema.org extensions •Community led • Domain focused
- 71. Extending Schema.org www.w3.org/community/schemabibex Schema.org extensions •Community led • Domain focused • Flat namespace
- 72. Extending Schema.org www.w3.org/community/schemabibex Schema.org extensions •Community led • Domain focused • Flat namespace • Hosted by Schema.org
- 73. Extending Schema.org www.w3.org/community/schemabibex Schema.org extensions •Community led • Domain focused • Flat namespace • Hosted by Schema.org • Initial extensions: - bib.schema.org - auto.schema.org - ???.schema.org
- 74. Dublin Core FOAF SKOS Bibo /OAD BIBFRAME RDA / Marc CIDOC CRM Bio / Geo OWL / RDF / RDFS Schema.org Ontology Project Vocabularies With Search EngineRecognition Select vocabularies with purpose
- 75. Dublin Core FOAF SKOS Bibo /OAD BIBFRAME RDA / Marc CIDOC CRM Bio / Geo OWL / RDF / RDFS Schema.org Ontology Project Vocabularies With Search Engine Recognition Select vocabularies with purpose
- 76. Dublin Core FOAF SKOS Bibo /OAD BIBFRAME RDA / Marc CIDOC CRM Bio / Geo OWL / RDF / RDFS Schema.org Ontology Project Vocabularies Being discovered is ! usually one purpose With Search Engine Recognition Select vocabularies with purpose
- 77. Research: A discovery unsharedis a secret
- 78. Research: Discovering and connectingfacts, materials, sources, people, places, events, organisations … and other research. A discovery unshared is a secret
- 79. Research: Discovering and connectingfacts, materials, sources, people, places, events, organisations … and other research. A discovery unshared is a secret •Identify - to share
- 80. Research: Discovering and connectingfacts, materials, sources, people, places, events, organisations … and other research. A discovery unshared is a secret •Identify - to share •Identify - to link
- 81. Research: Discovering and connectingfacts, materials, sources, people, places, events, organisations … and other research. A discovery unshared is a secret •Identify - to share •Identify - to link •URI - Uniform Resource Identifier
- 82. A Linked DataRecipe
- 83. A Linked DataRecipe 1. Establish the entities in your data - Person, Work, Place, Event, Concept, …
- 84. A Linked DataRecipe 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729>
- 85. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply
- 86. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format
- 87. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context
- 88. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, …
- 89. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers
- 90. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs
- 91. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain
- 92. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain c. Schema.org for everyone else
- 93. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain c. Schema.org for everyone else 6. Openly share your data
- 94. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain c. Schema.org for everyone else 6. Openly share your data - Open Data license
- 95. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain c. Schema.org for everyone else 6. Openly share your data - Open Data license - Return RDF from your URIs - Turtle, JSON, RDF/XML,Triples
- 96. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain c. Schema.org for everyone else 6. Openly share your data - Open Data license - Return RDF from your URIs - Turtle, JSON, RDF/XML,Triples - Embed Schema.org in your HTML
- 97. A Linked DataRecipe <http://myedu.org/faculty/54729>! a schema:Person ;! schema:name “Prof. Green” . sameAs <https://viaf.org/viaf/75121530/> . 1. Establish the entities in your data - Person, Work, Place, Event, Concept, … 2. Give them URIs <http://myedu.org/faculty/54729> 3. Describe each entity - no matter how simply - don’t just transform an old record format 4. Link to authoritative hubs to set your entities in context - ISNI, VIAF, ORCID, WorldCat Works, LCSH, Wikidata, … 5. Use appropriate vocabularies useful for all consumers a. The vocabularies for your needs b. Appropriate for your domain c. Schema.org for everyone else 6. Openly share your data - Open Data license - Return RDF from your URIs - Turtle, JSON, RDF/XML,Triples - Embed Schema.org in your HTML - Optionally add a SPARQL Endpoint to taste
- 98.
- 99. Entities and LinkedData 330 Million resources
- 100. Entities and LinkedData 330 Million resources 198 Million Works
- 101. Entities and LinkedData 330 Million resources 198 Million Works 98 Million Persons
- 102. Entities and LinkedData 330 Million resources 198 Million Works 98 Million Persons VIAF — ISNI — FAST
- 109.
- 110. Identifying The Benefit ofLinked Data Richard Wallis! Technology Evangelist @rjw Melbourne - 2nd July 2015