Versions Compared

Old Version 13

changes.mady.by.user Unknown User (kemman)

Saved on

compared with

New Version 14

changes.mady.by.user Unknown User (kemman)

Saved on

Key

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

...

The DARE community supports the implementation of the metadataPrefix 'oai_dc' and the the metadataPrefix 'dare_didl'. The schema for the XMLcontainer dare_didl is located at http://www.repository.knaw.nl/web/dare_didl.xsd.
The corresponding XML namespace for dare_didl namespace URI currently is http://www.repository.knaw.nl/web/dare_didl.
Every DARE repository must support this 'dare_didl' metadata schema.
The specification of the dare_didl XMLcontainer can be found in the document XMLcontainer1.1.1.pdf. at the location: http://www.darenet.nl/upload.view/DARE_DIDL-XMLcontainter-Specification-v1.1.1.pdf

Code Block

 <OAI-PMH ...>

...


  <...>

...


    <record>
      <metadata>
       <didl:DIDL>
         <didl:Container>...</didl:Container>

Anchor
_Toc146962622
_Toc146962622
Datestamp format

Look at: http://www.openarchives.org/OAI/openarchivesprotocol.html#Datestamp
, http://www.openarchives.org/OAI/openarchivesprotocol.html#Dates
and http://www.w3.org/TR/NOTE-datetime
The value of datestamps in both requests and responses must comply to the specifications for UTCdatetime in this document. The DARE agreement supports the use of optional granularity which involves the time with seconds YYYY-MM-DDThh:mm:ssZ.
This value complies with the specifications for the UTCdatetime in sections 3.3.1 in the OAI-PMH document. Datestamps are encoded using ISO8601 and are expressed in UTC.

Code Block

 <OAI-PMH ...>

...


  <...>

...


    <GetRecord>
      <record>
       <header>
         <datestamp>2001-12-14T12:01:45Z</datestamp>

A repository that supports YYYY-MM-DDThh:mm:ssZ should indicate so in the Identify response.

Code Block

 <OAI-PMH ...>

...


  <...>

...


  <Identify>
    <granularity>YYYY-MM-DDThh:mm:ssZ</granularity>

...


  <...>

Anchor
_Toc146962623
_Toc146962623
Set naming

Look at: http://www.openarchives.org/OAI/openarchivesprotocol.html#Set
The OAI-PMH document says the folowing:
Repositories may organize items into sets. Set organization may be flat, i.e. a simple list, or hierarchical.
The DARE agreement is that DARE repositories support at least two type of sets. The 'dare' set and the 'keur' set. Both sets are flat and do not have any hierarchical structure.
The table below shows the highly preferred setName and setSpec that can be used for either set.

...

Look at: http://www.openarchives.org/OAI/openarchivesprotocol.html#Identify
The repository must provide an administrator e-mail address for the Identify request.
In the near future we want the harvester to give immidiate response to the Repository Adminitrator to inform about the errors this DARE repository is creating.
See table below for an example of usage to the administer e-mail address.

Code Block

 <OAI-PMH ...>

...


  <...>

...


  <Identify>
    <adminEmail>somebody@loc.gov</adminEmail>

...


    <adminEmail>anybody@loc.gov</adminEmail>

...


    <...>

The use of an adminEmail in the Identify request is mandatory, and is also dictated by the OAI-PMH protocol. See below:
"The Identify verb is used to retrieve information about a repository."
"The response must include one or more instances of the following element:

...

Example of the recommended use of prefixes and namespaces.

Code Block

 <OAI-PMH

...


	xmlns="http://www.openarchives.org/OAI/2.0/"

...


	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

...


	xsi:schemaLocation="

...


http://www.openarchives.org/OAI/2.0/

...


  http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"

...


>

...


  <...>

...


  <metadata>
    <didl:DIDL

...


      xmlns:didl="urn:mpeg:mpeg21:2002:02-DIDL-NS"

...


	xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS"

...


	xmlns:dcterms="http://purl.org/dc/terms/"

...


	xsi:schemaLocation="

...


urn:mpeg:mpeg21:2002:02-DIDL-NS http://standards.iso.org/.../didl.xsd

...


urn:mpeg:mpeg21:2002:01-DII-NS  http://standards.iso.org/.../dii.xsd"

...


    >
      <...>

...


    </didl:DIDL>

...


  </metadata>

...


  </...>

...


<OAI-PMH>

Wiki Markup
\\
\*According to the proclamation in the same document (\[\*[http://www.w3.org/TR/REC-xml-names/#ns-using\*|http://www.w3.org/TR/REC-xml-names/#ns-using*]\|http://www.w3.org/TR/REC-xml-names/#ns-using\]), the DARE agreement will be that it is also possible to declare prefixes and namespaces in the ancestors of the document.\*

"

Anchor
nsc-NSDeclared
nsc-NSDeclared
The namespace prefix, unless it is xml or xmlns, MUST have been declared in a namespace declaration attribute in either the start-tag of the element where the prefix is used or in an ancestor element (i.e. an element in whose content the prefixed markup occurs)."


Example of the optional , but not recommended uses of prefixes and namespaces.

Code Block

 <OAI-PMH

...


	xmlns="http://www.openarchives.org/OAI/2.0/"

...


	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

...


	xmlns:didl="urn:mpeg:mpeg21:2002:02-DIDL-NS"

...


	xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS"

...


	xmlns:dcterms="http://purl.org/dc/terms/"

...


	xsi:schemaLocation="

...


http://www.openarchives.org/OAI/2.0/

...


  http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd

...


urn:mpeg:mpeg21:2002:02-DIDL-NS http://standards.iso.org/.../didl.xsd

...


urn:mpeg:mpeg21:2002:01-DII-NS  http://standards.iso.org/.../dii.xsd "

...


>

...


  <...>

...


  <metadata>
    <didl:DIDL>

...


      <...>

...


    </didl:DIDL>

...


  </metadata>

...


  </...>

...


<OAI-PMH>

Anchor
_Toc146962630
_Toc146962630
XML validation

The XML that the repository provides as output has to be initially validated by the DARE repository administrator, and by the DARE harvester administrator on the first harvest.
A DARE repository must provide valid XML according to the OAI-PMH schema, and also to the dare_didl schema.
Validation can be done by using an XML validator (e.g. from altova. www.altova.com ) by saving the repository output as an xml document and opening it in the validator.
For a validator to validate an XML document, inside the document the xsi:schemaLocation(s) must be used.

Code Block

 For the <OAI-PMH> schema use:

...


<OAI-PMH
            xmlns="http://www.openarchives.org/OAI/2.0/"

...


            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

...


            xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/

...


            http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"
>
Code Block

 For the <didl:DIDL> schema use:

...


<didl:DIDL

...


diext:DIDcreated="YYYY-MM-DDThh:mm:ssZ"

...


            xmlns:didl="urn:mpeg:mpeg21:2002:02-DIDL-NS"

...


            xmlns:dcterms="http://purl.org/dc/terms/"

...


            xmlns:diext="http://library.lanl.gov/2004-04/STB-RL/DIEXT"

...


            xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS"

...


            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

...


            xsi:schemaLocation="

...


                        urn:mpeg:mpeg21:2002:02-DIDL-NS

...


                        http://purl.lanl.gov/STB-RL/schemas/2004-08/DIDL.xsd

...


                        urn:mpeg:mpeg21:2002:01-DII-NS
                        http://purl.lanl.gov/STB-RL/schemas/2003-09/

...

DII.xsd
                        http://library.lanl.gov/2004-04/STB-RL/DIEXT
                        http://purl.lanl.gov/STB-RL/schemas/2004-04/DIEXT.xsd"
>

...

Code Block

 For the <oai_dc:dc> schema use:

...


<oai_dc:dc

...


            xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc

...

/"
            xmlns:dc="http://purl.org/dc/elements/1.1/"

...


            xsi:schemaLocation="

...


                        http://www.openarchives

...

.org/OAI/2.0/oai_dc/
                        http://www.openarchives.org/OAI/2.0/oai_dc.xsd

...


                        http://purl.org/dc/elements/1.1

...

/
                        http://dublincore.org/schemas/xmls/simpledc20021212.xsd"
>

...

Code Block

 For the <dare_qdc:qdc> schema use:

...


<dare_qdc:qdc

...


            xmlns:dare_qdc="http://dare.nl/dare_qdc:/2.0"

...


            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

...


                        http://purl.org/dc/elements/1.1/

...


                        http://dublincore.org/schemas/xmls/simpledc20021212.xsd"
>

...

Code Block

 For the <qdc:dc> schema use (not tested):

...


<container_qdc:qualifieddc

...


            xmlns:container_qdc="urn:dc:qdc:container"

...


            xmlns:qdc="http://purl.org/dc/elements/1.1/"

...


            xmlns:dterms="http://purl.org/dc/terms/"

...


            xmlns:dcmitype="http://purl.org/dc/dcmitype

...

/"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

...


            xsi:schemaLocation="

...


                       urn:dc:qdc:container

...


http://dublincore.org/schemas/xmls/qdc/2003/04/02/

...

qualifieddc.xsd

                       http://purl.org/dc/elements/1.1/

...


http://dublincore.org/schemas/xmls/qdc/2003/04/02/dc.xsd

...



                       http://purl.org/dc/terms/

...


http://dublincore.org/schemas/xmls/qdc/2003/04/02/dcterms.xsd

...



                       http://purl.org/dc/dcmitype/

...


http://dublincore.org/schemas/xmls/qdc/2003/04/02/dcmitype.xsd"

...


>

Anchor
_Toc146962631
_Toc146962631
Communication for Repository modification

...