In hindsight, I would omit the word "detailed," which seems to be the reason
for quoting that sentence. That would have left "in-development, draft
BIBFRAME vocabulary" as the focus, probably, and brings me to my point (and
a form of reply to your last two questions).
It is not complete. Far from it. There is much more than just
content/media/carrier terms missing presently. But, in the interest of
making this available and in the interest of engendering conversation and
feedback, we wanted to publish a complementary vocabulary for the high-level
document that preceded what you find at http://bibframe.org/vocab/ .
What's somewhat mystifying with respect to your message is the very strong
suggestion I received upon reading your email that you believe the (draft,
in-development) vocabulary be interpreted as a completed work or effort
versus the foundation for a much more detailed, granular vocabulary to come.
It is the latter, not the former. It is important the community understand
that.
Cordially,
Kevin
On Sun, 27 Jan 2013 14:25:42 -0800, J. McRee Elrod <[log in to unmask]> wrote:
>>http://bibframe.org/ - a new website for detailed information about the
>>in-development, draft BIBFRAME vocabulary.
>
>Interesting.
>
>I assume the demonstration displays are not determined by the Bibframe
>markup? I would find the displays awkward to say the least. Why no
>punctuation in imprint? The break up of collation is confusing, e.g.,
>why size before pagination, and why ISBN before either? I would find
>a simple ISBD display far easier to comprehend. Let's don't reinvent
>a well working wheel.
>
>The Bibframe markup seems to be less granular than MARC, e.g., no code
>for GMD. How would content/media/carrier terms be automatically
>substituted for GMD, if GMD is not separately coded?
>
>Nowhere do I see fixed field information preserved; wouldn't at least
>some of that information be needed for determining RDA media terms?
>
>
>
> __ __ J. McRee (Mac) Elrod ([log in to unmask])
> {__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
> ___} |__ \__________________________________________________________
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 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
>>
>=========================================================================
