Re: [regrep] regrep 1/24/2007: Question on RS Section 3.1 Errata(PublicComment)

["Farrukh S. Najmi" <farrukh@wellfleetsoftware.com>]

Farrukh S. Najmi wrote:
> BEDINI Ivan RD-BIZZ-CAE wrote:
>   
>>  
>> <farrukh>
>> ==========================================
>> Proposed Fixed Text Based upon public comment:
>>
>> A Submitter MUST supply the id attribute for submitted objects. If the
>> id is not a specified then the registry MUST return an
>> InvalidRequestException.
>>
>> If the id and lid match the id and lid of an existing RegistryObject
>> within the home registry, then the registry MUST treat it as an Update
>> action upon the existing RegistryObject. If the id matches the id of an
>> an existing RegistryObject within the home registry but the lid does not
>> match that existing object's lid, then the registry MUST return an
>> InvalidRequestException.
>>
>> If the Submitter supplies the id and it is a valid URN 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 treat it as a temporary id and replace it,
>> and all references to it within the request, with a registry generated
>> universally unique id. A registry generated universally unique 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).
>>
>> ==========================================
>> </farrukh>
>>
>> Does it imply that if only the LID matches with an already existing
>> RegistryObject then the registry MUST treat it as a Create new RO action
>> with the same LID?
>>
>>   
>>     
> Hi Ivan,
>
> If it matches an existing lid but has a different id then it is a new
> version for the same logical object. This is covered by versioning 
> feature's spec. Do we need to make any changes?
>
>   

Looking at the versioning spec content I do not see a clear statement
regarding the behavior when an obeject is submitted to match an existing
lid and a non-existing id. So your comment suggests we should clarify
this aspect.

Here is another modification to address your comment:


==========================================
Proposed Fixed Text Based upon public comment:

A Submitter MUST supply the id attribute for submitted objects. If the
id is not a specified then the registry MUST return an
InvalidRequestException.

If the id and lid match the id and lid of an existing RegistryObject
within the home registry, then the registry MUST treat it as an Update
action upon the existing RegistryObject. 

If the id matches the id of an
an existing RegistryObject within the home registry but the lid does not
match that existing object's lid, then the registry MUST return an
InvalidRequestException.

If the lid matches the lid of an
an existing RegistryObject within the home registry but the id does not
match that existing object's id, then the registry MUST create the newly submitted
object as a new version of the existing object.

If the Submitter supplies the id and it is a valid URN 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 treat it as a temporary id and replace it,
and all references to it within the request, with a registry generated
universally unique id. A registry generated universally unique 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

Web: http://www.wellfleetsoftware.com