1. RDA data and applications Gordon Dunsire Presented to staff of the British Library, Boston Spa, 20 Mar 2014

2. Outline  The presentation will describe how metadata created using RDA: Resource Description and Access is intended to be processed and used in resource discovery applications. RDA intentionally does not recommend any encoding format for the storage, transmission, or display of data, but it does specify the entities that are the focus of description, and their attributes and relationships. All RDA instructions and vocabularies are associated with one or more of the FRBR/FRAD entities Work, Expression, Manifestation, Item, Person, Family, and Corporate Body. The presentation discusses three basic data architectures supported by RDA: Flat file; relational; linked, and their relationship to the RDA instructions. The RDA element set was recently published as a namespace, so that URIs for RDA elements can be used to publish RDA linked data. The presentation shows how this data can be processed to make it suitable for sharing with data and applications within and beyond the RDA environment.

3. Functional Requirements for Bibliographic Records WorkExpression ManifestationItem User tasks AACR3 Item Carrier attributes Content attributes JSC, 2005

4. Entities: things of interest Work Expression Manifestation Item PersonCorporate Body FamilyConceptObjectEventPlace

5. Entity: focus of description (“record”) Manifestation Attributes: Abbreviated title Applied material Carrier type Copyright date Encoded bitrate … Values: aperture card audio cartridge computer disc … Resource{WEMI} entities

6. Entity: focus of relationships (links) Manifestation Corporate Body Item Person Work ExpressionFamily

7. Entity: focus of identification (access) Attributes: Date of conference, etc. Preferred name … Type of corporate body Variant name … … Access points: Combinations of attributes Corporate Body Identifier

8. Identification (access) Identifiers Authorized Access Points Structured Descriptions Unstructured Descriptions (i.e., notes) Global Local Terminal Local Aggregations of attributes

9. Data architectures Flat file Relational Linked Document (card, page) storing/displaying set of data values about multiple entities in a single aggregation. Dis-aggregation not guaranteed. [ISBD] Record storing/displaying structured set of data values in multiple hierarchical aggregations connected by local, opaque identifiers, each with a separate entity focus. Dis-aggregation guaranteed. [MARC, SQL data schema]

10. 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

11. “This work has author Gordon Dunsire” Resource Description Framework (RDF) Subject – Predicate - Object Subject Predicate Object “This work” “has author” “Gordon Dunsire” ? ? ? Uniform Resource Identifier (URI) ex:1Bd38 ex:ZX3G5 “literal” For machines For humans Triple!

12. ex: “This work” “Gordon Dunsire” ex:“has author” ex: Gordon Dunsire ex:“has author” ex: “This work” ex:“is author of” ex:“has name” “G. J. Dunsire” ex:“has alternate name” ex: Scotland ex:“has country of birth” “RDA and the Semantic Web” ex:“has title” ex: “That work” ex:“has derivative work” ex:“is derivative work of” One giant global graph

13. ex: Gordon Dunsire ex:“has author” ex: “This work” Data vs Ontology Data triple URI ex:“has label” ex: hasAuthor “has author” Ontology triple “Property” ex:“has type”

14. RDA vocabulary example ex:“has label” rdact: 1010 “notated music”@en “schriftlich fixierte Musik”@de ex:“has label” rdact: 1016 ex: “is related to” “tactile notated music”@en ex:“has label”

15. ex: Property1 “has author”@en ex: Property2 ex: “is sub- property of” “has creator”@en ex:“has label” Inference rules: sub-property ex: “This work” “Gordon Dunsire” ex:“has author” ex: “This work” “Gordon Dunsire” ex:“has creator”

16. rdae:P20037 “has translator”@en rdac:C10002rdac:C10006 “Expression”@en“Agent”@en label range rdau:P60385 “Relates an expression to a person, family, or corporate body contributing to an expression of a work by expressing the original text of the work in a language different from that of the original work.”@en “Relates a resource to an agent contributing to a resource by expressing the original text of the resource in a language different from that of the original resource.”@en domain label subPropertyOf definition semantic constraints human + machine inferences

17. ex:1 rdae:P20037 ex:2 “thing 1 has translator thing 2” ex:1 rdf:type rdac:C10006ex:2 rdf:type rdac:C10002 ex:1 rdau:P60385 ex:2 “thing 1 is a Expression” “thing 2 is a Agent” “thing 1 has translator thing 2”

18. bibo:numPagesbibo:numVolumesrdam:extentisbd:”has extent”dct:extentrdam:extentOfTextdct:formatrdau:extentrdau:extentOfTextdc:formatrdau:durationrdae:durationm21:M306__am21:M300unim:U127__aunim:U215__a

19. ex:3 rdam:extentOfText “xvii, 323 pages”@en ex:3 rdam:extent “xvii, 323 pages”@en dct:extent dct:format rdau:extent rdau:extentOfText ex:4 m21:M300 “1 map : col. ; 30 x 55 cm”@en ex:4 rdau:extent “1 map : col. ; 30 x 55 cm”@en dct:extent dct:format

20. DCAM and RDA Dublin Core Abstract Model Basic RDA metadata structures ex: ExpressionURI rdae: “has content type” rdfs:label rdact: 1010 “notated music”@en skos:inScheme rdaterms: RDAContentType

21. rdac: “Manifestation” rdfs: “domain” High-level metadata structures rdam: “has title” rdau: “has title” rdam: “has title proper” rdau: “has title proper” rdfs: “domain” sP sP = rdfs:”sub-property of” Constrained by FRBR (domain) Unconstrained

22. rdac: “Work” rdfs: “domain” Relationship designators rdaw: “has creator” rdau: “has creator” rdaw: “has designer” rdau: “has designer” sP sP = rdfs:”sub-property of” rdac: “Agent” rdfs: “range”

23. EntityPropertiesRangeNo Range Work23520035 Expression23519045 Manifestation21050160 Item504010 Agent22517550 Link-ability Triple clusters Triple chains Literals RelationshipsAttributesDomains Covering all media

24. rdaw: “is video screenplay (work)” rdaw: “is screenplay (work)” rdaw: “is complemented by (work)” rdaw: “has accompanying work relationship with” rdaw: “has related work” Rich detail sub-property ladder

25. rdau: “has voice actor” rdau: “has actor” rdau: “has performer” rdau: “has creator” rdaw: “has creator” Interoperability dcterms: “creator” dc: “creator” ???

26. Thank you!  gordon@gordondunsire.com