RE: new editor's draft of WSA available

Ugo,

Thanks for the review and comments.

Christopher Ferris
Architect, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624

Ugo Corda wrote on 10/22/2002 06:42:20 PM:

> Just a few comments after quickly going through the new draft:
> 
> - Section 3.1 and Section 4
> "The request/response pattern is also often called the remote procedure 
call (RPC) oriented 
> interaction style"
> 
> I thought we already agreed to drop that statement. See thread starting 
at [1]

Okay.

> 
> - Section 3.2.1
> "message integrity - one solution is a SOAP Module with encryption"
> "digital signatures" would be more appropriate here than "encryption" 

Correct. I'll fix this.

> 
> - Section 3.3.1.2
> "Packaging"
> 
> This term has been used in the past within the W3C to indicate the area 
currently addressed by 
> attachments (see for example [2]) and might create confusion
> 
> - Section 4 
> "Intermediaries are allowed to process a message header information 
only. When processing a 
> message, intermediaries must not disturb the data content, but may add 
or remove header content. "
> 
> I guess it depends on what we mean by "disturb". For example, an 
encryption intermediary must be 
> able to replace sections of the body with their encrypted 
representation.
> 
> 
> - Section 6.3.2
> "JMS"
> 
> JMS is not really a protocol, but a standardized Java API put on top of 
(usually proprietary) MOM 
> protocols. It might still be convenient to use JMS to refer to the 
collection of all those 
> possible protocols. Maybe a little clarification note would be useful.

Agreed, I'll clarify to indicate a JMS Service Provider's protocol, okay?

> 
> 
> Ugo
> 
> 
> [1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0054.html
> [2] http://www.w3.org/XML/2000/07/xml-packaging-charter
>