Although having two different identifier systems is a problem in theory, in 
practice it appears to me that at this point there are only a handful (a 
small number) of schemas that have identifiers of  both styles.

Could we perhaps:
1. precisely enumerate those that have the multiple identifiers.
2. come up with a procedure whereby when a schema identifier is needed:
    -  First check if one already exists.
    -  If it does, then it should be used, both by SRU and OpenURL, 
regardless of which syle it is.
    - if it does not, then assign an identifier: OpenURL style if it is 
(initially) for OpenURL use, SRU style if for SRU, and both registries add 


----- Original Message ----- 
From: "Hammond, Tony" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, May 20, 2009 11:17 AM
Subject: Re: One Data Format Identifier (and Registry) to Rule Them All

> Hi Rob:
> Yes, indeed they do.
> We've just put up an OAI server and are using PAM but as yet have no URI 
> for
> that:
> In fact I'm on a call in an hour with the PRISM folks to address just this
> issue. Hoping to get a URL for the schema so that we can register with SRU
> (with an SRU style identifier at this time).
> Cheers,
> Tony
> On 20/5/09 15:52, "Rob Sanderson" <[log in to unmask]> wrote:
>> PMH has an operation listMetadataFormats which lists the local names and
>> any other information it has about the formats it supports.
>> eg:
>> (view source to see the response without the helpful XSLT)
>> Eg, they have the problem, but don't even bother with a registry.
>> Rob
>> On Wed, 2009-05-20 at 15:30 +0100, Ray Denenberg, Library of Congress
>> wrote:
>>> From: "Dr R. Sanderson" <[log in to unmask]>
>>>> There isn't one, but the protocol has the same requirements as SRU and
>>>> OpenURL.
>>> I remain confused.   If the protocol has the requirement to specify a 
>>> schema
>>> identifier, there must be some way for an implementor to (1) find out 
>>> the
>>> appropriate identifier for a particular schema, including finding out 
>>> that
>>> there isn't one; and (2) register an identifier for a schema when there
>>> isn't one.
>>> --Ray
> ********************************************************************************
> DISCLAIMER: This e-mail is confidential and should not be used by anyone 
> who is
> not the original intended recipient. If you have received this e-mail in 
> error
> please inform the sender and delete it from your mailbox or any other 
> storage
> mechanism. Neither Macmillan Publishers Limited nor any of its agents 
> accept
> liability for any statements made which are clearly the sender's own and 
> not
> expressly made on behalf of Macmillan Publishers Limited or one of its 
> agents.
> Please note that neither Macmillan Publishers Limited nor any of its 
> agents
> accept any responsibility for viruses that may be contained in this e-mail 
> or
> its attachments and it is your responsibility to scan the e-mail and
> attachments (if any). No contracts may be concluded on behalf of Macmillan
> Publishers Limited or its agents by means of e-mail communication. 
> Macmillan
> Publishers Limited Registered in England and Wales with registered number 
> 785998
> Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS
> ********************************************************************************