Re: [ebxml-msg-comment] Fwd: [TC Admin] AS4 EBMS Schema XSD BUG

["Makesh Rao (marao)" <marao@cisco.com>]

Hello Stephen

Thanks for reporting the issue. I will table this in the next TC meeting and get back to you with our decision/resolution.

Thanks

Makesh

Co-Chair ebMS TC

From: Paul Knight <paul.knight@oasis-open.org>
Date: Friday, October 17, 2014 at 10:09 AM
To: "ebxml-msg-comment@lists.oasis-open.org" <ebxml-msg-comment@lists.oasis-open.org>
Cc: "A2C@godalming.ac.uk" <A2C@godalming.ac.uk>, Chet Ensign <chet.ensign@oasis-open.org>
Subject: [ebxml-msg-comment] Fwd: [TC Admin] AS4 EBMS Schema XSD BUG

Hi ebXML Messaging Services TC members,

Some detailed feedback and a question from implementers (below).  

Please let Stephen Law know that you've received his issue.

Thanks and best regards,

Paul 

---------- Forwarded message ----------
From: A2C <A2C@godalming.ac.uk>
Date: Fri, Oct 17, 2014 at 11:15 AM
Subject: [TC Admin] AS4 EBMS Schema XSD BUG
To: "tc-admin@oasis-open.org" <tc-admin@oasis-open.org>

Hi,

 

We are trying to validate EBMS messages against the schema that can be found here http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms-header-3_0-200704.xsd but we are running into an issue.

 

In the XSD it mentions the following:

 

“Note that the eb:Messaging element cannot be empty (at least one of eb:SignalMessage or eb:UserMessage element must present).”

 

However if I validate a message that contains neither of those against this XSD it counts as valid still which seems like a bug to me. So am I looking at an old XSD for this specification? Perhaps there is a newer version that I should be using that doesn’t have this issue.

<xsd:sequence>

                <xsd:element name="SignalMessage" type="SignalMessage" minOccurs="0" maxOccurs="unbounded"/>

                <xsd:element name="UserMessage" type="UserMessage" minOccurs="0" maxOccurs="unbounded"/>

                <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

 

We thought maybe changing the above which is the current part that defines it to the below might fix the issue but were not sure.

 

<xsd:sequence>

       <xsd:choice minOccurs="1" maxOccurs="unbounded">

              <xsd:element name="SignalMessage" type="SignalMessage" maxOccurs="unbounded"/>

              <xsd:element name="UserMessage" type="UserMessage" maxOccurs="unbounded"/>

       </xsd:choice>

       <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

                                               

Any help would be most appreciated.

 

Regards,

 

Stephen Law

Godalming College

This email is confidential and is for the attention of the addressee only. If you received this email in error please delete all copies from your system and notify the sender. No legally binding commitments will be created by this email. All email received and sent by us may be monitored to protect the business interests of Godalming College.

--

Paul Knight  - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst