[ fulfills an action item assigned Nov. 5]
Errata:
In msg-header-2_0.xsd, an "Acknowledgment" element is defined that has a content model with the following sequence:
This definition is incorrect because it leads to a violation of the Unique Particle Attribution constraint.
The most conservative correction, that leaves functionality specified in Version 2.0 of ebXML Messaging intact, is to remove the "any" element. In other words, a schema would be created that replaced the above by the following,
The ebXML Messaging specification Version 2.0 does not specify any functionality actually using the "Acknowledgment" element's extension point supplied by the "any" element.
If parties are using an extension in their acknowledgments, and need to have signatures and to do checks on instances with respect to their schema validity, then a suggested "work around" is to make a local copy of the schema that modifies the 'namespace="##other"' to refer to the namespace(s) of the element(s) that are, by bilateral agreement, allowed to be inserted at the extension point. For example, if an element
is an extension element, then the content model could be modified to read: