Date: Thu, 28 Mar 2024 14:45:37 +0100 (CET) Message-ID: <1640674480.7572.1711633537977@wiki01p.surfnet.nl> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7571_63733517.1711633537977" ------=_Part_7571_63733517.1711633537977 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
See: http=
://www.openarchives.org/OAI/openarchivesprotocol.html#MetadataNamespaces
OAI-PMH supports the dissemination of records in multiple metadata formats=
from a repository. The ListMetadataFormats request returns the list of all=
metadata formats. metadataPrefix arguments are used in ListRecords, ListId=
entifiers, and GetRecord requests the retrieval of records, or the headers =
of records that include metadata in the format specified by the metadataPre=
fix. For purposes of interoperability, repositories must disseminate Dublin=
Core, without any qualification. Therefore, the protocol reserves the meta=
dataPrefix 'oai_dc', and the URL of a metadata schema for unqualified Dubli=
n Core, which is http://www.openarchives.org/OAI/2.0/oai_dc.xsd. The corresp=
onding XML namespace URL is http://www.openarchives.org/OAI/2.0/oai_dc/.
The DRIVER community supports the implementation of the metadataPrefix '= oai_dc' and the metadataPrefix 'didl'. Every DRIVER repository that uses th= e XML container must support this 'didl' metadata schema. The specification= of the 'didl' XMLcontainer can be found in chapter Use of MPEG-21 DIDL (xm= l-container) - Compound object wrapping page.
<OAI-= PMH ...> <...> <record> <metadata> <didl:DIDL> <didl:Item>...</didl:Item>