This document discusses the history of the Dublin Core metadata standard and lessons learned that can help Linked Data succeed on the web. It describes how Dublin Core started with 15 simple metadata elements for resource discovery on the 1990s web. Over time, Dublin Core adopted RDF and developed an abstract data model, but struggled with concepts like open-world modeling, HTTP URIs, and modeling abstract concepts. For Linked Data to work, these challenges of integrating RDF and modeling abstract concepts need to be overcome. Dublin Core provides a useful vocabulary and experience that can help Linked Data succeed on the modern web.
Linked Data challenges and the history of Dublin Core metadata standard
1. Linked Data – the long and winding road Andy Powell, Eduserv @andypowe11 Linked Data – the future of knowledge organisation on the Web, London 14 Sept 2010
2. today’s topic... Linked Data: the future of knowledge organisation on the Web ...pre-supposes that Linked Data is the future of the Web and for that to be true, we have to understand the challenges we face in making it a reality
3. a story about the history of the Dublin Core initiative and what that history tells us about the challenges for Linked Data it’s a largely non-technical story (superficial?)
4. about me... long association with both Dublin Core and RDF more immersed in former than latter member of both the DC Usage Board and the Advisory Board previous chair of the DC Architecture WG lead author of the original DCMI Abstract Model
8. a record centric approach shipping records from A to B and the ‘record’ as mechanism for tracking provenance
9.
10. 15 ‘fuzzy buckets’a hang-over from days of library catalogue card – on which notes could be written?
11. flat-world modelling 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 c.f. use of dc:creator in practice
13. little abstraction of the model ...from the ‘syntax’ actually little shared understanding of the underlying model
14. addition of the model firstly using the analogy of a language ‘grammar’ then thru the development of the ‘Dublin Core Abstract Model’ then thru the addition of the ‘Application Profile’ essentially the RDF model
15. what have been the challenges of bringing the RDF model to the DC community?
20. so... my contention is that if Linked Data has a role to play in the future of knowledge organisation then Linked Data must be successful on the Web and that means that RDF must be successful on the Web
21. DC brings a useful vocabulary of ‘core’ properties and classes
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.