If a text aggregate "is" an expression -- that expression must belong to
SOME work though, right?
And if the individual things inside the aggregate ALSO exist on their
own independently (or in OTHER aggregations)... and you want to model
that (which you may NOT want to spend time modelling in the individual
cases, depending on context)... dont' those individual things inside the
aggregate need to be modelled as expressions (which belong to a work)
themselves?
In general, Jenn has spent more time thinking about these things in
terms of music-related records than even the long discussions on RDA-L,
and I think has even authored a position paper for some body on this
subject?
I am guessing that in musical cataloging, the individual things inside
an aggregate often DO exist on their own independently or in other
aggregations, and for the needs of music patrons, that DOES need to be
modelled, and I don't see how to do it except to call those things works
of their own too? If Symphony X is a work, then it's still a work
when an expression of it is bound together with Symphony's A, B, and C,
right?
Jonathan
Karen Coyle wrote:
Jenn, I can't claim to have spent sufficient time looking at this,
but... are you on the RDA-L list? Because we just went through a very
long discussion there in which we concluded that a text aggregate
(possibly analogous to a sound recording aggregate) is an expression,
not a "set" of separate work/expression entities. Your example implies
the latter, with the aggregate being described only at the
manifestation level. (And now I'm confused as to what the work would
be in something like a text collection, such as an anthology of poems.
Would the anthology be a work?)
kc
Quoting "Riley, Jenn" <[email protected]>:
The Variations/FRBR project at Indiana University
(http://vfrbr.info) is pleased to announce the release of an initial
set of XML Schemas for the encoding of FRBRized bibliographic data.
The Variations/FRBR project aims to provide a concrete testbed for
the FRBR conceptual model, and these XML Schemas represent one step
towards that goal by prescribing a concrete data format that
instantiates the conceptual model. Our project has been watching
recent work to represent the FRBR-based Resource Description and
Access (RDA) element vocabulary in RDF; however, due to the fact
that this work represents RDA data rather than FRBR data directly,
and that much metadata work in libraries currently (though perhaps
not permanently) operates in an XML rather than an RDF environment,
we concluded an XML-based format for FRBR data directly was needed
at this time. We view XML conforming to these Schemas to be one
possible external representation of FRBRized data, and will be
exploring other!
representations (including RDF) in the future. We define
"implementing FRBR," as the conceptual models described in the
companion FRBR and FRAD reports; at this time we are not actively
working on the model defined in the draft FRSAD report. Perhaps the
most notable feature of the Variations/FRBR XML Schemas is their
existence at three "levels": frbr, which embodies faithfully only
those features defined by the FRBR and FRAD reports; efrbr, which
adds additional features we hope will make the data format more
"useful"; and vfrbr, which both contracts and extends the FRBR and
FRAD models to create a data representation optimized for the
description of musical materials and we hope provides a model for
other domain-specific applications of FRBR.
A User Guide with details on the structure of the Schemas and how
they relate to one another may be found at
http://vfrbr.info/schemas/1.0/UserGuide.pdf, and links to all
Schemas and documentation may be found at
http://vfrbr.info/schemas/1.0. We hope this Schema release will lead
to further discussion of FRBR implementation issues within the
community. Comments and questions on the Variations/FRBR Schema
release may be sent to [email protected].
Variations/FRBR is generously funded through a National Leadership
Grant from the Institute of Museum and Library Services
<http://www.imls.gov>.
(And a big kudos goes to the V/FRBR project team:
http://www.dlib.indiana.edu/projects/vfrbr/people/index.shtml.
Thanks to all of you, and especially to Paul, Mark, and Ilias.)
Jenn
========================
Jenn Riley
Metadata Librarian
Digital Library Program
Indiana University - Bloomington
Wells Library W501
(812) 856-5759
www.dlib.indiana.edu
Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com
