Thank you David for forwarding Ronald’s
message.
Ronald,
You are right in your comments and we
thank you very much for your feedback. We will make the changes to correct
those errors. Just for your information, let me confirm what is correct:
1. The response example message in 5.3.1 has the collaborationInfo in the
wrong place (line 1520-1524) (the
example is wrong: typo error)
2. The mustunderstand and version on the message element are in the same
namespace according to the xsd but in different ones according to the docs (the xsd is wrong: mustUndersatand
is a SOAP attribute and must have the SOAP namespace, whereas the version
attribute must have ebMS namespace).
3. In the ebMS Header example (line 1151) contains a PartInfo element with
a scheme and description element. These are *not* in the schema in the same
document. In 5.2.1.13 there is information that it is allowed to use
these elements in the same namespace. (eb:Schema and eb:Description are optional elements and
are indeed not mentioned by the xsd. The xsd needs to be corrected to
incorporate those optional elements).
4. In the example in 5.2.1.3 and the docs of 5.2.1.4 there is a reference
to a type attribute. This attribute is not in the docs: PartyId is not an
xmltype. (the schema will be
corrected to reflect that).
Thank you Ronald,
Hamid.
From: David RR Webber
(XML) [mailto:david@drrw.info]
Sent: Sunday, July 02, 2006 7:28
AM
To: ebXML MSG
Subject: [ebxml-msg] [FWD:
[ebxml-msg-comment] Public Comment]
By a miracle I did not think this was SPAM.
Can someone please respond to Ronald on this?
-------- Original Message --------
Subject: [ebxml-msg-comment] Public Comment
From: comment-form@oasis-open.org
Date: Sat, July 01, 2006 6:45 pm
To: ebxml-msg-comment@lists.oasis-open.org
Comment from: ronald@vankuijk.net
Name: Ronald van Kuijk
Title: IT Architect
Organization: Private interest
Regarding Specification: ebMS 3.0 Public Review Draft 1
A few things that caught my attention trying to use the xsd with xmlbeans and
reading the docs:
- The response example message in 5.3.1 has the collaborationInfo in the wrong
place (line 1520-1524)
- the mustunderstand and version on the message element are in the same
namespace according to the xsd but in different ones according to the
docs
- in the ebMS Header example (line 1151) contains a PartInfo element with a
scheme and description element. These are *not* in the schema in the same
document. In 5.2.1.13 there is information that it is allowed to use
these elements in the same namespace
- in the example in 5.2.1.3 and the docs of 5.2.1.4 there is a reference to a
type attribute. This attribute is not in the docs (PartyId is not an xmltype)
---------------------------------------------------------------------
To unsubscribe, e-mail: ebxml-msg-comment-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ebxml-msg-comment-help@lists.oasis-open.org
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. You may a link to this group and all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php