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 |
