I admittedly find the code of the scenarios hard to read, so I was
trying to turn them into pictures, which is more like how I think. In
scenario 4 there is some expression level info:
ex:I rdf:type frbr:Expression ;
rdfs:comment "the international version"@en ;
ex:J rdf:type frbr:Expression ;
rdfs:comment "the US version"@en ;
The two "version" bits of information should be coded as editions (at
least, they were treated that way in the MARC record for this item).
These edition statements are properties of the expressions, just like
the language, date and running time. I think you could even have an
expression that has no properties (OK, maybe I ought to think about
that some more).
So in this case we have:
Expression x
edition: international version
language of expression: en
composer: entity:William Perry
duration: 133 minutes
Expression y
edition: US version
language of expression: en
composer: entity:William Perry
duration: 133 minutes
??: some note about the subtitles - I don't know what the RDA field is
(546 |a U.S. version: Silent with optional Spanish or French
subtitles; closed-captioned.)
I'm not quite sure what in the code hooks together expressions and
their properties. Perhaps it would be clearer with a simpler example
(personally, I don't quite get the scenario as written in English --
not having ever cataloged anything remotely similar to this).
I can understand the simple statements of relationship like:
ex:I frbr:embodiment ex:P
but this one I couldn't parse so I would appreciate some help in
understanding it.
ex:A frbr:realization [ frbr:embodiment [ frbr:part ex:P ] ; ] .
I think what confuses me is that I can't see where the particular
embodiment is identified. (Oh, I would really love a picture of this
whole thing!)
Thanks,
kc
--
-- ---
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596 skype: kcoylenet
mo.: 510-435-8234
------------------------------------
|