Fufilling my action item on obsolete wording

I have an action item to identify "wording that was used in absence of a
decision to use SOAP/WSDL " in the WSA document.  In other words, before the
ur-Trout question of "what is a web service" was settled, there were a lot
of weasel words talking about non-SOAP 'web services', and we can clean them
up. Here are my notes:

Section 1.1 "Purpose of the Web Services Architecture"
" There isn't always a simple one to one correspondence between the
architecture of the Web and the architecture of existing SOAP-based Web
services, but there is a substantial overlap."  Let's remove this sentence.


Section 2.3.1.3.3  "A message can be as simple as an HTTP GET request, in
which the HTTP headers are the headers and the parameters encoded in the URL
are the content. Note that extended Web services functionality in this
architecture is not supported in HTTP headers.
A message can also simply be a plain XML. However, such messages do not
support extended Web services functionality defined in this architecture.
A message can be a SOAP XML, in which the SOAP headers are the headers.
Extended Web services functionality are supported in SOAP headers."

First, AFAIK we need to assume that all Web services messages are SOAP
messages, or we reopen the ur-Troutpond and flop around it until the end of
January.  So, I suggest the following wording:
"A message can be part of any SOAP message exchange pattern, as simple as a
"SOAP Response" MEP  outlined in Section 6.3 of the SOAP Recommendation. A
plain XML message without SOAP headers is often a sensible design decision,
but is out of scope of this Web Services Architecture. Extended Web services
functionality is only supported via SOAP headers in the WSA."

That's all I found in the current editors draft.

Received on Wednesday, 17 December 2003 17:07:19 UTC