Example 3 from the PREMIS Data Dictionary, abbreviated

What appears in the record:
<?xml version="1.0" encoding="UTF-8"?>
<object xmlns="http://www.loc.gov/standards/premis/v1"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.loc.gov/standards/premis/v1 
http://www.loc.gov/standards/premis/v1/Object-v1-1.xsd">
     <objectIdentifier>
         <objectIdentifierType>LATMD</objectIdentifierType>
         <objectIdentifierValue>FD3OLGGY</objectIdentifierValue> <!-- the 
tar file -->
     </objectIdentifier>
     [...]
     <objectCategory>file</objectCategory>
     [...]
     <relationship>
         <relationshipType>structural</relationshipType>
         <relationshipSubType>has part</relationshipSubType>
         <relatedObjectIdentification>
             <relatedObjectIdentifierType>LATMD</relatedObjectIdentifierType>
             <relatedObjectIdentifierValue>FD3OLGGY/gr-zip 
6/10</relatedObjectIdentifierValue> <!-- the QuarkXPress file -->
             <relatedObjectSequence>1</relatedObjectSequence>
         </relatedObjectIdentification>
     </relationship>
     <relationship>
         <relationshipType>structural</relationshipType>
         <relationshipSubType>has part</relationshipSubType>
         <relatedObjectIdentification>
             <relatedObjectIdentifierType>LATMD</relatedObjectIdentifierType>
             <relatedObjectIdentifierValue>FD3OLGGY/FI.0610.homesales.eps</relatedObjectIdentifierValue> 
<!-- the EPS file -->
             <relatedObjectSequence>2</relatedObjectSequence>
         </relatedObjectIdentification>
     </relationship>
     <relationship>
         <relationshipType>structural</relationshipType>
         <relationshipSubType>has part</relationshipSubType>
         <relatedObjectIdentification>
             <relatedObjectIdentifierType>LATMD</relatedObjectIdentifierType>
             <relatedObjectIdentifierValue>FD3OLGGY/Home 
sales/chartsMay.99</relatedObjectIdentifierValue> <!-- the Macromedia 
FreeHand file -->
             <relatedObjectSequence>3</relatedObjectSequence>
         </relatedObjectIdentification>
     </relationship>
     [...]
</object>

What I'm proposing the schema for the object entity should allow:
<?xml version="1.0" encoding="UTF-8"?>
<object xmlns="http://www.loc.gov/standards/premis/v1"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.loc.gov/standards/premis/v1 
http://www.loc.gov/standards/premis/v1/Object-v1-1.xsd">
     <objectIdentifier>
         <objectIdentifierType>LATMD</objectIdentifierType>
         <objectIdentifierValue>FD3OLGGY</objectIdentifierValue> <!-- the 
tar file -->
     </objectIdentifier>
     [...]
     <objectCategory>file</objectCategory>
     [...]
     <relationship>
         <relationshipType>structural</relationshipType>
         <relationshipSubType>has part</relationshipSubType>
         <relatedObjectIdentification>
             <relatedObjectIdentifierType>LATMD</relatedObjectIdentifierType>
             <relatedObjectIdentifierValue>FD3OLGGY/gr-zip 
6/10</relatedObjectIdentifierValue> <!-- the QuarkXPress file -->
         </relatedObjectIdentification>
         <relationship>
             <relationshipType>structural</relationshipType>
             <relationshipSubType>has part</relationshipSubType>
             <relatedObjectIdentification>
                 <relatedObjectIdentifierType>LATMD</relatedObjectIdentifierType> 

                 <relatedObjectIdentifierValue>FD3OLGGY/FI.0610.homesales.eps</relatedObjectIdentifierValue> 
<!-- the EPS file -->
             </relatedObjectIdentification>
             <relationship>
                 <relationshipType>derivative</relationshipType>
                 <relationshipSubType>has source</relationshipSubType>
                 <relatedObjectIdentification>
                     <relatedObjectIdentifierType>LATMD</relatedObjectIdentifierType> 

                     <relatedObjectIdentifierValue>FD3OLGGY/Home 
sales/chartsMay.99</relatedObjectIdentifierValue> <!-- the Macromedia 
FreeHand file -->
                 </relatedObjectIdentification>
             </relationship>
         </relationship>
     </relationship>
     [...]
</object>

There may be very good reasons for not doing this.  I just wanted to get 
your feedback.

Thanks,
Youn


At 12:07 PM 10/10/2006, you wrote:
>I wonder if you could give us an example that one relationship is
>included in another relationship?
>
>Thanks,
>
>Zhiwu Xie
>
>
>On Fri, 2006-10-06 at 16:07, Youn Noh wrote:
> > For repositories that aren't using METS, I'm wondering if it might not 
> be a
> > good idea to make it possible to represent structural relationships in
> > PREMIS hierarchically by revising the schema for the object entity so that
> > relationship can be a child of relationship.
> >
> > Thank you,
> > Youn
> >
> >
> > Youn Noh
> > Digital Resources Catalog Librarian
> > Catalog Department
> > Yale University Library
> > P.O. Box 208240
> > New Haven, CT 06520-8240