Linked data - the long and winding road

2,340 views
2,262 views

Published on

A presentation at the ISKO UK One-day Workshop, Linked Data: the Future for Knowledge Organisation on the Web.

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

No Downloads
Views
Total views
2,340
On SlideShare
0
From Embeds
0
Number of Embeds
500
Actions
Shares
0
Downloads
30
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • I’ve invented a new Batman villain. His name is “The Modeller” and his scheme is to model Gotham city entirely accurately in a way that is of no practical value to anybody. He has an OWL which sits on his shoulder which has the power to absorb huge amounts of time and energy....Over the 3 issues there’s a running subplot about The Modeller's master weapon, the FRBR, which everyone knows is very very powerful but when the citizens of Gotham talk about it none of them can quite agree on exactly what it does....While unpopular with the fans, issue two, “Batman vs the Protégé“, will later be hailed as a Kafkaesque masterpiece. Batman descends further into madness as he realises that every moment he’s the Batman of that second in time, and each requires a URI, and every time he considers a plan of action, the theoretical Batmen in his imagination also require unique distinct identifiers which he must assign before continuing.
  • Linked data - the long and winding road

    1. 1. Linked Data – the long and winding road<br />Andy Powell, Eduserv<br />@andypowe11<br />Linked Data – the future of knowledge organisation on the Web, London<br />14 Sept 2010<br />
    2. 2. today’s topic...<br />Linked Data: the future of knowledge organisation on the Web<br />...pre-supposes that Linked Data is the future of the Web<br />and for that to be true, we have to understand the challenges we face in making it a reality<br />
    3. 3. a story<br />about the history of the Dublin Core initiative<br />and what that history tells us about the challenges for Linked Data<br />it’s a largely non-technical story (superficial?)<br />
    4. 4. about me...<br />long association with both Dublin Core<br />and RDF<br />more immersed in former than latter<br />member of both the DC Usage Board and the Advisory Board<br />previous chair of the<br />DC Architecture WG<br />lead author of the original<br />DCMI Abstract Model<br />
    5. 5. 15<br />What is DC?<br />Dublin Core (DC) is a metadata standard that provides a vocabulary for describing the "core" attributes of resources, most often in the context of resource discovery on the Web<br /><ul><li>~60 properties and classes within well curated vocabulary maintenance environment
    6. 6. declared using RDF/RDFS</li></li></ul><li>how did we get here?<br />work on DC started in 1995 with 12 (later 15) ‘metadata elements’<br />remember what the web was like in 1995?<br />a library approach to resource discovery<br />descriptive records embedded into web pages – using the HTML ‘meta’ tag<br />a focus on ‘document like objects’<br />librarian-centric<br />
    7. 7. what impact has that had on DC?<br />
    8. 8. a record centric approach<br />shipping records from A to B<br />and the ‘record’ as mechanism for tracking provenance <br />
    9. 9. <ul><li>broad semantics
    10. 10. 15 ‘fuzzy buckets’</li></ul>a hang-over from days of library catalogue card – on which notes could be written?<br />
    11. 11. flat-world modelling<br />1:1 principle - the principle whereby related but conceptually different entities, for example a painting and a digital image of the painting, are described by separate metadata records<br />c.f. use of dc:creator in practice<br />
    12. 12. Strings vs. things<br />
    13. 13. little abstraction of the model<br />...from the ‘syntax’<br />actually little shared understanding of the underlying model<br />
    14. 14. addition of the model<br />firstly using the analogy of a language ‘grammar’<br />then thru the development of the ‘Dublin Core Abstract Model’<br />then thru the addition of the ‘Application Profile’<br />essentially the RDF model<br />
    15. 15. what have been the challenges of bringing the RDF model to the DC community?<br />
    16. 16. Selling an ‘open world’ view...<br />selling an open-world view<br />
    17. 17. the ‘http’ URI problem<br />the ‘http’ URI problem<br />
    18. 18. modelling...<br />modelling<br />
    19. 19. http://blogs.ecs.soton.ac.uk/webteam/2010/09/02/the-modeler/<br />
    20. 20. so...<br />my contention is that if Linked Data has a role to play in the future of knowledge organisation<br />then Linked Data must be successful on the Web<br />and that means that RDF must be successful on the Web<br />
    21. 21. DC brings a useful vocabulary of ‘core’ properties and classes<br />
    22. 22. the history of DC helps us understand the challenges:<br /><ul><li>easing the pain of modelling
    23. 23. understanding http URIs and how they can be managed
    24. 24. working within an ‘open world’ view</li></li></ul><li>also that DC brings some important functional requirements to the Linked Data (RDF) world<br /><ul><li>‘boundedness’ (graphs, named graphs, records) particularly to support provenance
    25. 25. ‘constraints’ on those bounded graphs to support communities of practice</li></li></ul><li>Thank you<br />Thank you<br />psyberartist<br />bitzcelt<br />oseillo<br />Richard Parmiter<br />Justin Marty<br />Eric M Martin<br />jeremyfoo<br />robotson<br />...all at Flickr<br />Images by...<br />snarl <br />Vermin Inc<br />rachael.<br />mollyali<br />ArsElectronica<br />spike55151<br />actionhero<br />Jessie Reeder<br />

    ×