Web of data
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Web of data

on

  • 2,419 views

Introduction session to the WOD-PD event in Vienna http://www.webofdata.info/

Introduction session to the WOD-PD event in Vienna http://www.webofdata.info/

Statistics

Views

Total Views
2,419
Views on SlideShare
2,419
Embed Views
0

Actions

Likes
2
Downloads
29
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

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

Web of data Presentation Transcript

  • 1.
    • Web of Data 101
    • Keith Alexander (Talis)
    • Yves Raimond (QMUL/BBC A&Mi)
    • WOD-PD 2008, October 22 nd , 2008
  • 2. Outline
    • Introduction to linked data
    • 1 st hacking session
    • SPARQL
    • 2 nd hacking session
    • What's out there?
  • 3. The Web of Data
  • 4. The Web
    • Names (URIs)
    • Documents (HTML, XML, JSON, ...)
    • Interactions with names (HTTP)
    Names Documents HTTP GET
  • 5. Links
  • 6. What does it look like, now?
    • Names identify documents, e.g. HTML, XML, etc.
    • Documents are interlinked:
    <a href=” http://moustaki.org/ ” />
  • 7. Web of documents
  • 8. We understand...
  • 9. We understand...
  • 10. Machines don't...
  • 11. Shortcomings
    • Untyped links
      • Friend?
      • City?
      • Favorite artist?
    • Opacity
      • Me?
      • That gig?
      • A pizza?
    • ”Give me bands that I listened to in the month who are making a gig next to my current location”
  • 12. The Google way
    • Let's aggregate a massive amount of documents. By using the linkage information and statistical analysis, we can infer enough to provide a good search service.
  • 13. Right, but...
    • Search is not everything
      • ”Give me bands that I listened to in the last month who are making a gig next to my current location”
    • Information extraction must cover:
      • Multiple domains
      • Multiple media
    • Frustrating
      • Documents often generated from database
      • Why reverse-engineer the ”view” process?
  • 14. Silos and views
  • 15. Solution
    • Easy, let's just build web services on top of the WS-* stack, wrapping every single possible database query
  • 16.
    • Just jocking :-)
  • 17. Web of data
    • Let's get back to the Web:
      • Names (URIs)
      • Documents (HTML, XML, JSON, ...)
      • Interactions (HTTP GET/POST/PUT/DELETE)
    • Not only documents can be named !!
      • Persons, cities, bands, WOD-PD...
    • Documents can hold structured data
      • Stuff that your program can use
    • Problem solved. Session finished.
  • 18. Web of data A web of things
  • 19. RDF
    • RDF is the web standard for such structured data
    • RDF data model:
      • Subject (URI)
      • Property (URI)
      • Object (URI or literal)
  • 20. RDF literals
    • Literals are just string values
    • They can have language tags associated with them
    • Or they can have a datatype associated with them
    • Or they can be plain
  • 21. RDF example
    • http://moustaki.org/foaf.rdf#moustaki
    • http://xmlns.com/foaf/0.1/based_near
    • http://dbpedia.org/resource/London
  • 22.
    • http://dbpedia.org/resource/The_Clash
    • http://dbpedia.org/property/origin
    • http://dbpedia.org/resource/London
  • 23.
    • http://moustaki.org/foaf.rdf#moustaki
    • http://xmlns.com/foaf/0.1/interest
    • http://dbpedia.org/resource/The_Clash
  • 24. RDF Me The Clash London
  • 25. The nice thing about all those URIs
    • … is that you can look them up to get more information about the things they signify.
    • Even the properties and types are URIs. This means you can look them up to get more information about their semantics.
      • Web ontologies
    • You can also do handy things like retrieve the labels (rdfs:label) of the predicates, to create dynamic user interfaces.
  • 26. Writing RDF
    • RDF is the data model
    • Different ways to serialise RDF
      • RDF/XML
      • Turtle
      • RDFa (RDF embedded in XHTML)
  • 27. RDF/XML
    • <foaf:Person rdf:about=” http://moustaki.org/foaf.rdf#moustaki ”>
    • <foaf:knows rdf:resource=” http://sw-app.org/mic.xhtml#i ”/>
    • <foaf:interest rdf:resource=” http://dbpedia.org/resource/The_Clash ”>
    • <foaf:name>Yves Raimond</foaf:name>
    • </foaf:Person>
  • 28. Turtle
    • < http://moustaki.org/foaf.rdf#moustaki >
    • a foaf:Person;
    • foaf:interest < http://dbpedia.org/resource/The_Clash >;
    • foaf:knows < http://sw-app.org/mic.xhtml#i >;
    • foaf:name ”Yves Raimond” .
  • 29. Summary - Linked Data principles
    • 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 RDF information
    • Include RDF statements that link to other URIs so that they can discover related things Tim Berners-Lee, 2007 http://www.w3.org/DesignIssues/LinkedData.html
  • 30. Example
    • http://dbtune.org/jamendo/artist/5
    • RDF representation:
      • This is an artist
        • http://purl.org/ontology/mo/MusicArtist
      • It made two records
        • http://dbtune.org/jamendo/record/33
        • http://dbtune.org/jamendo/record/174
      • It is based near a place
        • http://sws.geonames.org/2991627/
    • More information about that place? GET it!
  • 31. Tabulator demo