Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Code Block
xml
xml
<didl:Item>

 

Code Block
xml
xml
<didl:Descriptor> <didl:Statement mimeType="application/xml"> 
<dip:ObjectType> info:eu-repo/semantics/descriptiveMetadata</dip:ObjectType> </didl:Statement> </didl:Descriptor>

1

Code Block
xml
xml
<didl:Descriptor> <\!-\- This metadata instance has its own ID number --> 
<didl:Statement mimeType="application/xml"> 
<dii:Identifier>info:doi/10.1705/74836724783</dii:Identifier> </didl:Statement> </didl:Descriptor>

2

Code Block
xml
xml
<didl:Descriptor> <\!-\- This record has its own Modification date --> 
<didl:Statement mimeType="application/xml"> 
<dcterms:modified>2006-12-20T10:29:12Z</dcterms:modified> </didl:Statement> </didl:Descriptor>

 

Code Block
xml
xml
<didl:Component>

3

Code Block
xml
xml
<didl:Resource mimeType="application/xml"> 
<\!-\- the DC data --> <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ 
[http://www.openarchives.org/OAI/2.0/oai_dc.xsd]"> <dc:creator>...</dc:creator> <dc:creator>...</dc:creator> <dc:title> ... </dc:title> ... </oai_dc:dc> </didl:Resource>

 

Code Block
xml
xml
</didl:Component>

 

Code Block
xml
xml
</didl:Item>

...

The second Item ObjectType contains a link to one digital object. This is always "by-reference" to limit the file size, when used for metadata transfer purpouses. ("by-value" is possible but increases the file size and touches the issueon ownership, use base64 encoding, not exampled here), and the Item element has an ObjectType statement with an info:eu-repo/semantics/objectFile URI. An objectFile Item can occur more than once. See the following:

<didl:Item> ... <!-- Below this line one can find links to one or more digital objects - ->

<didl:Item> <!- - First Item for a File/Bitstream --> <didl:Descriptor> <didl:Statement mimeType="application/xml"> <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType> </didl:Statement> </didl:Descriptor> ... <didl:Component> <didl:Resource mimeType="application/pdf" ref="http://my.server.nl/report.pdf"/></didl:Component> </didl:Item>

<didl:Item> <!- - Second Item for a File/Bitstream --> <didl:Descriptor> <didl:Statement mimeType="application/xml"> <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType> </didl:Statement> </didl:Descriptor> ... <didl:Component> <didl:Resource mimeType="application/pdf" ref="http://my.server.nl/appendix.pdf"/><didl:Component> </didl:Item>

<didl:Item> <!- - Third Item for a File/Bitstream - -> <didl:Descriptor> <didl:Statement mimeType="application/xml"> <dip:ObjectType>info:eu-repo/semantics/objectFile</dip:ObjectType> </didl:Statement> </didl:Descriptor> ... <didl:Component> <didl:Resource mimeType="application/pdf" ref="http://my.server.nl/datasheets.xls"/><didl:Component> </didl:Item>

</didl:Item>

...

The third ObjectType Item element contains a link to the jump-off page or intermediate page. This is done in the same way as for the Object Item element. Currently this is restricted to 1 Item of this type; there are no identifier elements, nor modification date elements present. This Item element is optional:

<didl:Item> ... <!-- Below this line; an Item with a link to one optional Intermediate page - ->

<didl:Item> <didl:Descriptor> <didl:Statement mimeType="application/xml"> <dip:ObjectType> info:eu-repo/semantics/humanStartPage </dip:ObjectType> </didl:Statement> </didl:Descriptor> ... <didl:Component> <didl:Resource mimeType="application/html" ref="http://my.server.nl/mypub.html"/></didl:Component> </didl:Item>

</didl:Item>