Here's how Issue #1 looks on the task group wiki:
Issue #1: Relationship to FRBR Entities
How far is it necessary to go in associating RDA elements to FRBR
entities in the formal representation? Some RDA elements are associated
with more than one FRBR entity, so opting to go without the specific
association we could be introducing both a measure of ambiguity and the
possibility of hindering interoperability. Making the association firmly
introduces some additional complexity in regards to sub-properties,
however.
***************
This one is turning out to be very complex, and I'm feeling the need to
start putting together some initial lists of elements. I did some
analysis of the element list provided by JSC, and there are over 60
elements on their table that aren't associated with a FRBR entity. I'm
thinking that perhaps we need, for the moment, to push aside the FRBR
question, and identify elements and sub-elements without concerning
ourselves about their FRBR role.
Unless someone has a better idea.
I'm willing to stick my neck out with a first list of elements, although
it's hard to talk about them entirely out of context. I could try to
organize them, or we could mark up the JSC list and publish that via
Google Docs.
--
-----------------------------------
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596 skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------
|