Re: [regrep] [RS Issue] Allowing non UUID,URN values for RegistryObject.id

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Farrukh Najmi wrote:

>
> Matt commented on regrep-rs-3.0-draft-01.pdf section 5.1.2 where it 
> says "The id MUST be a Universally Unique Identifier (UUID) and MUST 
> conform to the format of a URN that specifies a DCE 128 bit UUID as 
> specified in [UUID]" as follows:
>
> "There are certain situations where it may be necessary for a registry 
> to specify an ID That is not dce 128.  For example, in Adobe's 
> implementation, all user information comes from our Policy Server, and 
> it has its own IDs.  we use a namespace to indicate this, e.g. 
> urn:aps:node:87787887878787.  This section should be lenient to this."
>
> I have long felt that we should relax the id attribute to allow any 
> URN and require that the registry check for uniqueness within the 
> local registry during submission. In a federated situation the local 
> id is implictly qualified by the home attribute value for the home 
> registry so that would allow global uniqueness.
>
> Does anyone object to the change that allows RegistryObject.id to be 
> any URN value that is unique within the local registry? If so please 
> indicate your reasons clearly and indicate whether you could live with 
> this change if others felt it was needed. Thanks.
>
Here is how the new text on id attribute reads for draft 02:

5.1.2 Unique ID Generation

As specified by [ebRIM], all RegistryObjects MUST have a unique id 
contained within the value of the id attribute. The id MUST be a valid 
URN and MUST be unique across all other RegistryObjects in the home 
registry for the RegistryObject.

A Submitter MAY optionally supply the id attribute for submitted 
objects. If the Submitter supplies the id and it is a valid URN and does 
not conflict with the id of an existing RegistryObject within the home 
registry then the registry MUST honor the Submitter-supplied id value 
and use it as the value of the id attribute of the object in the 
registry. If the id is not a valid URN then the registry MUST return an 
InvalidRequestException. If the id conflicts with the id of an existing 
RegistryObject within the home registry then the registry MUST return 
InvalidRequestException for an UpdateObjectsRequest and treat it as an 
Update action for a SubmitObjectsRequest.

If the client does not supply an id for a submitted object then the 
registry MUST generate a universally unique id. A registry generated id 
value MUST conform to the format of a URN that specifies a DCE 128 bit 
UUID as specified in [UUID]:

(e.g. /urn:uuid:a2345678-1234-1234-123456789012/).



-- 
Regards,
Farrukh