ebXML TR&P -- comments on Messaging Service Specification v0.1

[Philippe DeSmedt <PDeSmedt@viquity.com>]

All,

I'd like to add the following comments on the ebXML TR&P Messaging Service
Specification v0.1, to those already posted to the list (apologies for
duplicates):

*	Section 2.5.4. Optional Support for Signed and Encrypted Payloads:
This section appears to have been copied verbatim from section 2.4.4
(Optional Support for Signed Headers), and makes no mention of encryption.
Encryption is not done on the header, but it is suggested as a possibility
for the payload. As such, we'll need to add a sentence or paragraph to
section 2.5.4 that actually specifies how encryption could de done (in
addition to signing), i.e., have the body of the section correspond to its
title;
*	we need to make sure that the lists of authors and contributors, as
well as the Acknowledgements section (6) are up-to-date -- there are many
people who have valuably contributed to the specs, through e-mail,
conference calls, and face-to-face meetings, that have been left off;
*	if we will indeed have a section where bindings are specified for
mime-aware vs non-mime-aware transports, as we have been discussing, we'll
need to update the Introduction (1), where it is currently stated that 'no
assumption or dependency is made relative to transport protocol [...]';
*	I'm a bit unclear as to the meaning of the NOTE in section 3 (lines
372-373): re. possibly missing header elements, it is stated: '[...] Every
effort will be made to preclude this possibility.' As we are 'only' at
version 0.1 of this document, there's a strong likelihood that things will
change throughout the document (hopefully not by much). Why do we add a NOTE
only to this section? Are we more concerned with this piece of the spec
changing than other pieces? If so, why?

Regards,

-Philippe
_______________________________
Philippe De Smedt
Architect
Viquity Corporation (www.viquity.com)
1161 N. Fair Oaks Avenue
Sunnyvale, CA 94089-2102
(408) 548-9722
(408) 747-5586 (fax)
pdesmedt@viquity.com