- From: David Fallside <fallside@us.ibm.com>
- Date: Thu, 6 Jun 2002 15:02:43 -0700
- To: xmlp-comments@w3.org, ylafon@w3.org
- Cc: frystyk@microsoft.com, "Christopher Ferris" <chris.ferris@sun.com>, "David Orchard" <david.orchard@bea.com>, distobj@acm.org, highland.m.mountain@intel.com, "Marc Hadley" <marc.hadley@sun.com>, "Jean-Jacques Moreau" <moreau@crf.canon.fr>, "Noah Mendelsohn" <noah_mendelsohn@us.ibm.com>
Yves, pls capture the following as an issue in the LC issues list. It was submitted by Henrik as the result of GETF work. ==================================== From [1], this should replace the 2nd paragraph in section 2 [3]: This section defines the SOAP distributed processing model. The SOAP processing model specifies how a SOAP receiver node processes a SOAP message. It applies to a single message only, in isolation from any other SOAP message. The SOAP processing model itself does not maintain any state or perform any correlation or coordination between messages, even, for example, when used in combination with a feature which involves sending multiple SOAP messages in sequence, each subsequent message depending on the response to the previous message. It is the responsibility of each such features to define such combined processing. Section 4. SOAP Protocol Binding Framework defines a framework for describing the rules for how SOAP messages can be exchanged over a variety of underlying protocols. Section 3. SOAP Extensibility Model describes how SOAP can be extended and how SOAP extensions might interact with the SOAP processing model and the SOAP protocol binding framework. [1] http://lists.w3.org/Archives/Public/xml-dist-app/2002Jun/0028.html [3] http://www.w3.org/2000/xp/Group/1/10/11/soap12-part1.xml#msgexchngmdl ================================== ............................................ David C. Fallside, IBM Ext Ph: 530.477.7169 Int Ph: 544.9665 fallside@us.ibm.com
Received on Thursday, 6 June 2002 18:08:12 UTC