- From: Marc Hadley <mhadley@dev.w3.org>
- Date: Tue, 15 Feb 2005 22:06:29 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv29569
Modified Files:
ws-addr-soap.xml
Log Message:
Fixed some references to message information headers to message information properties
Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -C2 -d -r1.25 -r1.26
*** ws-addr-soap.xml 10 Feb 2005 11:09:24 -0000 1.25
--- ws-addr-soap.xml 15 Feb 2005 22:06:27 -0000 1.26
***************
*** 24,28 ****
<loc href="&w3c-designation-wsa-soap;">&w3c-designation-wsa-soap;</loc>
</publoc> &altlocs; <prevlocs>
! <loc href="&prevloc;">&prevloc;</loc>
</prevlocs>
<latestloc>
--- 24,28 ----
<loc href="&w3c-designation-wsa-soap;">&w3c-designation-wsa-soap;</loc>
</publoc> &altlocs; <prevlocs>
! <loc href="&prevloc;">&prevloc;</loc>
</prevlocs>
<latestloc>
***************
*** 59,63 ****
abstract properties defined in &wsa-core.title; to SOAP Messages.</p>
<p>The following example illustrates the use of these mechanisms in a SOAP 1.2 message
! being sent from http://example.com/business/client1 to http://example.com/fabrikam/Purchasing:</p>
<example>
<head>Use of message addressing properties in a SOAP 1.2 message.</head>
--- 59,64 ----
abstract properties defined in &wsa-core.title; to SOAP Messages.</p>
<p>The following example illustrates the use of these mechanisms in a SOAP 1.2 message
! being sent from http://example.com/business/client1 to
! http://example.com/fabrikam/Purchasing:</p>
<example>
<head>Use of message addressing properties in a SOAP 1.2 message.</head>
***************
*** 83,92 ****
mechanisms defined in the specification are used. The body is represented by
lines (012) to (014).</p>
! <p>Lines (003) to (010) contain the message information header blocks. Specifically,
! lines (003) to (005) specify the identifier for this message and lines (006) to
! (008) specify the endpoint to which replies to this message should be sent as an
! Endpoint Reference. Line (009) specifies the address URI of the ultimate
! receiver of this message. Line (010) specifies an Action URI identifying
! expected semantics.</p>
</example>
<div2 id="_Toc77464315">
--- 84,93 ----
mechanisms defined in the specification are used. The body is represented by
lines (012) to (014).</p>
! <p>Lines (003) to (010) contain the message information properties serialized as
! SOAP header blocks. Specifically, lines (003) to (005) specify the identifier
! for this message and lines (006) to (008) specify the endpoint to which replies
! to this message should be sent as an Endpoint Reference. Line (009) specifies
! the address URI of the ultimate receiver of this message. Line (010) specifies
! an Action URI identifying expected semantics.</p>
</example>
<div2 id="_Toc77464315">
***************
*** 97,108 ****
<p>When describing abstract data models, this specification uses the notational
convention used by XML Infoset [<bibref ref="XMLInfoSet"/>]. Specifically,
! abstract property names always appear in square brackets (e.g., [some property]).</p>
<p>When describing concrete XML schemas [<bibref ref="XMLSchemaP1"/>, <bibref
! ref="XMLSchemaP2"/>], this specification uses the notational convention of
WS-Security [<bibref ref="WS-Security"/>]. Specifically, each member of an
element's [children] or [attributes] property is described using an XPath-like
notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates
the presence of an element wildcard (<xs:any/>). The use of @{any}
! indicates the presence of an attribute wildcard (<xs:anyAttribute/>).</p>
</div2>
<div2 id="_Toc77464316">
--- 98,111 ----
<p>When describing abstract data models, this specification uses the notational
convention used by XML Infoset [<bibref ref="XMLInfoSet"/>]. Specifically,
! abstract property names always appear in square brackets (e.g., [some
! property]).</p>
<p>When describing concrete XML schemas [<bibref ref="XMLSchemaP1"/>, <bibref
! ref="XMLSchemaP2"/>], this specification uses the notational convention of
WS-Security [<bibref ref="WS-Security"/>]. Specifically, each member of an
element's [children] or [attributes] property is described using an XPath-like
notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates
the presence of an element wildcard (<xs:any/>). The use of @{any}
! indicates the presence of an attribute wildcard
! (<xs:anyAttribute/>).</p>
</div2>
<div2 id="_Toc77464316">
***************
*** 111,115 ****
listed in <specref ref="nsrefs"/>. Note that the choice of any namespace prefix
is arbitrary and not semantically significant (see [<bibref ref="XMLNS"/> ]).</p>
! <table id="nsrefs" border="1" summary="Namespace prefixes usage in this specification">
<caption>Prefixes and Namespaces used in this specification</caption>
<tbody>
--- 114,119 ----
listed in <specref ref="nsrefs"/>. Note that the choice of any namespace prefix
is arbitrary and not semantically significant (see [<bibref ref="XMLNS"/> ]).</p>
! <table id="nsrefs" border="1"
! summary="Namespace prefixes usage in this specification">
<caption>Prefixes and Namespaces used in this specification</caption>
<tbody>
***************
*** 137,142 ****
</table>
<p>WS-Addressing is defined in terms of the XML Information Set [<bibref
! ref="XMLInfoSet"/>]. WS-Addressing is conformant to the SOAP 1.2 [<bibref
! ref="SOAP12-PART1"/>] processing model and is also compatible with SOAP
1.1[<bibref ref="SOAP11"/>] for backwards compatibility. WS-Addressing may
be used with WSDL [<bibref ref="WSDL20"/>] described services as described in
--- 141,146 ----
</table>
<p>WS-Addressing is defined in terms of the XML Information Set [<bibref
! ref="XMLInfoSet"/>]. WS-Addressing is conformant to the SOAP 1.2 [<bibref
! ref="SOAP12-PART1"/>] processing model and is also compatible with SOAP
1.1[<bibref ref="SOAP11"/>] for backwards compatibility. WS-Addressing may
be used with WSDL [<bibref ref="WSDL20"/>] described services as described in
***************
*** 162,166 ****
the absence of an applicable policy stating that a different mapping must be used,
the SOAP binding defined here is assumed to apply. To ensure interoperability with a
! broad range of devices, all conformant implementations MUST support the SOAP binding.</p>
<p>The SOAP binding for endpoint references is defined by the following three rules:</p>
<ulist>
--- 166,171 ----
the absence of an applicable policy stating that a different mapping must be used,
the SOAP binding defined here is assumed to apply. To ensure interoperability with a
! broad range of devices, all conformant implementations MUST support the SOAP
! binding.</p>
<p>The SOAP binding for endpoint references is defined by the following three rules:</p>
<ulist>
***************
*** 171,191 ****
</item>
<item>
! <p>Each
! <!-- Resolving i001
! [reference property] and
! -->
! [reference parameter] element becomes a header
! block in the SOAP message. The element information item of each
! <!-- Resolving i001
! [reference property] or
! -->
! [reference parameter] (including all of its [children],
! [attributes] and [in-scope namespaces]) is to be added as a header block in
! the new message.</p>
</item>
- <item>
- <p>Each header block added as a result of the above rule is annotated with a wsa:Type attribute whose value is <attval>parameter</attval>.
- </p>
- </item>
</ulist>
<p>The next example shows how the default SOAP binding for endpoint references is used
--- 176,188 ----
</item>
<item>
! <p>Each [reference parameter] element becomes a header block in the SOAP
! message. The element information item of each [reference parameter]
! (including all of its [children], [attributes] and [in-scope namespaces]) is
! added as a header block in the new message.</p>
! </item>
! <item>
! <p>Each header block added as a result of the above rule is annotated with a
! wsa:Type attribute whose value is <attval>parameter</attval>. </p>
</item>
</ulist>
<p>The next example shows how the default SOAP binding for endpoint references is used
***************
*** 193,197 ****
<example>
<head>Example endpoint reference.</head>
! <eg xml:space="preserve">
<wsa:EndpointReference
xmlns:wsa="&nsuri;"
--- 190,195 ----
<example>
<head>Example endpoint reference.</head>
! <eg xml:space="preserve"
! >
<wsa:EndpointReference
xmlns:wsa="&nsuri;"
***************
*** 219,223 ****
<example>
<head>Example endpoint reference mapped to SOAP message header blocks.</head>
! <eg xml:space="preserve">
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="&nsuri;"
--- 217,222 ----
<example>
<head>Example endpoint reference mapped to SOAP message header blocks.</head>
! <eg xml:space="preserve"
! >
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="&nsuri;"
***************
*** 240,247 ****
<p>The faults defined in this section are generated if the condition stated in the
preamble in each subsection is met.</p>
! <p>Endpoints compliant with this specification MUST include required message information
! headers on 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
--- 239,246 ----
<p>The faults defined in this section are generated if the condition stated in the
preamble in each subsection is met.</p>
! <p>Endpoints compliant with this specification MUST include the required message
! information 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
***************
*** 255,259 ****
<example>
<head>Binding of fault properties to SOAP 1.2 messages.</head>
! <eg xml:space="preserve">
<S:Envelope>
<S:Header>
--- 254,259 ----
<example>
<head>Binding of fault properties to SOAP 1.2 messages.</head>
! <eg xml:space="preserve"
! >
<S:Envelope>
<S:Header>
***************
*** 286,290 ****
<example>
<head>Binding of fault properties to SOAP 1.1 messages.</head>
! <eg xml:space="preserve">
<S11:Envelope>
<S11:Body>
--- 286,291 ----
<example>
<head>Binding of fault properties to SOAP 1.1 messages.</head>
! <eg xml:space="preserve"
! >
<S11:Envelope>
<S11:Body>
***************
*** 298,322 ****
</example>
<div2 id="_Toc77464329">
! <head> Invalid Message Information Header</head>
! <p>A message information header cannot be processed.</p>
<p> [Code] S:Sender</p>
! <p> [Subcode] wsa:InvalidMessageInformationHeader</p>
! <p> [Reason] A message information header is not valid and the message cannot be
processed. The validity failure can be either structural or semantic, e.g. a
[destination] that is not a URI or a [relationship] to a [message id] that was
never issued.</p>
! <p> [Detail] [invalid header]</p>
</div2>
<div2 id="_Toc77464330">
! <head> Message Information Header Required</head>
! <p>A required message information header is absent.</p>
<p> [Code] S:Sender</p>
! <p> [Subcode] wsa:MessageInformationHeaderRequired</p>
! <p> [Reason] A required message information header, To, MessageID, or Action, is not present.</p>
! <p> [Detail] [Missing Header QName]</p>
</div2>
<div2 id="_Toc77464331">
<head> Destination Unreachable</head>
! <p>No endpoint can be found capable of acting in the role of the [destination] property.</p>
<p> [Code] S:Sender</p>
<p> [Subcode] wsa:DestinationUnreachable</p>
--- 299,325 ----
</example>
<div2 id="_Toc77464329">
! <head> Invalid Message Information Property</head>
! <p>A message information property cannot be processed.</p>
<p> [Code] S:Sender</p>
! <p> [Subcode] wsa:InvalidMessageInformationProperty</p>
! <p> [Reason] A message information property is not valid and the message cannot be
processed. The validity failure can be either structural or semantic, e.g. a
[destination] that is not a URI or a [relationship] to a [message id] that was
never issued.</p>
! <p> [Detail] [invalid property]</p>
</div2>
<div2 id="_Toc77464330">
! <head> Message Information Property Required</head>
! <p>A required message information property is absent.</p>
<p> [Code] S:Sender</p>
! <p> [Subcode] wsa:MessageInformationPropertyRequired</p>
! <p> [Reason] A required message information property, To, MessageID, or Action, is not
! present.</p>
! <p> [Detail] [Missing Property QName]</p>
</div2>
<div2 id="_Toc77464331">
<head> Destination Unreachable</head>
! <p>No endpoint can be found capable of acting in the role of the [destination]
! property.</p>
<p> [Code] S:Sender</p>
<p> [Subcode] wsa:DestinationUnreachable</p>
***************
*** 343,347 ****
<p> [Subcode] wsa:EndpointUnavailable</p>
<p> [Reason] The endpoint is unable to process the message at this time.</p>
! <p> [Detail] <wsa:RetryAfter ...>[xs:NonNegativeInteger]</wsa:RetryAfter></p>
<p> The following describes the attributes and elements listed above:</p>
<glist>
--- 346,351 ----
<p> [Subcode] wsa:EndpointUnavailable</p>
<p> [Reason] The endpoint is unable to process the message at this time.</p>
! <p> [Detail] <wsa:RetryAfter
! ...>[xs:NonNegativeInteger]</wsa:RetryAfter></p>
<p> The following describes the attributes and elements listed above:</p>
<glist>
***************
*** 351,355 ****
<p>This element (of type xs:NonNegativeInteger) is a suggested minimum
duration in milliseconds to wait before retransmitting the message.
! If this element is omitted from the detail, the value is infinite.</p>
</def>
</gitem>
--- 355,360 ----
<p>This element (of type xs:NonNegativeInteger) is a suggested minimum
duration in milliseconds to wait before retransmitting the message.
! If this element is omitted from the detail, the value is
! infinite.</p>
</def>
</gitem>
***************
*** 370,377 ****
the mechanisms described in WS-Security [<bibref ref="WS-Security"/>]. In order to
properly secure messages, the body and all relevant headers need to be included in
! the signature. Specifically, the message information headers described in this
specification (e.g. <wsa:To>) need to be signed with the body in order
to "bind" the two together. It should be noted that for messages traveling through
! intermediaries, it is possible that some or all of the message information headers
may have multiple signatures when the message arrives at the ultimate receiver. It
is strongly recommended that the initial sender include a signature to prevent any
--- 375,382 ----
the mechanisms described in WS-Security [<bibref ref="WS-Security"/>]. In order to
properly secure messages, the body and all relevant headers need to be included in
! the signature. Specifically, the message information property headers described in this
specification (e.g. <wsa:To>) need to be signed with the body in order
to "bind" the two together. It should be noted that for messages traveling through
! intermediaries, it is possible that some or all of the message information property headers
may have multiple signatures when the message arrives at the ultimate receiver. It
is strongly recommended that the initial sender include a signature to prevent any
***************
*** 381,392 ****
ensure that a signature is provided with claims allowing it to speak for the
specified target in order to prevent certain classes of attacks (e.g. redirects). As
! well, care should be taken if the specified endpoint contains reference
! <!-- Resolving i001
! properties
! or
! -->
! parameters as unverified endpoint references could cause certain classes of
! header insertion attacks.</p>
! <p>The message information headers blocks may have their contents encrypted in order to
obtain end-to-end privacy, but care should be taken to ensure that intermediary
processors have access to required information (e.g. <wsa:To>).</p>
--- 386,393 ----
ensure that a signature is provided with claims allowing it to speak for the
specified target in order to prevent certain classes of attacks (e.g. redirects). As
! well, care should be taken if the specified endpoint contains reference
! parameters as unverified
! endpoint references could cause certain classes of header insertion attacks.</p>
! <p>The message information property header blocks may have their contents encrypted in order to
obtain end-to-end privacy, but care should be taken to ensure that intermediary
processors have access to required information (e.g. <wsa:To>).</p>
***************
*** 460,466 ****
<head> References</head>
<blist>
! <bibl key="WS-Addressing-Core" id="WSADDR-CORE" 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;">
<titleref>&wsa-wsdl.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
<bibl key="WSDL 2.0" id="WSDL20" href="">
--- 461,469 ----
<head> References</head>
<blist>
! <bibl key="WS-Addressing-Core" id="WSADDR-CORE"
! 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;">
<titleref>&wsa-wsdl.title;</titleref>, M. Gudgin, M. Hadley, Editors.</bibl>
<bibl key="WSDL 2.0" id="WSDL20" href="">
***************
*** 475,481 ****
S. Bradner, Author. Internet Engineering Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt. </bibl>
! <bibl id="RFC2396" key="RFC 3986"
! href="http://www.ietf.org/rfc/rfc3986.txt">
! T. Berners-Lee, et al, "Uniform Resource Identifier (URI): Generic Syntax,",
W3C/MIT, January 2005.</bibl>
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2000/REC-xml-20001006">
--- 478,483 ----
S. Bradner, Author. Internet Engineering Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt. </bibl>
! <bibl id="RFC2396" key="RFC 3986" href="http://www.ietf.org/rfc/rfc3986.txt"> T.
! Berners-Lee, et al, "Uniform Resource Identifier (URI): Generic Syntax,",
W3C/MIT, January 2005.</bibl>
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2000/REC-xml-20001006">
***************
*** 486,490 ****
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>
! <bibl id="XMLNS" key="XML Namespaces" href="http://www.w3.org/TR/1999/REC-xml-names-19990114">
<titleref>Namespaces in XML</titleref>, T. Bray, D. Hollander, and A. Layman,
Editors. World Wide Web Consortium, 14 January 1999. This version of the XML
--- 488,493 ----
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>
! <bibl id="XMLNS" key="XML Namespaces"
! href="http://www.w3.org/TR/1999/REC-xml-names-19990114">
<titleref>Namespaces in XML</titleref>, T. Bray, D. Hollander, and A. Layman,
Editors. World Wide Web Consortium, 14 January 1999. This version of the XML
***************
*** 492,503 ****
http://www.w3.org/TR/1999/REC-xml-names-19990114. The <loc
href="http://www.w3.org/TR/REC-xml-names">latest version of Namespaces in
! XML</loc> is available at http://www.w3.org/TR/REC-xml-names. </bibl>
! <bibl id="XMLInfoSet" key="XML Information Set" href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024">
<titleref>XML Information Set</titleref>, J. Cowan and R. Tobin, Editors. World
Wide Web Consortium, 24 October 2001. This version of the XML Information Set
Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The <loc
href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
! Set</loc> is available at http://www.w3.org/TR/xml-infoset. </bibl>
! <bibl id="XMLSchemaP1" key="XML Schema Structures" href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">
<titleref>XML Schema Part 1: Structures</titleref>, H. Thompson, D. Beech, M.
Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 2 May 2001. This
--- 495,508 ----
http://www.w3.org/TR/1999/REC-xml-names-19990114. The <loc
href="http://www.w3.org/TR/REC-xml-names">latest version of Namespaces in
! XML</loc> is available at http://www.w3.org/TR/REC-xml-names. </bibl>
! <bibl id="XMLInfoSet" key="XML Information Set"
! href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024">
<titleref>XML Information Set</titleref>, J. Cowan and R. Tobin, Editors. World
Wide Web Consortium, 24 October 2001. This version of the XML Information Set
Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The <loc
href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
! Set</loc> is available at http://www.w3.org/TR/xml-infoset. </bibl>
! <bibl id="XMLSchemaP1" key="XML Schema Structures"
! href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">
<titleref>XML Schema Part 1: Structures</titleref>, H. Thompson, D. Beech, M.
Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 2 May 2001. This
***************
*** 506,510 ****
href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
1</loc> is available at http://www.w3.org/TR/xmlschema-1. </bibl>
! <bibl key="XML Schema Datatypes" id="XMLSchemaP2" href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">
<titleref>XML Schema Part 2: Datatypes</titleref>, P. Byron and A. Malhotra,
Editors. World Wide Web Consortium, 2 May 2001. This version of the XML Schema
--- 511,516 ----
href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
1</loc> is available at http://www.w3.org/TR/xmlschema-1. </bibl>
! <bibl key="XML Schema Datatypes" id="XMLSchemaP2"
! href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">
<titleref>XML Schema Part 2: Datatypes</titleref>, P. Byron and A. Malhotra,
Editors. World Wide Web Consortium, 2 May 2001. This version of the XML Schema
***************
*** 512,516 ****
<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/">
<titleref>SOAP Version 1.2 Part 1: Messaging Framework</titleref>, M. Gudgin, M.
Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web
--- 518,523 ----
<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/">
<titleref>SOAP Version 1.2 Part 1: Messaging Framework</titleref>, M. Gudgin, M.
Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web
***************
*** 521,549 ****
1.2 Part 1: Messaging Framework"</loc> is available at
http://www.w3.org/TR/soap12-part1/. </bibl>
! <bibl id="WSDL11" key="WSDL 1.1"
! href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">E. Christensen, et al,
! <titleref>Web Services Description Language (WSDL) 1.1</titleref>, March 2001.</bibl>
<bibl id="SOAP11" key="SOAP 1.1"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Don Box, et al,
<titleref>Simple Object Access Protocol (SOAP) 1.1</titleref>, May 2000.</bibl>
<bibl id="WS-Security" key="WS-Security"
! href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">
! OASIS, <titleref>Web Services Security: SOAP Message Security</titleref>, March 2004.</bibl>
</blist>
</div1>
</body>
! <back>
!
! &acknowledgements;
!
! <inform-div1 id="changelog">
<head>Change Log</head>
<div2>
<head>Changes Since First Working Draft</head>
! <p role="ws-addr-soap.xml:20041206:20060101">Placeholder for auto change log generation.</p>
</div2>
<div2>
<head>Changes Since Submission</head>
! <p role="ws-addr-soap.xml:20041001:20041205">Placeholder for auto change log generation.</p>
</div2>
</inform-div1>
--- 528,555 ----
1.2 Part 1: Messaging Framework"</loc> is available at
http://www.w3.org/TR/soap12-part1/. </bibl>
! <bibl id="WSDL11" key="WSDL 1.1" href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"
! >E. Christensen, et al, <titleref>Web Services Description Language (WSDL)
! 1.1</titleref>, March 2001.</bibl>
<bibl id="SOAP11" key="SOAP 1.1"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Don Box, et al,
<titleref>Simple Object Access Protocol (SOAP) 1.1</titleref>, May 2000.</bibl>
<bibl id="WS-Security" key="WS-Security"
! href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"
! > OASIS, <titleref>Web Services Security: SOAP Message Security</titleref>,
! March 2004.</bibl>
</blist>
</div1>
</body>
! <back> &acknowledgements; <inform-div1 id="changelog">
<head>Change Log</head>
<div2>
<head>Changes Since First Working Draft</head>
! <p role="ws-addr-soap.xml:20041206:20060101">Placeholder for auto change log
! generation.</p>
</div2>
<div2>
<head>Changes Since Submission</head>
! <p role="ws-addr-soap.xml:20041001:20041205">Placeholder for auto change log
! generation.</p>
</div2>
</inform-div1>
Received on Tuesday, 15 February 2005 22:06:30 UTC