RDA in library linked data applications Gordon Dunsire
RDA in library linked data applications Gordon Dunsire Presented at FSR 2014 Rome 27 -28 February 2014
Overview v. RDA elements constrained to FRBR v. Unconstrained versions for non-FRBR applications v. Inferences v. Maps v. Interoperability v. Issues
“Expression”@en “has translator”@en label rdac: C 10006 domain definition “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 rdae: P 20037 “Agent”@en label range sub. Property. Of rdac: C 10002 “Relates a resource to an agent rdau: P 60385 contributing to a resource by expressing the original text of the semantic definition resource in a constraints language different from that of the human + machine original resource. ”@en inferences
ex: 1 rdae: P 20037 ex: 1 ex: 2 ex: 1 rdf: type “thing 1 has translator thing 2” ex: 2 rdac: C 10006 rdac: C 10002 rdau: P 60385 ex: 2 “thing 1 is a Expression” “thing 2 is a Agent” “thing 1 has translator thing 2”
dct: format dct: extent unim: U 215__a m 21: M 300 rdam: extent rdau: duration rdau: extent m 21: M 306__a rdam: extent. Of. Text rdau: extent. Of. Text rdae: duration isbd: ”has extent” bibo: num. Volumes bibo: num. Pages unim: U 127__a
ex: 3 rdam: extent. Of. Text “xvii, 323 pages”@en rdau: extent. Of. Text ex: 3 rdam: extent dct: extent “xvii, 323 pages”@en dct: format rdau: extent ex: 4 m 21: M 300 “ 1 map : col. ; 30 x 55 cm”@en ex: 4 rdau: extent dct: extent “ 1 map : col. ; 30 x 55 cm”@en dct: format
Issues v. Interoperability of classes (domain entities) v. Resource; WEMI, Document, Collection v. Synchronization of unconstrained properties v“Relates a resource to a resource that describes a described entity. ” v. Property refinement; e. g. “has translator” v“has translator person” v“has translator family” v“has translator corporate body”
Thank you! vgordon@gordondunsire. com vrdaregistry. info
- Slides: 8