This document discusses the development of RDA vocabularies based on FRBR. It provides a brief history of the RDA vocabulary task group and describes how they have modeled RDA properties and relationships using semantic web techniques. Properties are declared at different levels, with some directly related to FRBR entities and others more generalized for extension. Challenges remain in completing the modeling work and relating it to the RDA guidance text.

1. Diane I. Hillmann Metadata Management Associates/Information Institute of Syracuse RDA Vocabulary Developments Based on FRBR

2. A brief history A structural tour, including: Rationale and decision making Use of domains and ranges to express FRBR structure Potential for extension Moving towards completion What we’ve learned Setting the Stage 10/26/10 2 ASIS&T-2010

3. Met at the British Library April 30/May 1, 2007 The participants agreed that DCMI and the Joint Steering Committee for the Development of RDA should work together to: Develop an RDA Element Vocabulary Expose RDA Value Vocabularies Develop an RDA Application Profile, based on FRBR and FRAD The first two are largely complete; the third is started Still negotiating review process 3 Task Group History 10/26/10 ASIS&T-2010

4. Property and value vocabularies registered on the Open Metadata Registry (formerly the NSDL Registry): http://metadataregistry.org/rdabrowse.htm ‘FRBR in RDA’ Vocabulary declared as classes RDA Properties declared as a ‘generalized’ vocabulary, with no explicit relationship to FRBR entities Bounded subproperties for the generalized elements explicitly related to FRBR entities (using ‘domain’) Structure: Rationale & Decisions 10/26/10 4 ASIS&T-2010

5. Property (Generalized, no FRBR relationship) Semantic Web Subproperty (with relationship to one FRBR entity) FRBR Entity The Simple Case: One Property-- One FRBR Entity Library Applications 10/26/10 5 ASIS&T-2010

6. Book format Semantic Web Book format (Manifestation) Manifestation The Simple Case: One Property-- One FRBR Entity Library Applications 10/26/10 6 ASIS&T-2010

7. 10/26/10 ASIS&T-2010 7 http://RDVocab.info/Elements/bookFormatManifestation

9. Relationships in Appendix J actually include the name of the FRBR entity in the name and have separate definitions (we re-used this strategy for the FRBR-bounded properties)

10. Other properties and sub-properties appear multiple times in the text and ERDs, with the same definitions and no indication that they might be repeated elsewhere (we consolidated these)10/26/10 8 ASIS&T-2010 More Complex Relationships

11. Property (Generalized, no FRBR relationship) Semantic Web Subproperty (with relationship to one FRBR entity) FRBR Entity Subproperty (with relationship to one FRBR entity) FRBR Entity The Not-So-Simple Case: One Property—more than One FRBR Entity Library Applications 10/26/10 9 ASIS&T-2010

12. Extent Semantic Web Extent (Manifestation) FRBR Manifestation Extent (Item) FRBR Item The Not-So-Simple Case: One Property—more than One FRBR Entity Library Applications 10/26/10 10 ASIS&T-2010

13. 10/26/10 ASIS&T-2010 11

15. This work provided a template for the registration of the role terms in RDA (in Appendix I) and, by extension, the other RDA relationships

16. Role and relationship properties are registered at the same level as elements, rather than as attributes (as MARC does with relators, and RDA does in its XML)10/26/10 12 ASIS&T-2010 Roles: Attributes or Properties?

17. Mapping, Etc. “Super” Property Semantic Web Subproperty (Generalized, no FRBR relationship) Subproperty (with relationship to one FRBR entity) FRBR Entity The Roles Case: Properties, Subproperties and FRBR Entities Library Applications 10/26/10 13 ASIS&T-2010

18. Mapping, Etc. RDA:Creator Semantic Web RDArole:Composer RDArole:Composer (Work) Work The Roles Case: Properties, Subproperties and FRBR Entities Library Applications 10/26/10 14 ASIS&T-2010

19. The inclusion of generalized properties provides a path for extension of RDA into specialized library communities and non-library communities They may have a different notion of how FRBR ‘aggregates’, for example, a colorized version of a film may be viewed as a separate work They may not wish to use FRBR at all They may have additional properties to include, that have a relationship to the RDA properties Extension 10/26/10 15 ASIS&T-2010

20. RDA:adaptedAs hasSubproperty RDA:adaptedAsARadioScript 10/26/10 16 ASIS&T-2010

21. RDA:adaptedAs hasSubproperty RDA:adaptedAsARadioScript hasSubproperty KidLit:adaptedAsAPictureBook 10/26/10 17 ASIS&T-2010

22. RDA:adaptedAs hasSubproperty RDA:adaptedAsARadioScript hasSubproperty hasSubproperty KidLit:adaptedAsAPictureBook KidLit:adaptedAsAChapterBook 10/26/10 18 ASIS&T-2010

23. Completing the hierarchies, both generalized and FRBR-bounded Elements and Relationships need to have bounded hierarchies built (generalized hierarchies complete) Roles need generalized properties created JSC review incomplete, for both properties and vocabularies Status designations need to be updated from ‘New—proposed’ to ‘Published’ Completing the Vocabularies 10/26/10 19 ASIS&T-2010

25. This provides exciting opportunities to relate all the vocabularies togetherRemaining Issues 10/26/10 20 ASIS&T-2010

26. We wrote about the decisions we made for RDA in DLib: http://dlib.org/dlib/january10/hillmann/01hillmann.html Need to continue to disclose what we’ve learned and work on building best practices documentation in this environment What We’ve Learned 10/26/10 21 ASIS&T-2010

27. DCMI/RDA Task Group Wiki: http://dublincore.org/dcmirdataskgroup/ RDA Vocabularies: http://metadataregistry.org/rdabrowse.htm Diane: metadata.maven@gmail.com Gordon: gordon@gordondunsire.com Please join us and participate! Links and Contact Info 10/26/10 22 ASIS&T-2010