Upload
diane-i-hillmann
View
2.434
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Presentation at ASIS&T, Tuesday, Oct. 26, as part of a panel on FRBR research and implementation.
Citation preview
Diane I. Hillmann
Metadata Management Associates/Information Institute of Syracuse
RDA Vocabulary Developments Based on
FRBR
2ASIS&T-2010
A brief historyA structural tour, including:
Rationale and decision makingUse of domains and ranges to express FRBR
structurePotential for extension
Moving towards completionWhat we’ve learned
Setting the Stage
10/26/10
3ASIS&T-2010
Met at the British Library April 30/May 1, 2007The participants agreed that DCMI and the
Joint Steering Committee for the Development of RDA should work together to:Develop an RDA Element VocabularyExpose RDA Value VocabulariesDevelop an RDA Application Profile, based on
FRBR and FRADThe first two are largely complete; the third is
startedStill negotiating review process
Task Group History
10/26/10
4ASIS&T-2010
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 classesRDA 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
ASIS&T-2010 5
Property (Generalized, no FRBR relationship)
Subproperty (with relationship to one FRBR entity)
FRBR Entity
SemanticWeb
Library ApplicationsThe Simple Case:
One Property-- One FRBR Entity
10/26/10
ASIS&T-2010 6
Book format
Book format (Manifestation)
Manifestation
SemanticWeb
Library ApplicationsThe Simple Case:
One Property-- One FRBR Entity
10/26/10
ASIS&T-2010 710/26/10
http://RDVocab.info/Elements/bookFormatManifestation
8ASIS&T-2010
Some properties related to more than one FRBR entity
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)
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
More Complex Relationships
ASIS&T-2010 9
Property (Generalized, no FRBR relationship)
Subproperty (with relationship to one FRBR entity)
Subproperty (with relationship to one FRBR entity)
FRBR Entity
FRBR Entity
SemanticWeb
Library ApplicationsThe Not-So-Simple Case: One Property—more than
One FRBR Entity10/26/10
ASIS&T-2010 10
Extent
Extent (Item)
Extent (Manifestation)
FRBR Item
FRBR Manifestation
SemanticWeb
Library ApplicationsThe Not-So-Simple Case: One Property—more than
One FRBR Entity10/26/10
ASIS&T-2010 1110/26/10
12ASIS&T-2010
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 DCThese have been superseded by the ‘new’ id.loc.info
version, without the relationships to DC terms (has been pushback on this decision!)
This work provided a template for the registration of the role terms in RDA (in Appendix I) and, by extension, the other RDA relationshipsRole 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
Roles: Attributes or Properties?
ASIS&T-2010 13
“Super” Property
Subproperty (with relationship to one FRBR entity)
Subproperty (Generalized, no FRBR relationship)
FRBR Entity
SemanticWeb
Library Applications The Roles Case: Properties, Subproperties
and FRBR Entities
Mapping,Etc.
10/26/10
ASIS&T-2010 14
RDA:Creator
RDArole:Composer (Work)
RDArole:Composer
Work
SemanticWeb
Library Applications The Roles Case: Properties, Subproperties
and FRBR Entities
Mapping,Etc.
10/26/10
15ASIS&T-2010
The inclusion of generalized properties provides a path for extension of RDA into specialized library communities and non-library communitiesThey 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 allThey may have additional properties to include,
that have a relationship to the RDA properties
Extension
10/26/10
ASIS&T-2010 16
RDA:adaptedAs
RDA:adaptedAsARadioScript
hasSubprope
rty
10/26/10
ASIS&T-2010 17
RDA:adaptedAs
RDA:adaptedAsARadioScript
KidLit:adaptedAsAPictureBook
hasSubproperty
hasSubprope
rty10/26/10
ASIS&T-2010 18
RDA:adaptedAs
RDA:adaptedAsARadioScript
KidLit:adaptedAsAPictureBook
hasSubproperty
hasSubprope
rty
KidLit:adaptedAsAChapterBook
hasS
ubprop
e
rty
10/26/10
19ASIS&T-2010
Completing the hierarchies, both generalized and FRBR-boundedElements and Relationships need to have
bounded hierarchies built (generalized hierarchies complete)
Roles need generalized properties createdJSC review incomplete, for both properties
and vocabulariesStatus designations need to be updated from
‘New—proposed’ to ‘Published’
Completing the Vocabularies
10/26/10
20ASIS&T-2010
How do these relate to the RDA guidance text?Who will maintain these? How will they be kept in sync
with the text? Will the governance model for these be the same as the
text? Who decides?How can we use these vocabularies effectively?
What else do we need to identify?How should we continue this work?
IFLA has followed suit using the Open Metadata Registry to add the ‘official’ FRBR entities, FRAD, and ISBDThis provides exciting opportunities to relate all the
vocabularies together
Remaining Issues
10/26/10
21ASIS&T-2010
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
22ASIS&T-2010
DCMI/RDA Task Group Wiki: http://dublincore.org/dcmirdataskgroup/
RDA Vocabularies: http://metadataregistry.org/rdabrowse.htm
Diane: [email protected]: [email protected]
Please join us and participate!
Links and Contact Info
10/26/10