RDA thinking globally acting globally Gordon Dunsire Presented

RDA: thinking globally, acting globally Gordon Dunsire Presented at International Developments in Library Linked Data: Think Globally, Act Globally – Part Two: an ALCTS Program, ALA Annual, Las Vegas, USA, 28 Jun 2014

Overview v. Failure of top-down approach v. RDA tools v. Case: intended audience v. Mapping the focus of description v. Top-down, bottom-up issues

Acting locally Universal Bibliographic Control Thinking globally KOS++ FR: Functional ISBD: International Standard BIBFRAME: Bibliographic Requirements Bibliographic Description Bib. O: Framework DC: Dublin Core RDA: Resource Bibliographic CRM: Conceptual MARC 21 Description schema. org Ontology Reference Model and Access UNIMARC Confusing tongues? RDF Say what we mean

Element set + Relationship designators For un. FRBRized applications 30 million (partial) examples Links to other vocabularies

Globalizing RDA linked data Language-specific labels and definitions (for humans) Language-neutral URIs (immutable) Language-specific URIs (for developers)

isbdu: “has note on use or audience” Unconstrained versions isbd: “has note on use or audience” rdau: “Intended audience” Value vocabularies (KOS) Broader/narrower/same? rdfs: sub. Property. Of rdaw: “Intended audience” m 21: “Target audience of …” m 21: e frbrer: “has intended audience” bf: “Intended audience” MPAA: NC-17? BBFC: 18? dct: “audience” m 21: “Target audience” Map of “Audience” Element sets (schema) schema: “audience” “adult” pbcore: adult “adult” umarc: m “adult, general” umarc: k “adult, serious”

Mapping entities bf: expression. Of bf: Work marc 21: Resource ? bf: instance. Of bf: Instance rda: Work isbd: P 1193 (has work aspect ) rdae: P 20231 (has work expressed) rda: Expression isbd: P 1190 (has expression aspect ) rdam: P 30139 (has expression manifested) rda: Manifestation isbd: Resource isbd: P 1192 (has manifestation aspect ) rdai: P 40049 (has manifestation exemplified) rda: Item isbd: P 1191 (has item aspect )

Top-down v Examine local schema v Identify the common elements v Create a common/global element set (RDF) v Refine the global element set to connect down (map) to specific local elements v Issues v. Common elements may not cover the same space as local elements v. Refinement not possible v. Common elements have to be augmented v. Favours the global over the local v. Encourages a good-enough approach

Bottom-up v. Publish the local schema(s) in RDF v. Map local elements from different schema to lowest common (dumber) elements – add new elements if necessary v. Continue until all local schema have been mapped v. Issues v. Multiplicity of RDF element sets v. Frequent overlap and redundancy v. Local management resources

Thank you! vjscchair@rdatoolkit. org vrdaregistry. info v. Published RDA element sets vrdvocab. info v. Published RDA value vocabularies vhttps: //github. com/RDARegistry/RDAVocabularies v. Project: versions, issues, feedback