W3C home > Mailing lists > Public > www-ws-arch@w3.org > October 2002

Re: new editor's draft of WSA available

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Fri, 25 Oct 2002 10:24:49 +0200
Message-ID: <3DB8FFD1.3070909@crf.canon.fr>
To: Christopher B Ferris <chrisfer@us.ibm.com>
CC: www-ws-arch@w3.org

Chris et al,

Some further comments on the draft.



Section 1.1 The Need for an Architecture

For consistency with:
   "extensible message framework (SOAP)"
I suggest adding "(WSDL)" to:
   "interface definition language"
   "interface definition language (WSDL)"

Section 3.1 Basic Architecture

MEPs are defined at least three times:
   "Requester and providers interact using one or more
    message exchange pattern (MEPs)."
   "message exchange patterns (MEP)s that
    group basic messages into higher-level interactions"
and again:
   "Service requesters and providers interact by
    exchaging messages, which may be aggregated to form
    message exchange patterns (MEPs)."

Similarly, the extended Web services architecture is defined at 
least twice:
   "details how messages may carry context to support
    security, transactions, orchestration"
   "may be extended to include features that
    ensure privacy, coordinate transactions, orchestrate"

More importantly, the two sentences give above give the 
impression that the extended architecture is provided only 
through specialized MEPs; other types of features (modules) are 
completely left out.

I don't think the paragraph starting with the following sentence 
is very clear: "For example, an XML message may have or more 
content models associated with it"

More imporantly, the terminology used used in the paragraph cited 
above is at odds with that of SOAP (and possibly that of WSDL). 
For example, "content model" vs. "module", "endpoint" vs. "node", 
"provider" vs. "ultimate receiver". This is likely to create 

The following sentence gives the impression that, to access a 
service, you always need to be a provider as well: "that function 
as both requesters and providers".

I disagree with the following sentence, both from a WSDL and SOAP 
   "The request/response pattern [should be MEP] is also often
    called the remote procedure call (RPC)."
Document exchanges work with request-response as well.

Section 3.2.1 Features

"Here is a partial list of features:"
Why a partial list? Why a list at all?

The description of list items is very terse.

Section 3.3 Web Services Stacks

The appearance of the acronym "SOA" first comes as a shock: where 
did the "P" disappear? It might be worth changing the acronym to 
something less akin to "SOAP".
Received on Friday, 25 October 2002 04:24:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:42 UTC