[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] regrep 1/24/2007: Question on RS Section 3.1 Errata(PublicComment)
Dear Colleagues, Thank you for all the good feedback to nail the wording down on this part of the errata. Since there were multiple changes, I suggest we look at the final proposed text and review that rather than intermediate changes. This will make it easier on all of us. Thanks. Here is the final text I had proposed based on all the comments received... ========================================== 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). ========================================== BEDINI Ivan RD-BIZZ-CAE wrote: > Hi Kathryn, > concerning my comments the changes are as follow: > || > \/ > > 1. > OLD Text from ebRIM3.0 Section2.5.6 Attribute lid: > "The lid attribute MAY be specified by the submitter when creating the original version of a RegistryObject. If the submitter assigns the lid attribute, she must guarantee that it is a globally unique URN." > > REPLACE with new text: > "The lid attribute MAY be specified by the submitter when creating the original version of a RegistryObject. If the submitter assigns the lid attribute *when submitting the original version of a RegistryObject*, she must guarantee that it is a globally unique URN." > > 2. > OLD Text On the Registry Services Errata, Section 3.1: > ========== > Reference: Line 1150 original text: > 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 a 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/). > > ========== > > REPLACE with new text: > ========== > "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 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 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)." > > ========== > > Many thanks, > Ivan > > -----Message d'origine----- > De : Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com] > Envoyé : lundi 29 janvier 2007 17:00 > À : BEDINI Ivan RD-BIZZ-CAE; Monica J. Martin; Farrukh S. Najmi; ebXML Regrep > Objet : RE: [regrep] regrep 1/24/2007: Question on RS Section 3.1 Errata(PublicComment) > > Okay - between the comments Monica sent, the public comment, comments from Ivan, and from Farrukh, do we now have a consensus on how the text needs to be changed? Although the vote on the two ballots was completed and both erratas were approved as Committee Drafts, it sounds like the RS errata needs to be re-worded and go through the process again. > > Please let me know exactly what text needs to be changed for the issues Monica, public comment and Ivan brought up, and I will make changes and re-submit for the TC review and discussion at our next telecon (Feb. 8th) > > Thanks, > Kathryn > > Kathryn Breininger > Boeing Library Services > 425-965-0182 phone > > > > > -----Original Message----- > From: BEDINI Ivan RD-BIZZ-CAE [mailto:ivan.bedini@orange-ftgroup.com] > Sent: Thursday, January 25, 2007 8:38 AM > To: Farrukh S. Najmi > Cc: ebXML Regrep > Subject: RE: [regrep] regrep 1/24/2007: Question on RS Section 3.1 Errata(PublicComment) > > Thanks Farrukh, > Sounds good to me. > > -- > Regards, > Ivan > > -----Message d'origine----- > De : Farrukh S. Najmi [mailto:farrukh@wellfleetsoftware.com] > Envoyé : jeudi 25 janvier 2007 17:11 > À : BEDINI Ivan RD-BIZZ-CAE > Cc : ebXML Regrep > Objet : Re: [regrep] regrep 1/24/2007: Question on RS Section 3.1 Errata(PublicComment) > > BEDINI Ivan RD-BIZZ-CAE wrote: > >> Exactly, >> I agree with the latest modification. >> >> Another concern now is about the attribute LID definition, as follow: >> <ebRIM3.0_Section_2.5.6 Attribute lid> ...If the submitter assigns the >> lid attribute, she must guarantee that it is a globally unique URN... >> </ebRIM3.0_Section_2.5.6 Attribute lid> >> >> This could seem inconsistent with the new text and not clear about the action to do. Not sure about what means *globally unique*. >> If my interpretation is correct, in reality it is not so because physically two differents UUID imply two diferents RegistryObjects (R01 and RO2) with the same LID => the LID is not globally unique. >> What must be guaranteed is that in this case => Twoor more RO with the >> same LID must have (at least) a different version number (i.e. for the >> same LID => RO1 version must be different from RO2 version) >> >> >> > > The complete text says: > > "The lid attribute MAY be specified by the submitter when creating the original version of a RegistryObject. If the submitter assigns the lid attribute, she must guarantee that it is a globally unique URN." > > The text applies to specifying lid when submitting the "original version of a RegistryObject". In this case it MUST be globally unique. > > Perhaps a clarity could be: > > > "The lid attribute MAY be specified by the submitter when creating the original version of a RegistryObject. If the submitter assigns the lid attribute *when submitting the original version of a RegistryObject*, she must guarantee that it is a globally unique URN." > > > -- > Regards, > Farrukh > > Web: http://www.wellfleetsoftware.com > > > -- Regards, Farrukh Web: http://www.wellfleetsoftware.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]