[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SOAP wording AI proposal
>> AI: Hal and Maryann to uncover existing wording for
describing SOAP so
>> it can be put into Section 3.2 of the bindings document.
Maryann, Hal and myself propose the following text for this AI. I also plan to include the proposed text in the upcoming bindings document draft. The second paragraph is derived/modified from the SOAP 1.2 Primer (probably should include reference). Draft text:
"SOAP is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. It uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation specific semantics. Two major design goals for SOAP are simplicity and extensibility <http://www.w3.org/TR/2003/REC-soap12-part1-20030624/>. SOAP attempts to meet these goals by omitting, from the messaging framework, features that are often found in distributed systems. Such features include but are not limited to "reliability", "security", "correlation", "routing", and "Message Exchange Patterns" (MEPs).
A SOAP message is fundamentally a one-way transmission between
SOAP nodes from a SOAP sender to a SOAP receiver, possibly routed through one or
more SOAP intermediaries. SOAP messages are expected to be combined by
applications to implement more complex interaction patterns ranging from
request/response to multiple, back-and-forth "conversational" exchanges. A SOAP
message is an XML schema definition and associated processing rules, defining a
SOAP Envelope, SOAP header block and SOAP body."