As it happens I have a lot of examples, and they're even written up, though not specifically as formal 'use cases'. You may recall that in 2007 DCMI collaborated with JSC on the building of the RDA Vocabularies. There was quite a bit of good stuff gathered as part of that activity, which is now on the wiki of the successor group, the DCMI Bibliographic Metadata Task Group ( At the bottom of that page is a like to the historical archives of the group.

The specific thing that I believe would help is a section called "Cataloger Scenarios":

There are ten scenarios, contributed by a variety of people, and they generated a fair amount of discussion, most of which is still available through the JISC archives for the list (which is the same list as the original group used). As I'm sure you remember, catalogers inspired to supply examples contribute the knottiest things they know about, based on their experiences with the materials they catalog. So you'll note that there are a lot of special format scenarios.

Bon appetit!


P.S. BTW, one of the best things about RDA is the relationships, all of which have URIs: (relationships between Works Expressions Manifestations Items (roles). These vocabularies have just over 750 properties, but some are complicated by the necessity of describing properties separately when they relate to different classes.

On Tue, Nov 27, 2012 at 2:51 PM, Eric Miller <[log in to unmask]> wrote:
Hi Diane, Philippe,

In this draft model, the aggregation would be done at the (BIBFRAME) Work level. A set of collected stories, for example, would in fact be a Collection (Work) of other Works. Works are typed and a Collection is just one kind of Work. What connects these Works together are a set of defined relationships that create a Web of Works. The paperback (or hardback, or …) version of this collected Work would be instances of this Collection (but there may be other instances associated with the individual Works as well).

Whats missing from this primer are more detailed use cases and example applications which help demonstrate more concretely this approach. I'm hopeful these will be made available soon. Nothing helps ground any model (and serialization, vocabulary, constraint layer, HTTP services, etc.) like practical examples.

Diane, as you know no good idea goes unpunished ;), if there are specific examples that you would be willing to suggest that would be extremely helpful. I can't claim a quick turn around, but I'd be happy to give a go at representing these via BIBFRAME.


On Nov 26, 2012, at 10:34 AM, Diane Hillmann <[log in to unmask]> wrote:

> Philippe:
> I had the same response, immediately thinking of things like collected stories (single or multiple authors) and serial issues. These are certainly fairly common in bibliographic metadata, and were not well handled in MARC or MODS. The FRBR model, though admittedly a complex beast, accommodated these materials, and gave some hope that there could be ways of handling those kinds of materials in ways that a machine could understand, rather than (as usual) depending on the human user to figure it out.
> Diane Hillmann
> Sent from my iPad
> On Nov 26, 2012, at 9:13 AM, "LE PAPE, Philippe" <[log in to unmask]> wrote:
>> Dear Everybody,
>> Colleagues have already expressed their concern about the vanishing of FRBR Expression entity in Zepheira's "BIBFRAME" model, but I was rather puzzled by this:
>> "Each BIBFRAME Instance is an instance of one and,only one BIBFRAME Work." P. 10.
>> What about (FRBR) Manifestations embodying more than one (FRBR) Work then? Will there be something like compound (BIBFRAME) instances? Or will the aggregation be done at the (BIBFRAME) Work level?
>> Ph.
>> --
>> Philippe Le Pape
>> Mission Normalisation
>> 227 avenue Professeur-Jean-Louis-Viala
>> Tél.  33 (0)4 67 54 84 67
>> Fax  33 (0)4 67 54 84 14