270 likes | 514 Views
RDA and the semantic Web. Lectio magistralis in Library Science b y Gordon Dunsire Florence University, Florence , Italy 4th March, 2014. In the beginning …. 3?. Toronto, 1997. General Material Designator (US). General Material Designator (UK). Content vs Carrier / Haworth.
E N D
RDA and the semantic Web Lectiomagistralis in Library Science by Gordon Dunsire Florence University, Florence, Italy 4th March, 2014
In the beginning … 3? Toronto, 1997
General Material Designator (US) General Material Designator (UK) Content vs Carrier / Haworth Logical analysis / Delsey Chief source of information Item Series Subseries Type of publication Class of materials Structure of AACR3 $£$£$£!!! ? ISBD(G)
Functional Requirements for Bibliographic Records Work Expression User tasks Manifestation Item Content attributes Carrier attributes AACR3 Item JSC, 2005
Semantic Web (Berners-Lee) Structured collections of information Sets of inference rules Automated reasoning Web of linked data Web of linked documents Web of linked computing devices
Resource Description Framework (RDF) “This work has author Gordon Dunsire” Triple! Subject – Predicate - Object ex:1Bd38 ? Subject “This work” Predicate “has author” ? ex:ZX3G5 Object “Gordon Dunsire” ? “literal” Uniform Resource Identifier (URI) For machines For humans
ex:“is derivative work of” ex:“has derivative work” ex:“hastitle” “RDA and the Semantic Web” ex:“has author” One giant global graph “Gordon Dunsire” ex:“hasname” ex: “This work” ex: “That work” ex: Scotland ex:“is author of” ex: Gordon Dunsire ex: “This work” “G. J. Dunsire” ex:“has author” ex:“hasalternate name” ex:“has country of birth”
Data vs Ontology Data triple URI ex: Gordon Dunsire ex: “This work” ex: hasAuthor ex:“has author” ex:“haslabel” Ontology triple ex:“hastype” “has author” “Property”
RDA vocabulary example “notated music”@en ex:“haslabel” “schriftlichfixierteMusik”@de ex:“haslabel” rdact: 1010 rdact: 1016 ex: “is related to” ex:“haslabel” “tactile notated music”@en
Inference rules: sub-property ex:“haslabel” “has author”@en ex:“has author” ex:“hascreator” ex: “is sub- property of” “has creator”@en ex: “This work” ex: “This work” ex: Property1 ex: Property2 ex:“haslabel” “Gordon Dunsire” “Gordon Dunsire”
rdfs:label rdfs:comment RDF vocabularies: DCT + RDFS Dublin Core Terms + RDF Schema rdfs:range rdfs:label “Creator” “Agent” dcterms: creator dcterms: Agent “A resource that acts or has the power to act.” Source of URIs
Inference rules: range rdfs:range ex: Gordon Dunsire ex: Gordon Dunsire ex: “This work” dcterms: creator dcterms: agent dcterms: Agent rdfs:type dcterms:creator
Data model meeting Panizzi British Library, London, 30 April – 1 May 2007 Members of RDA and Semantic Web communities “… agreed that RDA and DCMI should work together …” (Dublin Core Metadata Initiative)
Benefits expected • The library community gets a metadata standard that is compatible with the Web Architecture and that is fully interoperable with other Semantic Web initiatives • The DCMI community gets a libraries application profile firmly based on the DCAM and FRBR (which will be a high profile exemplar for others to follow) • The Semantic Web community get a significant pool of well thought-out metadata terms to re-use • There is wider uptake of RDA
Activities • Development of an RDA Element Vocabulary • Development of an RDA DC Application Profile based on FRBR and FRAD • Disclosure of RDA Value Vocabularies using RDF/RDFS/SKOS
Opaque URI (only for machines) Compact URI = rdact:1010
DCAM and RDA Dublin Core Abstract Model rdae: “has content type” <indecs> skos:inScheme rdfs:label Basic RDA metadata structures ex: ExpressionURI rdact: 1010 “notated music”@en rdaterms: RDAContentType
High-level metadata structures Unconstrained rdfs: “domain” Constrained by FRBR (domain) sP rdfs: “domain” rdam: “has title” rdau: “has title” rdam: “has title proper” rdau: “has title proper” rdac: “Manifestation” sP sP sP = rdfs:”sub-property of”
Relationship designators sP rdaw: “has creator” rdau: “has creator” rdau: “has designer” rdaw: “has designer” rdac: “Work” rdac: “Agent” rdfs: “domain” sP rdfs: “range” sP sP = rdfs:”sub-property of”
Link-ability Domains Relationships Attributes Triple chains Triple clusters Literals Covering all media
Rich detail rdaw: “is video screenplay (work)” rdaw: “is screenplay (work)” rdaw: “has related work” rdaw: “has accompanying work relationship with” rdaw: “is complemented by (work)” sub-property ladder
Interoperability ??? rdau: “has voice actor” rdaw: “has creator” rdau: “has actor” dcterms: “creator” dc: “creator” rdau: “has performer” rdau: “has creator”
To do • Publish more RDA value vocabularies • Develop cross-entity elements • E.g. Work-Expression relationship designators • Develop Application Profile for RDA “core” • Develop RDF elements for aggregated statements (RDA, ISBD, MARC, …) • E.g. Place of publication -> Publication statement
Achievements: 5+ years on • Rich set of elements and value vocabularies for “bibliographic control” • At global, “universal” level • “a metadata standard that is compatible with the Web Architecture and that is fully interoperable with other Semantic Web initiatives” • “a significant pool of well thought-out metadata terms to re-use” • Wider uptake of RDA? …
Thank you! • gordon@gordondunsire.com