ASIS&T 2010

2,600 views
2,553 views

Published on

Presentation at ASIS&T, Tuesday, Oct. 26, as part of a panel on FRBR research and implementation.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,600
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ASIS&T 2010

  1. 1. Diane I. Hillmann<br />Metadata Management Associates/Information Institute of Syracuse<br />RDA Vocabulary Developments Based on FRBR<br />
  2. 2. A brief history<br />A structural tour, including:<br />Rationale and decision making<br />Use of domains and ranges to express FRBR structure<br />Potential for extension<br />Moving towards completion<br />What we’ve learned<br />Setting the Stage<br />10/26/10<br />2<br />ASIS&T-2010<br />
  3. 3. Met at the British Library April 30/May 1, 2007<br />The participants agreed that DCMI and the Joint Steering Committee for the Development of RDA should work together to:<br />Develop an RDA Element Vocabulary<br />Expose RDA Value Vocabularies<br />Develop an RDA Application Profile, based on FRBR and FRAD<br />The first two are largely complete; the third is started<br />Still negotiating review process<br />3<br />Task Group History<br />10/26/10<br />ASIS&T-2010<br />
  4. 4. Property and value vocabularies registered on the Open Metadata Registry (formerly the NSDL Registry): http://metadataregistry.org/rdabrowse.htm<br />‘FRBR in RDA’ Vocabulary declared as classes<br />RDA Properties declared as a ‘generalized’ vocabulary, with no explicit relationship to FRBR entities<br />Bounded subproperties for the generalized elements explicitly related to FRBR entities (using ‘domain’)<br />Structure: Rationale & Decisions<br />10/26/10<br />4<br />ASIS&T-2010<br />
  5. 5. Property (Generalized, no FRBR relationship)<br />Semantic<br />Web<br />Subproperty (with relationship to one FRBR entity)<br />FRBR Entity<br />The Simple Case: <br />One Property-- <br />One FRBR Entity<br />Library Applications<br />10/26/10<br />5<br />ASIS&T-2010<br />
  6. 6. Book format<br />Semantic<br />Web<br />Book format (Manifestation)<br />Manifestation<br />The Simple Case: <br />One Property-- <br />One FRBR Entity<br />Library Applications<br />10/26/10<br />6<br />ASIS&T-2010<br />
  7. 7. 10/26/10<br />ASIS&T-2010<br />7<br />http://RDVocab.info/Elements/bookFormatManifestation<br />
  8. 8. <ul><li>Some properties related to more than one FRBR entity
  9. 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. 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)</li></ul>10/26/10<br />8<br />ASIS&T-2010<br />More Complex Relationships<br />
  11. 11. Property (Generalized, no FRBR relationship)<br />Semantic<br />Web<br />Subproperty (with relationship to one FRBR entity)<br />FRBR Entity<br />Subproperty (with relationship to one FRBR entity)<br />FRBR Entity<br />The Not-So-Simple Case: <br />One Property—more than<br />One FRBR Entity<br />Library Applications<br />10/26/10<br />9<br />ASIS&T-2010<br />
  12. 12. Extent<br />Semantic<br />Web<br />Extent (Manifestation)<br />FRBR Manifestation<br />Extent (Item)<br />FRBR Item<br />The Not-So-Simple Case: <br />One Property—more than<br />One FRBR Entity<br />Library Applications<br />10/26/10<br />10<br />ASIS&T-2010<br />
  13. 13. 10/26/10<br />ASIS&T-2010<br />11<br />
  14. 14. In 2005, the DC Usage Board worked with LC to build a formal representation of the MARC Relators so that these terms could be used with DC<br /><ul><li>These have been superseded by the ‘new’ id.loc.info version, without the relationships to DC terms (has been pushback on this decision!)
  15. 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. 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)</li></ul>10/26/10<br />12<br />ASIS&T-2010<br />Roles: Attributes or Properties?<br />
  17. 17. Mapping,<br />Etc.<br />“Super” Property <br />Semantic<br />Web<br />Subproperty (Generalized, no FRBR relationship)<br />Subproperty (with relationship to one FRBR entity)<br />FRBR Entity<br />The Roles Case: <br />Properties, Subproperties<br />and FRBR Entities<br />Library Applications<br />10/26/10<br />13<br />ASIS&T-2010<br />
  18. 18. Mapping,<br />Etc.<br />RDA:Creator<br />Semantic<br />Web<br />RDArole:Composer<br />RDArole:Composer (Work)<br />Work<br />The Roles Case: <br />Properties, Subproperties<br />and FRBR Entities<br />Library Applications<br />10/26/10<br />14<br />ASIS&T-2010<br />
  19. 19. The inclusion of generalized properties provides a path for extension of RDA into specialized library communities and non-library communities<br />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<br />They may not wish to use FRBR at all<br />They may have additional properties to include, that have a relationship to the RDA properties<br />Extension <br />10/26/10<br />15<br />ASIS&T-2010<br />
  20. 20. RDA:adaptedAs<br />hasSubproperty<br />RDA:adaptedAsARadioScript<br />10/26/10<br />16<br />ASIS&T-2010<br />
  21. 21. RDA:adaptedAs<br />hasSubproperty<br />RDA:adaptedAsARadioScript<br />hasSubproperty<br />KidLit:adaptedAsAPictureBook<br />10/26/10<br />17<br />ASIS&T-2010<br />
  22. 22. RDA:adaptedAs<br />hasSubproperty<br />RDA:adaptedAsARadioScript<br />hasSubproperty<br />hasSubproperty<br />KidLit:adaptedAsAPictureBook<br />KidLit:adaptedAsAChapterBook<br />10/26/10<br />18<br />ASIS&T-2010<br />
  23. 23. Completing the hierarchies, both generalized and FRBR-bounded<br />Elements and Relationships need to have bounded hierarchies built (generalized hierarchies complete)<br />Roles need generalized properties created<br />JSC review incomplete, for both properties and vocabularies<br />Status designations need to be updated from ‘New—proposed’ to ‘Published’<br />Completing the Vocabularies<br />10/26/10<br />19<br />ASIS&T-2010<br />
  24. 24. How do these relate to the RDA guidance text?<br />Who will maintain these? How will they be kept in sync with the text? <br />Will the governance model for these be the same as the text? Who decides?<br />How can we use these vocabularies effectively?<br />What else do we need to identify?<br />How should we continue this work?<br /><ul><li>IFLA has followed suit using the Open Metadata Registry to add the ‘official’ FRBR entities, FRAD, and ISBD
  25. 25. This provides exciting opportunities to relate all the vocabularies together</li></ul>Remaining Issues<br />10/26/10<br />20<br />ASIS&T-2010<br />
  26. 26. We wrote about the decisions we made for RDA in DLib: http://dlib.org/dlib/january10/hillmann/01hillmann.html<br />Need to continue to disclose what we’ve learned and work on building best practices documentation in this environment<br />What We’ve Learned<br />10/26/10<br />21<br />ASIS&T-2010<br />
  27. 27. DCMI/RDA Task Group Wiki: http://dublincore.org/dcmirdataskgroup/<br />RDA Vocabularies: http://metadataregistry.org/rdabrowse.htm<br />Diane: metadata.maven@gmail.com<br />Gordon: gordon@gordondunsire.com<br />Please join us and participate!<br />Links and Contact Info<br />10/26/10<br />22<br />ASIS&T-2010<br />

×