Hi Yann,

On Mar 23, 2005, at 9:41 AM, Yann Nicolas wrote:

> Bonjour,
>
> I would like to associate descriptive metadata, not with parts of an
> object
> (via an attribute in a div of the map), but to versions of it (e.g.
> metadata for the draft and metadata for the final text ; metadata for
> the
> PDF and metadata for the XML edition). In other terms, some of the
> descriptive metadata should be pointed by the FRBR-work (maximal set of
> files), some by each FRBR-expression (relevant set of files), and some
> by
> each FRBR-manifestation (relevant set of files).
> But it seems impossible to associate a group of files with a
> descriptive
> metadata section.
> Is there an other method to express this FRBR structure, at least in
> the
> simple case that my explanation implies ?

There are a couple of ways to solve this problem:

1. You could express each of the FRBR levels as separate METS documents
and use the <mptr> element to point from the higher to lower levels.
So you'd
have a METS document for the work, which would contain a <structMap>
with
<div> elements for each expression.  Those expression <div> elements
would
have <mptr>s identifying other METS documents for each individual
expression.
The expression METS documents would have <structMaps> with
<div>s/<mptrs>
pointing to METS documents for each manifestation.  You could put
<descMD>
records appropriate to each work/expression/manifestation in their
respective
METS documents.

2. If you don't want to establish a hierarchy of METS documents for your
object, you can still accomplish much the same thing in a single METS
document's <structMap>, e.g.,

<structMap>
      <div TYPE="FRBR WORK" DMDID="lDREF for appropriate desc. metadata
record here">
           <div TYPE="FRBR EXPRESSION" DMDID="IDREF for more desc.
metadata">
                <div TYPE="FRBR EXPRESSION" DMDID="yet more desc.
metadata" LABEL="XML version">
                     <fptr></fptr>
                </div>
                <div TYPE="FRBR EXPRESSION" DMDID="even more desc.
metadata" LABEL="PDF version">
                     <fptr></fptr>
                </div>
           </div>
      </div>
<structMap>

3. Alternatively, you could have the skip the <div>s for the FRBR
expression level in case 2
above, and rely on the DMDID attribute on the individual file elements
in the <fileSec> to point
to appropriate descriptive metadata records.  For expressions with a
large number of component
files, you'll end up repeating the IDREF information linking each
<file> element to the same desc. metadata
record for the expression.  Then you'd have something like this:

<structMap>
      <div TYPE="FRBR WORK" DMDID="IDREF for appropriate desc. metadata
record here">
           <div TYPE="FRBR EXPRESSION" DMDID="IDREF for more desc.
metadata">
                <fptr FILEID="XML_Version" />
               <fptr FILEID="PDF_Version" />
           </div>
      </div>
<structMap>

<fileSec>
      <fileGrp>
           <file ID="XML_Version" DMDID="IDREF for yet more desc.
metadata" />
      </fileGrp>
      <fileGrp>
          <file ID="PDF_Version" DMDID="IDREF for even more desc.
metadata" />
      </fileGrp>
</fileSec>


Jerome McDonough
Digital Library Development Team Leader
Elmer Bobst Library, New York University
70 Washington Square South
New York, NY 10012
(212) 998-2425
[log in to unmask]