[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-bp] [ebBP] 5/31/2004: Get out the vote for WI-43-66 [RSD]
There are clear use cases for both NameID and UUID. The most important difference between them is that a UUID is explicit to an instance while the NameID is general to a class of instance that have the same name. Thus UUID is used when specific instance must be composed to solve the problem, and NameID is used when the local (or package) versions are composed to solve the problem. NameID is critical for standards work, since there must be a way to bind all of the implementations of a semantic process or transaction together, that being the NameID. Thanks, John -----Original Message----- From: Monica J. Martin [mailto:Monica.Martin@Sun.COM] Sent: Monday, May 31, 2004 8:32 PM To: ebXML BP Subject: [ebxml-bp] [ebBP] 5/31/2004: Get out the vote for WI-43-66 [RSD] Importance: High OASIS.ebBP.WI-43-66-Name and Name ID Clarification; Topic|; Point|Quorum Vote Opened 31 May 2004; Attachment|http://www.oasis-open.org/archives/ebxml-bp/200405/msg00147.h Attachment|tml; mm1@ The vote for this work item today and will continue to 8 June 2004. Original Work Item 43 (encompasses 66): In the BPSS Schema v1.01 and v1.1 elements can be reference either by their name or their ID (or GUID). Seems one is redundant and ID's (GUIDs) normally used to reference other elements. Do GUID's help XML parsers? Use of GUID and GUIDREF could lead to processing errors. Identify or recommend if acceptable for CPPA or allow them to also decide on this (for CPA negotiation). Given resolve, specify explicitly if the scope of global uniqueness for GUIDREF. Vote Question: ======================================================================================== Do you agree that: The BPSS SHOULD support the use document-scoped nameID attribute for reference solution (Solution 2) with the distributed amendment: [See Nagahashi submission under References]. NameID: NameID is xsd:ID. NameID is Document-scoped, regardless of package structure. Since NameID is document-scoped, no qualified identifier syntax is required. The NameID MUST be used for reference purposes. Name: The Name attribute MAY be mandatory. Name attribute MAY be unique within a BPSS document. The use of Name attribute is used by CPPA v2.0 to reference BPSS elements. The Name SHOULD NOT be used by other BPSS elements for reference purposes. The Name type is xsd:string and arbitrary text is allowed. Use cases for visualization, CPPA and another identified requirements will dictate whether or not the Name is required. Whether or not the Name is mandatory or optional will be further investigated. At this time, the Name attribute SHOULD be required. The technical specification SHOULD clearly specify the use of Name and NameID. In addition, a implementor's note or hint SHOULD be given to ensure care is taken to make NameID unique within a document (such as embedding package name in NameID). ======================================================================================== References: Summary proposal for vote: http://www.oasis-open.org/archives/ebxml-bp/200405/msg00147.html @mm1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]