[ebBP] 5/24/2004: WI-43-66 Clarification and Proposal to go to Vote 31May 2004, End 8 June 2004 [RSD]

["Monica J. Martin" <Monica.Martin@Sun.COM>]

OASIS.ebBP.WI-43-66-Name and Name ID Clarification;
Topic|;
Point|Summary for Opening of Another Quorum Vote 31 May 2004;
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200404/msg00125.html;
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00250.html; 

Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00224.html; 


mm1@
In the informal F2F in New Orleans in late April 2004, the group 
recommended the following on WI-43-66 Name and Name ID usage:

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.

Key requirements:

    * Provide capability to use a computable identifier for reference.
    * Allow a Name to be effectively used by business analysts.
    * Provide guidance to implementers about the effective use of Name
      and Name ID (i.e. Document scoped usage)
    * Support other ebXML specifications (ebCPPA requirements for example).

Recommendation from informal F2F in New Orleans:

    * For v2.0: Set up a vote for Solution 2 amended and allow for Other
      if any other option is preferred.
    * For v3.0: Open work item to quantify Service definition for
      ebMS-CPA-ebBP alignment.

Vote Question (to be opened 31 May 2004):
========================================================================================
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:
Roberts, original proposal and input, 22 February: 
http://www.oasis-open.org/archives/ebxml-bp/200402/msg00224.html
Martin, boundaries for v2.0 scope, 24 February: 
http://www.oasis-open.org/archives/ebxml-bp/200402/msg00250.html
Nagahashi, updated proposal including Solution 2 with amendment: 
http://www.oasis-open.org/archives/ebxml-bp/200404/msg00125.html
Martin, informal F2F agenda and summary, 
http://www.oasis-open.org/archives/ebxml-bp/200404/msg00053.html
========================================================================================

This email and today's meeting mention serve as the 7-day notice on this 
vote that will open 31 May 2004 and close 8 June 2004.

@mm1