[OAI-implementers] OAI identifiers
Fri, 12 Dec 2003 13:29:00 -0500
It's also important to distinguish between the identifier for the
RESOURCE, which would go in a dc:identifier (for Dublin core metadata)
field, and the identifier for the OAI ITEM, which would be in the OAI
record header, and would be the value for the OAI identifier argument
(for GetRecord verb, for example).
It's unusual to have a full URL (starting "http://") as the identifier
of an OAI ITEM, while it is common to have a full URL in a dc:identifier
> -----Original Message-----
> From: Simeon Warner
> Sent: Friday, December 12, 2003 1:16 PM
> To: email@example.com
> Subject: Re: [OAI-implementers] OAI identifiers
> If you are not using oai-identifiers then you must not include an
> oai-identifier description block in your Identify response. The
> oai-identifier description container (defined by the schema
> http://www.openarchives.org/OAI/2.0/oai-identifier.xsd) is specific
> to the oai-identifier scheme.
> From an OAI standpoint, your ARK's should be treated as opaque
> within your repository by any service provider that doesn't recognize
> understand them.
> On Fri, 12 Dec 2003, David Loy wrote:
> > This is the first time I've written to this list.
> > I am trying to get a better understanding of identifier as used in
> > protocol.
> > According to the standard (I'm using
> > , a unique identifier is defined as a URI which by definition
> > ftp:, http:, oai: etc.
> > We use an ark as our persistent URI (see
> > http://www.cdlib.org/inside/diglib/ark/):
> > http://findaid.oac.cdlib.org/findaid/ark:/13030/ft2s200504
> > My question is how to set up the description element of the Identity
> > response to describe this non-oai identifier.
> > Any help would be terrific.
> > Thanks
> > David Loy
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe: