1 / 10

RDA: thinking globally, acting globally

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. Failure of top-down approach RDA tools

steve
Download Presentation

RDA: thinking globally, acting globally

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

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

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

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

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

  7. Mapping entities rda: Work isbd:P1193 (has work aspect ) bf: expressionOf rdae:P20231 (has work expressed) bf: Work isbd:P1190 (has expression aspect ) ? rda: Expression rdam:P30139 (has expression manifested) bf: Instance bf: instanceOf rda: Manifestation isbd:P1192 (has manifestation aspect ) marc21: Resource isbd: Resource rdai:P40049 (has manifestation exemplified) rda: Item isbd:P1191 (has item aspect )

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

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

  10. Thank you! • jscchair@rdatoolkit.org • rdaregistry.info • Published RDA element sets • rdvocab.info • Published RDA value vocabularies • https://github.com/RDARegistry/RDA-Vocabularies • Project: versions, issues, feedback

More Related