Thanks for setting this up. Drilling down into the explanations of
Work and Types of Work I can see that in BibFrame Works are Resources,
and therefore can have the properties of Resources as well as
properties specific to Works, and that Types of Work (examples:
Dissertation, Cartographic) include more specific properties as well,
in addition to the properties of Resource and Work.
Could the Types of Work be defined on a different level--less format,
more FRBR? Could FRBR Work and FRBR Expression be types of the
BibFrame Work, with the latter taking over the Language property, or
must all BibFrame Works include the property Language, regardless of
type? Could Integral Work and Aggregated Work (another distinction
from FRBR) be defined in BibFrame as Types of Work? The use case for
the latter would be, say, to differentiate by type between a BibFrame
Work description of Hamlet the play (a FRBR integral work) and a
BibFrame Work description of a critical edition of Hamlet (a FRBR
aggregated work)--to provide different answers to the questions "What
did Shakespeare write?" and "What does the library have by
Are these the sort of things that an RDA profile for BibFrame could
specify? Are these useful questions to be raising?
On Sun, Jan 27, 2013 at 2:28 PM, Kevin Ford <[log in to unmask]> wrote:
> The Library of Congress is pleased to announce the publication of
> http://bibframe.org/ - a new website for detailed information about the
> in-development, draft BIBFRAME vocabulary. It also includes
> demonstrations of the BIBFRAME model from MARC bibliographic records from
> all of the experimenters' collections, including the Library of Congress.
> These are displayed in a human-friendly manner with Exhibit3, a light-weight
> publishing framework for data. The source MARC/XML data, resulting BIBFRAME
> resources, and Exhibit JSON are available for download.
> The website also provides services that permit librarians interested in what
> bibliographic resources might look like conforming to the BIBFRAME data
> model to view MARC/XML records from the Library of Congress's main database
> along side BIBFRAME resources resulting from the most current
> transformation. Another tool allows users to submit their own MARC/XML
> records for transformation. The data resulting from these transformations
> are also displayed with Exhibit3 and the resulting data available for download.
> It is important to understand that the vocabulary is a draft. It will
> continue to evolve, sometimes rapidly in the coming months. The code
> performing the transformations is also a work in progress. Users may note
> that the names of classes/properties/elements/attributes in the vocabulary
> do not match those seen in the BIBFRAME data. We will be working in the
> next couple of weeks to bring the names of
> classes/properties/elements/attributes seen in the resulting data into
> alignment with the terms found in the vocabulary.
> We encourage and want constructive feedback on the vocabulary and data
> transformations. All are invited to join the conversation. This listserv
> is the best place for those discussions. The vocabulary is designed to get
> us started, but, as a community effort, your valuable feedback is essential
> (and has been already - thank you).
> One last note: the website is also very much a work in progress. There may
> be bugs (errors) with the website - a result of rapid, iterative development
> - and until we can establish a mechanism to report such errors, please feel
> free to email Kevin Ford ([log in to unmask]).
> Kevin Ford
> Network Development and MARC Standards Office
> Library of Congress
> Washington, DC
Stephen Hearn, Metadata Strategist
Technical Services, University Libraries
University of Minnesota
160 Wilson Library
309 19th Avenue South
Minneapolis, MN 55455