Would it be stretching the rules too much to use the FILEID on a <fptr>
to point at a fileGrp ID rather than at a file ID?  

The task that I'm working on is managing a set of versions of a single
file (object), not a set of files that make up a version.  My first take
on this would be something like this:

<fileGrp ID="fileGrp1">
  <file ID="file1v1" USE="obsolete"/>
  <file ID="file1v2" USE="active"/>
...
<structMap>
  <div>
     <filePtr FILEID="fileGrp1">
...

But the documentation suggests that FILEID should point to <file> and
doesn't mention <fileGrp> as a possibility.  It seems a bit verbose to
repeat everything in the StructMap like this:

<fileGrp ID="fileGrp1">
  <file ID="file1v1" USE="obsolete"/>
  <file ID="file1v2" USE="active"/>
...
<structMap>
  <div>
     <filePtr FILEID="file1v1">
  </div>
  <div>
     <filePtr FILEID="file1v2"> 
  </div>
...

But I'm willing to do it if it would be better METS practice.

I would prefer to insert new files only in the fileGrp section and in
appropriate metadata sections when there has been no change in the
actual structure.  Hence my desire to point from <filePtr> to <fileGrp>
rather than <file> 

Evan Owens

==========================================
Evan Owens ([log in to unmask]) 
Chief Technology Officer
Ithaka Electronic-Archiving Initiative 
228 Alexander Street 
Princeton, NJ 08540-7102 
Phone: 609 258-8230 
Fax: 609 258-5778 
==========================================