Quoting Casey A Mullin <cmul...@stanford.edu>:
[I'm behind on this thread, which raced forth over the weekend. Still catching up...]

In the mean time, I'll respond to Karen and Heidrun's comments. To be clear, > I'm not suggesting certain works/expressions be "flagged" as primary or secondary. What I'm referring to is the idea that certain works/expressions
> need not even be identified in the data. According to FRBR, we may know they
exist, but identifying them (whether through access points, identifiers, etc.) is of marginal utility in a case like this.


kc: Right, none of what we're talking about relates to parts or secondary works that are not identified as such in the cataloging. We are concerned about what to do if you *do* wish to bring them out in the description.

If someone wished to come back
later and identify the introduction as a work in its own right, they could do that.As Karen pointed out, this can seem "devilish", but only when trying to
 > envision it in a MARC environment.

kc: Nothing devilish at all in MARC: you add a 7xx for it. It's only devilish in a FRBR-based environment.


[Hide Quoted Text]

As for Karen's other question:
<snip>

Manifestation 1 is embodiment of Expression A
Manifestation 1 is embodiment of Expression B
Manifestation 1 is embodiment of Expression C
something else occurs to me about this model: there is no place for a title proper for each of the expressions -- If A is the whole, and B and C are individual works in A, then where are the titles proper for B and C?
</snip>

Title Proper is a Manifestation attribute. Expressions have no titles, per se. I would say that if an augmenting Work (like a preface) didn't have a title, that's all the more reason to forego identifying it. If you did, you'd need to devise one in RDA.


kc: Exactly. So how to you do this? that's the question we are asking. A title proper can only be defined within a FRBR manifestation entity. In this case, what does your FRBR manifestation contain, given that the the part exists physically only within that aggregate manifestation? You would end up with two manifestation entities for the same physical manifestation: one with the title proper of the part, and one for the actual item in hand. Honestly, I'd like to see what this looks like. It's ok for it to be a bit sketchy, but use, if you can, the RDA properties (from http://rdvocab.info). That would really help! (You don't need to use the URIs -- the element names will be fine.)

kc

Reply via email to