[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-msg-comment] Fwd: [TC Admin] AS4 EBMS Schema XSD BUG
Some of us do have some experience in validating XML content with XSLT + Xpath. So we can advise on this, even provide some generic (XSLT) code that helps doing this. We are talking of all kinds of validation (value of attributes/elements, presence of optional elements/attr, combinations that are consistent/inconsistent) that are usually beyond xsd capability. In my experience, people often use xsd more for code generation (stubs, classes) than for actual validation… For a past test project in WS-I, I had to develop a little generic open-source in XSLT such that people only need to know about XPath, in order to write test assertions that can be processed to do this kind of testing, including the case you mention. -jacques From: Makesh Rao (marao) [mailto:marao@cisco.com] Hi Stephen Apologies for the delay. We discussed this in our TC meeting on 5th November. I was to communicate out to you and I apologize for not doing it immediately. Basically the TC members were of the opinion that ideally the XSD alone should not be used to catch all the validation rules. Another approach e.g. Using xslt was mentioned a something that effectively does the validation. Hope this clarifies the situation you encountered. Thanks Makesh From: A2C <A2C@godalming.ac.uk> Hi Makesh, I just wanted to check in to see if there was a decision/resolution regarding the Schema bug I encountered. I’m not sure how often you meet so you may not have had a chance to discuss it yet. Also I wanted to take the opportunity to report a typo I found that caused some issues within our implementation group. In the spec document located at http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/os/AS4-profile-v1.0-os.html#__RefHeading__58431_149522555The examples repeatedly use <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmlds#sha1"/>.We didn’t realise this was incorrect until one of our test partners APIs threw an error as it did not conform to W3C standards. The W3C spec http://www.w3.org/TR/xmldsig-core/#sec-AlgID has the correct algorithm URI as http://www.w3.org/2000/09/xmldsig#sha1 Regards, Stephen Law Godalming College From: Makesh Rao (marao) [mailto: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> 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 ---------- 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 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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]