W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > April to June 2005

2004/ws/addressing ws-addr-soap.xml,1.47,1.48

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 22 Apr 2005 15:27:32 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DP044-0002Up-2F@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv9583

Modified Files:
	ws-addr-soap.xml 
Log Message:
Added resolution to lc1 - clarified impact of omitting [message id], [reply endpoint] and [fault endpoint] on fault message generation

Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -C2 -d -r1.47 -r1.48
*** ws-addr-soap.xml	12 Apr 2005 13:17:44 -0000	1.47
--- ws-addr-soap.xml	22 Apr 2005 15:27:29 -0000	1.48
***************
*** 267,272 ****
                      targetted at the ultimate recipient in the SOAP message path (note that
                      extensions to WS-Addressing could be written to specify different targetting).
!                         <specref ref="bindrefp"/> describes additional processing required when binding 
!                     message addressing properties to SOAP header blocks.</p>
                  <p>When receiving a message, the abstract properties are populated from their
                      corresponding element information items in the message. Note that the message
--- 267,272 ----
                      targetted at the ultimate recipient in the SOAP message path (note that
                      extensions to WS-Addressing could be written to specify different targetting).
!                         <specref ref="bindrefp"/> describes additional processing required when
!                     binding message addressing properties to SOAP header blocks.</p>
                  <p>When receiving a message, the abstract properties are populated from their
                      corresponding element information items in the message. Note that the message
***************
*** 277,291 ****
              <div2 id="bindrefp">
                  <head>Binding Message Addressing Properties</head>
!                 <p>When a message is be addressed to an endpoint, the values of the SOAP 1.2 Addressing
!                     1.0 Feature properties
!                     are mapped to the message as SOAP header blocks with the following additional
!                     modifications:</p>
                  <ulist>
                      <item>
!                         <p>The value of the &nsuri;/feature/ReferenceParameters property
!                             is added to the SOAP
!                             message header. The element information item of each [reference parameter]
!                             (including all of its [children], [attributes] and [in-scope
!                             namespaces]) is added as a SOAP header block in the new message.</p>
                      </item>
                      <item>
--- 277,290 ----
              <div2 id="bindrefp">
                  <head>Binding Message Addressing Properties</head>
!                 <p>When a message is be addressed to an endpoint, the values of the SOAP 1.2
!                     Addressing 1.0 Feature properties are mapped to the message as SOAP header
!                     blocks with the following additional modifications:</p>
                  <ulist>
                      <item>
!                         <p>The value of the &nsuri;/feature/ReferenceParameters property is
!                             added to the SOAP message header. The element information item of each
!                             [reference parameter] (including all of its [children], [attributes] and
!                             [in-scope namespaces]) is added as a SOAP header block in the new
!                             message.</p>
                      </item>
                      <item>
***************
*** 321,328 ****
  &lt;/wsa:EndpointReference&gt;</eg>
                  </example>
!                 <p>The address value is copied in the "To"
!                     header block and the "CustomerKey" and "ShoppingCart" elements are copied
!                     literally as a header blocks in a SOAP message addressed to this endpoint. The
!                     resulting SOAP message would look as follows:</p>
                  <example>
                      <head>Example endpoint reference mapped to SOAP message header blocks.</head>
--- 320,327 ----
  &lt;/wsa:EndpointReference&gt;</eg>
                  </example>
!                 <p>The address value is copied in the "To" header block and the "CustomerKey" and
!                     "ShoppingCart" elements are copied literally as a header blocks in a SOAP
!                     message addressed to this endpoint. The resulting SOAP message would look as
!                     follows:</p>
                  <example>
                      <head>Example endpoint reference mapped to SOAP message header blocks.</head>
***************
*** 353,358 ****
                  ensure interoperability with a broad range of devices, all conformant
                  implementations that include support for SOAP 1.1 MUST support the SOAP 1.1
!                 Addressing 1.0 Extension. This SOAP 1.1 extension is provided for backwards 
! 			    compatibility only.</p>
              <div2 id="s11extname">
                  <head>Extension Name</head>
--- 352,357 ----
                  ensure interoperability with a broad range of devices, all conformant
                  implementations that include support for SOAP 1.1 MUST support the SOAP 1.1
!                 Addressing 1.0 Extension. This SOAP 1.1 extension is provided for backwards
!                 compatibility only.</p>
              <div2 id="s11extname">
                  <head>Extension Name</head>
***************
*** 392,402 ****
                  preamble in each subsection is met.</p>
              <p>Endpoints compliant with this specification MUST include the required message
!                 addressing properties serialized as SOAP headers in all fault messages. Fault
!                 messages are correlated as replies using the [relationship] property as defined in
!                 Section 3. The [action] property below designates WS-Addressing fault messages:</p>
              <eg xml:space="preserve">
  &nsuri;/fault
  </eg>
!             <p>The definitions of faults use the following properties:</p>
              <p> [Code] The fault code.</p>
              <p> [Subcode] The fault subcode.</p>
--- 391,407 ----
                  preamble in each subsection is met.</p>
              <p>Endpoints compliant with this specification MUST include the required message
!                 addressing properties serialized as SOAP headers in generated fault messages. When
!                 the input message contains a [message id] property, fault messages are correlated as
!                 replies using the [relationship] property as defined in &wsa-core.title;[<bibref
!                     ref="WSADDR-CORE"/>]. Omission of the [message id] property in an input message
!                 may impact the correlation of a fault message to the message that caused the fault
!                 message to be generated. Omission of the [fault endpoint] or [reply endpoint] properties in input
!                 messages may affect the ability to deliver a generated fault message</p>
!             <p>The [action] property below
!                 designates WS-Addressing fault messages:</p>
              <eg xml:space="preserve">
  &nsuri;/fault
  </eg>
!             <p>The definitions of faults uses the following properties:</p>
              <p> [Code] The fault code.</p>
              <p> [Subcode] The fault subcode.</p>
***************
*** 552,556 ****
                      href="&w3c-designation-wsa-core;">
                      <titleref>&wsa-core.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
! <!--
                  <bibl key="WS-Addressing-WSDL" id="WSADDR-WSDL"
                      href="&w3c-designation-wsa-wsdl;">
--- 557,561 ----
                      href="&w3c-designation-wsa-core;">
                      <titleref>&wsa-core.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
!                 <!--
                  <bibl key="WS-Addressing-WSDL" id="WSADDR-WSDL"
                      href="&w3c-designation-wsa-wsdl;">
***************
*** 578,583 ****
                      <titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
                      Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
!                     Consortium, 4 February 2004. This version of the XML
!                     1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
                          href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
                      available at http://www.w3.org/TR/REC-xml. </bibl>
--- 583,588 ----
                      <titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
                      Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
!                     Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
!                     http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
                          href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
                      available at http://www.w3.org/TR/REC-xml. </bibl>
***************
*** 599,606 ****
                  <bibl id="XMLSchemaP1" key="XML Schema Structures"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
!                     <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson, D. Beech, M.
!                     Maloney, and N. Mendelsohn, Editors. World Wide
! 		    Web Consortium, 28 October 2004. This
!                     version of the XML Schema Part 1 Recommendation is
                      http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
                          href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
--- 604,610 ----
                  <bibl id="XMLSchemaP1" key="XML Schema Structures"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
!                     <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson,
!                     D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 28
!                     October 2004. This version of the XML Schema Part 1 Recommendation is
                      http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
                          href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
***************
*** 608,616 ****
                  <bibl key="XML Schema Datatypes" id="XMLSchemaP2"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
!                     <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and A. Malhotra,
!                     Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema
!                     Part 2 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The
!                         <loc href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
!                         Part 2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
                  <bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
                      href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
--- 612,621 ----
                  <bibl key="XML Schema Datatypes" id="XMLSchemaP2"
                      href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
!                     <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and
!                     A. Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This version
!                     of the XML Schema Part 2 Recommendation is
!                     http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <loc
!                         href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema Part
!                     2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
                  <bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
                      href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
Received on Friday, 22 April 2005 15:27:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:40 GMT