- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 22 Apr 2005 18:49:34 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv8571
Modified Files:
ws-addr-soap.xml
Log Message:
Added resolution to lc23 - changed IRI to URI for constant values that are URIs.
Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -C2 -d -r1.48 -r1.49
*** ws-addr-soap.xml 22 Apr 2005 15:27:29 -0000 1.48
--- ws-addr-soap.xml 22 Apr 2005 18:49:32 -0000 1.49
***************
*** 67,93 ****
xmlns:wsa="&nsuri;">
(002) <S:Header>
! (003) <wsa:MessageID>
! (004) http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA
! (005) </wsa:MessageID>
! (006) <wsa:ReplyTo>
! (007) <wsa:Address>http://example.com/business/client1</wsa:Address>
! (008) </wsa:ReplyTo>
! (009) <wsa:To>http://example.com/fabrikam/Purchasing</wsa:To>
! (010) <wsa:Action>http://example.com/fabrikam/SubmitPO</wsa:Action>
! (011) </S:Header>
! (012) <S:Body>
! (013) ...
! (014) </S:Body>
! (015) </S:Envelope>
</eg>
! <p>Lines (002) to (011) represent the header of the SOAP message where the
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 addressing 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 IRI identifying expected semantics.</p>
</example>
<div2 id="notation">
--- 67,91 ----
xmlns:wsa="&nsuri;">
(002) <S:Header>
! (003) <wsa:MessageID>http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA</wsa:MessageID>
! (004) <wsa:ReplyTo>
! (005) <wsa:Address>http://example.com/business/client1</wsa:Address>
! (006) </wsa:ReplyTo>
! (007) <wsa:To>http://example.com/fabrikam/Purchasing</wsa:To>
! (008) <wsa:Action>http://example.com/fabrikam/SubmitPO</wsa:Action>
! (009) </S:Header>
! (010) <S:Body>
! (011) ...
! (012) </S:Body>
! (013) </S:Envelope>
</eg>
! <p>Lines (002) to (009) represent the header of the SOAP message where the
mechanisms defined in the specification are used. The body is represented by
! lines (010) to (012).</p>
! <p>Lines (003) to (008) contain the message addressing properties serialized as SOAP
! header blocks. Specifically, line (003) specifies the identifier for
! this message and lines (004) to (006) specify the endpoint to which replies to
! this message should be sent as an Endpoint Reference. Line (007) specifies the
! address URI of the ultimate receiver of this message. Line (008) specifies an
! action URI identifying expected semantics.</p>
</example>
<div2 id="notation">
***************
*** 163,167 ****
<div2 id="s12featurename">
<head>Feature Name</head>
! <p>The SOAP 1.2 Addressing 1.0 Feature is named using the following IRI:</p>
<ulist>
<item>
--- 161,165 ----
<div2 id="s12featurename">
<head>Feature Name</head>
! <p>The SOAP 1.2 Addressing 1.0 Feature is named using the following URI:</p>
<ulist>
<item>
***************
*** 249,253 ****
<div2 id="s12modulename">
<head>Module Name</head>
! <p>The SOAP 1.2 Addressing 1.0 Module is identified using the following IRI:</p>
<ulist>
<item>
--- 247,251 ----
<div2 id="s12modulename">
<head>Module Name</head>
! <p>The SOAP 1.2 Addressing 1.0 Module is identified using the following URI:</p>
<ulist>
<item>
***************
*** 356,360 ****
<div2 id="s11extname">
<head>Extension Name</head>
! <p>The SOAP 1.1 Addressing 1.0 Extension is identified using the following IRI:</p>
<ulist>
<item>
--- 354,358 ----
<div2 id="s11extname">
<head>Extension Name</head>
! <p>The SOAP 1.1 Addressing 1.0 Extension is identified using the following URI:</p>
<ulist>
<item>
***************
*** 391,403 ****
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
--- 389,400 ----
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. Fault
! messages are correlated as replies using the [relationship] property as defined in
! &wsa-core.title;[<bibref ref="WSADDR-CORE"/>]. Note that omission of the [message id]
! property in an input message may impact the ability of a fault message receiver to
! correlate the 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 impact the delivery of a generated fault message</p>
! <p>The [action] property below designates WS-Addressing fault messages:</p>
<eg xml:space="preserve">
&nsuri;/fault
Received on Friday, 22 April 2005 18:49:39 UTC