linked data in practice

23
Linked Data in Practice Oregon Digital Linked Data Workshop, Eugene Oregon November 25, 2013 Karen Estlund [email protected]

Upload: karen-estlund

Post on 25-Jun-2015

101 views

Category:

Technology


1 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Linked data in practice

Linked Data in PracticeOregon Digital Linked Data Workshop, Eugene OregonNovember 25, 2013

Karen [email protected]

Page 2: Linked data in practice

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

Page 3: Linked data in practice

Why now?

grufnik, http://www.flickr.com/photos/grufnik/298814187/, CC BY-NC-ND

Page 4: Linked data in practice

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.

Page 5: Linked data in practice

Metadata Schemas

Page 6: Linked data in practice

Linked Data Vocabularies

Page 7: Linked data in practice

Vocabularies Building upon Each Other

E.g. DarwinCore building on DublinCore

Page 8: Linked data in practice

Self-contained Vocabularies

Page 9: Linked data in practice

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.

Page 10: Linked data in practice

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.

Page 11: Linked data in practice

Blank Node Example

<creator><creatorName>...</creatorName><nameIdentifier

nameIdentifierScheme=”...”schemeURI=”...”>...

</nameIdentifier></creator>

Page 12: Linked data in practice

Blank Node RDF Graph

My Presentation

dcite:creator

Estlund, Karen

dcite:creatorName 951...

dcite:nameIdentifier

Page 13: Linked data in practice

Linked Data Resources

Page 14: Linked data in practice

Example from BBC News

Page 15: Linked data in practice

LOD in HTML <head>

Page 16: Linked data in practice

Example from Historic Oregon Newspapers

Page 17: Linked data in practice

LOD at expected URL (e.g. ‘X.rdf’)

http://oregonnews.uoregon.edu/lccn/sn84022653/1897-05-01/ed-1/seq-5.rdf

Page 18: Linked data in practice

Example from Oregon Digital Hydra

Page 19: Linked data in practice

Expected file

http://hydra-dev.library.oregonstate.edu/catalog/oregondigital:41.nt

Page 20: Linked data in practice

Authority in Linked Data

Page 21: Linked data in practice

Interface Issues

Page 22: Linked data in practice

Institution or Community?

Shoupiest, http://www.flickr.com/photos/shoupiest/4470852646/, CC BY-NC

Page 23: Linked data in practice

Questions

?