Linked data in practice

343 views
210 views

Published on

Part 2 of a Linked Data Workshop for library staff at University of Oregon and Oregon State University Libraries.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
343
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Linked data in practice

  1. 1. Linked Data in Practice Oregon Digital Linked Data Workshop, Eugene Oregon November 25, 2013 Karen Estlund kestlund@uoregon.edu
  2. 2. The Promise of the Semantic Web I have a dream for the Web [in which computers] become capable of analyzing all the data on the Web – the content, links, and transactions between people and computers. — Tim Berners-Lee, 1999
  3. 3. Why now? grufnik, http://www.flickr.com/photos/grufnik/298814187/, CC BY-NC-ND
  4. 4. Principles 1. You should not be constrained by your schema. 2. You are not that special. 3. You do not know everything. 4. If your data isn’t reusable, shareable, and machine readable, then you’re not doing good enough. 5. Use exemplary behavior and reuse from others so that they may also reuse from you.
  5. 5. Metadata Schemas
  6. 6. Linked Data Vocabularies
  7. 7. Vocabularies Building upon Each Other E.g. DarwinCore building on DublinCore
  8. 8. Self-contained Vocabularies
  9. 9. Comparing “Title” ● DataCite, Title ○ A name or title by which a resource is known. ● DublinCore, Title ○ A name given to the resource. ● MODS, Title ○ A word, phrase, character, or group of characters that constitutes the chief title of a resource (i.e. the title normally used when citing the resource). ● Open Graph, Title ○ The title of your object as it should appear within the graph.
  10. 10. Comparing “Title” Cont. ● VRA Core 4.0, Title ○ The title or identifying phrase given to a Work or an Image. For complex works or series the title may refer to a discrete component or unit within the larger entity (a print from a series, a panel from a fresco cycle, a building within a temple complex) or may identify only the larger entity itself. Record multiple titles in repeating instances of the ti tle element. Indicate the preferred title with pref ="true" and alternate titles with pref="false". For an Image record this category describes the specific view of the depicted Work or Collection, and corresponds to the CCO View Description.
  11. 11. Blank Node Example <creator> <creatorName>...</creatorName> <nameIdentifier nameIdentifierScheme=”...” schemeURI=”...”>... </nameIdentifier> </creator>
  12. 12. Blank Node RDF Graph My Presentation dcite:creator dcite:nameIdentifier dcite:creatorName Estlund, Karen 951...
  13. 13. Linked Data Resources
  14. 14. Example from BBC News
  15. 15. LOD in HTML <head>
  16. 16. Example from Historic Oregon Newspapers
  17. 17. LOD at expected URL (e.g. ‘X.rdf’) http://oregonnews.uoregon.edu/lccn/sn84022653/1897-05-01/ed-1/seq-5.rdf
  18. 18. Example from Oregon Digital Hydra
  19. 19. Expected file http://hydra-dev.library.oregonstate.edu/catalog/oregondigital:41.nt
  20. 20. Authority in Linked Data
  21. 21. Interface Issues
  22. 22. Institution or Community? Shoupiest, http://www.flickr.com/photos/shoupiest/4470852646/, CC BY-NC
  23. 23. Questions ?

×