T2-editorial comments on ver. 1.0.2

[Martin W Sachs <mwsachs@us.ibm.com>]

Section 11, Security:  Line 2372 contains the wrong title for the ebXML
risk assessment document.  The title in the reference list is correct.
Also, the reference callout [ebTASEC] does not conform to the ebXML list of
abbreviations.  It should be secRISK.  This needs to be corrected in line
2372 and in the reference list.

Section 5.3, Operational Policies..., last paragraph, line 633:   The
statement "This specification MUST distinguish..."  does not belong in the
MSG specification.  It is stating a requirement on the specification.  It
should be deleted or changed to "This specification distinguishes..."

Section 7.2, ebXML SOAP Envelope Extensions, line 898:  This line states "
All of the ebXML SOAP extension element content defined in this
specification MUST be namespace qualified to the ebXML SOAP Envelope
extensions namespace as defined in section 8.2.1"., which is a requirement
on the specification.  It should either be deleted or changed to a
declarative statement ("...are namespace qualified to...).

Section 6.1.1, SOAP Structural conformance, line 764 states"ebXML Message
packaging SHALL comply with the following specifications:" It is not clear
whether this is a requirement on the software that uses the MSH or on the
MS spec itself.  If it is about the MS spec, it should be changed to
"...packaging complies".

Section 6.2, Message Package, lines 770 and 771:  This states "All MIME
header elements of the Message Package MUST be in conformance with the SOAP
Messages with Attachments [SOAPATTACH] specification.  In addition, the
Content-Type MIME header in the Message Package MUST contain a type
attribute that matches the MIME media type of the MIME body part that
contains the SOAP Message document.  In accordance with the [SOAP]
specification, the MIME media type of the SOAP Message MUST have the value
"text/xml."
It is not clear whether these MUSTs are requirements on the using software
or on the MS specification itself.  If they are about the MS specification,
the statements should be changed to declarative statements about the
specification, such as "...type of the SOAP message has the value...".

Regards,
Marty



*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************