[Fwd: [ebxml-dev] nondeterministic Acknowledgment in ebms?]

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

On ebxml-dev....

--- Begin Message ---

• From: Bryan Rasmussen <brs@itst.dk>
• To: ebxml-dev@lists.ebxml.org
• Date: Thu, 10 Feb 2005 11:52:15 +0100

Hey, in the ebms schemas found at
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd
the element ACKNOWLEDGMENT creates a nondeterministic model
<!-- ACKNOWLEDGMENT, for use in soap:Header element -->
<element name="Acknowledgment">
    <complexType>
        <sequence>
            <element ref="tns:Timestamp"/>
            <element ref="tns:RefToMessageId"/>
            <element ref="tns:From" minOccurs="0"/>
            <element ref="ds:Reference" minOccurs="0"
maxOccurs="unbounded"/>
            <any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
        </sequence>
        <attributeGroup ref="tns:headerExtension.grp"/>
        <attribute ref="soap:actor"/>
    </complexType>
</element>

The combination:
 
            <element ref="ds:Reference" minOccurs="0"
maxOccurs="unbounded"/>
            <any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>

creates a nondeterministic content model. ds is not the targetNamespace.

Is there another schema somewhere that this problem does not exist? My
suggestion would be the obvious

<element name="Acknowledgment">
    <complexType>
        <sequence>
            <element ref="tns:Timestamp"/>
            <element ref="tns:RefToMessageId"/>
            <element ref="tns:From" minOccurs="0"/>
            <any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
        </sequence>
        <attributeGroup ref="tns:headerExtension.grp"/>
        <attribute ref="soap:actor"/>
    </complexType>
</element>

--- End Message ---