1 / 8

RDA in library linked data applications

This presentation by Gordon Dunsire at FSR 2014 in Rome delves into the application of Resource Description and Access (RDA) elements constrained to FRBR, alongside unconstrained versions for non-FRBR contexts. It discusses inferences, interoperability issues, and explores specific properties such as "has translator." The presentation emphasizes the relationships between resources and agents, including the impact of language on the expression of works. Attendees will gain insights into the semantic constraints involved and the challenges of aligning different data classes in library systems.

akasma
Télécharger la présentation

RDA in library linked data applications

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 in library linked data applications Gordon Dunsire Presented at FSR 2014 Rome 27-28 February 2014

  2. Overview • RDA elements constrained to FRBR • Unconstrained versions for non-FRBR applications • Inferences • Maps • Interoperability • Issues

  3. “Expression”@en “has translator”@en “Agent”@en label label label range domain definition subPropertyOf “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 rdae:P20037 rdac:C10002 rdac:C10006 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 definition semantic constraints human + machine inferences

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

  5. dc:format rdam:extent rdau:extent unim:U127__a unim:U215__a m21:M300 isbd:”has extent” dct:extent dct:format rdau:duration bibo:numPages bibo:numVolumes rdam:extentOfText rdau:extentOfText m21:M306__a rdae:duration

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

  7. Issues • Interoperability of classes (domain entities) • Resource; WEMI, Document, Collection • Synchronization of unconstrained properties • “Relates a resource to a resource that describes a described entity.” • Property refinement; e.g. “has translator” • “has translator person” • “has translator family” • “has translator corporate body”

  8. Thank you! • gordon@gordondunsire.com • rdaregistry.info

More Related