• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Linked data: Four rules and five stars for the Amsterdam Museum
 

Linked data: Four rules and five stars for the Amsterdam Museum

on

  • 1,400 views

Slides used for a guest lecture about Linked Data for the course "Knowledge and Media" at the VU Amsterdam (Nov 2011). ...

Slides used for a guest lecture about Linked Data for the course "Knowledge and Media" at the VU Amsterdam (Nov 2011).
The talk takes the practical example of converting Amsterdam Museum data to Five-star Linked Open Data.

Statistics

Views

Total Views
1,400
Views on SlideShare
1,367
Embed Views
33

Actions

Likes
0
Downloads
19
Comments
0

2 Embeds 33

http://www.few.vu.nl 32
http://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Things = “resources”
  • - Not completely straightforward xml (nestedness)
  • XMLRDF tool: clean up, link to resources etc.
  • PREFIX am: PREFIX skos: SELECT ?proxy ?xWHERE {?proxy am:material ?x. ?x skos:prefLabel "gietijzer"@nl}ORDER BY ?proxyLIMIT 50
  • Apps for AmsterdamPlaatsen van Betekenis
  • Apps for AmsterdamPlaatsen van Betekenis
  • Apps for AmsterdamPlaatsen van Betekenis

Linked data: Four rules and five stars for the Amsterdam Museum Linked data: Four rules and five stars for the Amsterdam Museum Presentation Transcript

  • Linked Data Victor de BoerSlide stolen from Christophe Gueret
  • Why Linked Data?
  • Why linked data (1/2)Slide stolen from Christophe Gueret
  • Why linked data (2/2)Slide stolen from Christophe Gueret
  • ``Sharable, spreadable and nerd-friendly’’ -- Charlotte S H Jensen, kulturweb
  • Four rules of Linked Data1. Use URIs as names for things (Resources)2. Use HTTP URIs so that people can look up those names. (Dereferencing)3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)4. Include links to other URIs. so that they can discover more things. http://www.w3.org/DesignIssues/LinkedData.html
  • Linked Open Data five star system Available on the web (whatever ★ format), but with an open license Available as machine-readable ★★ structured data (e.g. excel instead of image scan of a table) as (2) plus non-proprietary format ★★★ (e.g. CSV instead of excel) All the above plus, Use open standards from W3C (RDF and ★★★★ SPARQL) to identify things, so that people can point at your stuff All the above, plus: Link your data ★★★★★ to other people’s data to provide context www.w3.org/designissues/linkeddata.html
  • Linked Data Cloud Diagram
  • May 2007
  • Oct 2007
  • “Linking Open Data cloud diagram, by Richard Cyganiak and Anja Jentzsch. http://lod-cloud.net/”
  • “Linking Open Data cloud diagram, by Richard Cyganiak and Anja Jentzsch. http://lod-cloud.net/”
  • Amsterdam Museum as Linked Open Data
  • Use case on how to transform “raw” XML data into 5-star Linked Open Data
  • Europeana• “Europeana enables people to explore the digital resources of Europes museums, libraries, archives and audio-visual collections.’’ www.europeana.eu From portal… …to data aggregator.
  • Amsterdam Museum• Formerly Amsterdam Historic Museum – “The rich collection of works of art, objects and archaeological finds brings to life the fortunes of Amsterdammers of days gone by and today.”• In March 2010 published their whole collection online – 70.000 objects – CC license• We converted their data to RDF
  • AM metadata <record priref="10541“ >• Adlib database XML API <acquisition.date>1997</acquisition.date> <dimension> <dimension.type>hoogte</dimension.type> <dimension.unit>cm</dimension.unit> <dimension.value>6</dimension.value>• Object metadata … </dimension> • 73.000 objects, 256MB </record> • Nested XML• Concept Thesaurus <record priref="28024“ > <term>Kalverstraat 124</term> <broader_term>Kalverstraat</broader_term> • 27.000, 9MB <term.type>GEOKEYW </term.type> • Different types (geo,motif, event) </record>• Person ‘Thesaurus’ <record priref="6" > • 67.000 persons, 10MB <biography>boekverkoper en uitgever van cartografie</biography> • Consolidated from object metadata fields <birth.date.start>1659</birth.date.start> • Creators, annotators, reproduction <death.date.start>1733</death.date.start> <name>Aa, Pieter van der</name> creators, institutions, <nationality>Nederlands</nationality> <use>Aa, Pieter van der (I)</use> </record>
  • Back to the four rules of Linked Data1. Use URIs as names for things2. Use HTTP URIs so that people can look up those names.3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)4. Include links to other URIs. so that they can discover more things. http://www.w3.org/DesignIssues/LinkedData.html
  • How to make cool URI’sUse HTTP://Use a namespace you controlUnique, stable and persistent• Don’t use: – Author name, subject, status, access, file name extension, software mechanism C://MyDisk/awesome/VdeBoer/latest/cgi_bin/rembrandt.html
  • Amsterdam Museum URIs• PURL basename: http://purl.org/collections/nl/am/• Objects: Use “prirefs”, prefixed by “proxy-” – http://purl.org/collections/nl/am/proxy-63432• Concepts & Persons: Use “prirefs”, prefixed by “p-”, or “t-” – http://purl.org/collections/nl/am/p-201• Properties (schema): Use XML element name – http://purl.org/collections/nl/am/acquisition.date
  • Again, the rules of Linked Data1. Use URIs as names for things2. Use HTTP URIs so that people can look up those names.3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)4. Include links to other URIs. so that they can discover more things. http://www.w3.org/DesignIssues/LinkedData.html
  • RDF reminderSubject Predicate Objectam:Rembrandt am:hasBirthdate “1651” Triplesam:Rembrandt foaf:knows am:PiterLastmanam:PiterLastman am:wasBornIn geonames:Amsterdam “1651” geonames:Amsterdam am:Rembrandt Graph am:PiterLastman
  • RDF conversion<record priref="19319 “ > <date>1651</date> <maker>Rembrandt (1606-1669)</maker> <object.type>etsplaat</object.type> priref “19319 ”… date</record> “1651” am:Record _:bn1 “Rembrandt (1606-1669)” object.type “etsplaat” “19319 ” am:date “1651” “1234” am:priref am:Record am:birthdate am:maker am:Person am:proxy-19319 “1606” am:p-1234 rda:name “Rembrandt” skos:Concept am:etsplaat “etsplaat” skos:prefLabel
  • Architecture SPARQL-app Browser Purl.org redirect SPARQL Web interface HTTP serverRDF(s) storage Logic Prolog http://semanticweb.cs.vu.nl/
  • How to access the data• PURL 303 redirect to VU semantic layer http://purl.org/collections/nl/am/proxy-63432  http://semanticweb.cs.vu.nl/europeana/browse/list_resource?r=h ttp://purl.org/collections/nl/am/proxy-63432• At our server: content negotiation – HTTP request text/html: • Local condensed view • Local full view – HTTP request application/rdf+xml • rdf/xml “describe”• SPARQL endpoint
  • text/html
  • text/html
  • application/rdf+xml@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .@prefix ore: <http://www.openarchives.org/ore/terms/> .@prefix ens: <http://www.europeana.eu/schemas/edm/> .@prefix ahm: <http://purl.org/collections/nl/am/>ahm:proxy-66970 a ore:Proxy ; ahm:title "Zegelstempel Felix Meritis"@nl ; ahm:material ahm:t-12463 , ahm:t-5447 ; ahm:objectCategory ahm:t-5504 ; ahm:objectName ahm:t-13817 , ahm:t-8489 ; ahm:objectNumber "KA 7653.1" ; ahm:priref "66970" .ahm:proxy-66972 a ore:Proxy ; ahm:acquisitionDate "0000" ; ahm:title "Zegelstempel mogelijk van familiewapen"@nl .
  • SPARQLhttp://semanticweb.cs.vu.nl/europeana/user/query
  • Again, the rules of Linked Data1. Use URIs as names for things2. Use HTTP URIs so that people can look up those names.3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)4. Include links to other URIs. so that they can discover more things. http://www.w3.org/DesignIssues/LinkedData.html
  • Link to other sources “19319 ” am:date “1651” “1234” am:priref am:Record am:birthdate am:maker am:Personam:proxy-19319 “1606” am:p-1234 rda:name “Rembrandt” owl:sameAs (?) Viaf:nationality Viaf:Person “Dutch” Viaf:RebrandtvanRijn “Rembrandt Harmensz. rdfs:label Van Rijn”
  • Amalgame alignment platform• Semi-automatic matching – Simple automatic techniques, – chained together by hand• 3500+ links put in RDF – 143 places linked to GeoNames – 1076 persons linked to ULAN (VIAF) – 34 persons linked to DBPedia – 2498 concepts AATNed.
  • CKAN Data Hubhttp://thedatahub.org/dataset/amsterdam-museum-as-edm-lod
  • Four rules and Five stars1. Use URIs as names for things2. Use HTTP URIs so that people can look up those names.3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)4. Include links to other URIs. so that they can discover more things.
  • And now applications!…right??
  • Developers still do this… …although more and more of this is happening
  • Some issues with L(O)D• Extra burden on the data provider• Nerd-only (aka “SPARQL is hard”)• How do we build user-friendly systems? – Ranking, user-friendly information presentation• Scalability (how do you query a huge graph?)• Licenses• Is Open always a good idea? – Context?
  • end
  • EDM
  • What kind of RDF?• Europeana Data Model (EDM) – Keep original metadata intact – Use sem web (LD) principles: RDF• Re-use of standard models – Dublin Core for metadata representation • creator, date, title etc. – SKOS for vocabularies • preferredLabel, hasBroader, etc.
  • EDM voorbeeld Provenance +web views/plaatjes proxy object metadataAggregation Physical Object geen metadata