- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 22 Apr 2005 15:06:50 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv4529
Modified Files:
ws-addr-core.xml
Log Message:
Added resolution to lc2 - assorted editorial changes
Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.54
retrieving revision 1.55
diff -C2 -d -r1.54 -r1.55
*** ws-addr-core.xml 30 Mar 2005 21:02:05 -0000 1.54
--- ws-addr-core.xml 22 Apr 2005 15:06:48 -0000 1.55
***************
*** 246,251 ****
<p>The wsa:EndpointReferenceType type is used wherever a Web service endpoint is
referenced. The following describes the contents of this type:</p>
- <example>
- <head>Structure of the wsa:EndpointReference element.</head>
<eg xml:space="preserve"
>
--- 246,249 ----
***************
*** 258,264 ****
<wsa:Metadata> ... </wsa:Metadata>?
<xs:any/>*
! </wsa:EndpointReference>
! </eg>
! </example>
<p>The following describes the attributes and elements listed in the schema overview
above:</p>
--- 256,260 ----
<wsa:Metadata> ... </wsa:Metadata>?
<xs:any/>*
! </wsa:EndpointReference></eg>
<p>The following describes the attributes and elements listed in the schema overview
above:</p>
***************
*** 305,309 ****
<label> /wsa:EndpointReference/wsa:ReferenceParameters/{any}</label>
<def>
! <p>Each element information item of found in [reference parameters]
(including all of its [children], [attributes] and [in-scope
namespaces]) is represented as is.</p>
--- 301,305 ----
<label> /wsa:EndpointReference/wsa:ReferenceParameters/{any}</label>
<def>
! <p>Each element information item found in [reference parameters]
(including all of its [children], [attributes] and [in-scope
namespaces]) is represented as is.</p>
***************
*** 435,439 ****
restricted to the usual single Request, single Reply pattern, or to a particular
WSDL MEP. The contract between the interacting parties may specify that multiple or
! even a variable number or replies be delivered. </p>
<p> The set of message addressing properties defined in this specification
is sufficient for many simple variations of one-way and request-reply
--- 431,435 ----
restricted to the usual single Request, single Reply pattern, or to a particular
WSDL MEP. The contract between the interacting parties may specify that multiple or
! even a variable number of replies be delivered. </p>
<p> The set of message addressing properties defined in this specification
is sufficient for many simple variations of one-way and request-reply
***************
*** 472,476 ****
this message. When formulating a fault message as defined in <specref
ref="formreplymsg"/>, the sender MUST use the contents of the [fault
! endpoint], when present, of the message being replied to to formulate
the fault message. If this property is present, the [message id]
property is REQUIRED.</p>
--- 468,472 ----
this message. When formulating a fault message as defined in <specref
ref="formreplymsg"/>, the sender MUST use the contents of the [fault
! endpoint], when present, of the message being replied to formulate
the fault message. If this property is present, the [message id]
property is REQUIRED.</p>
***************
*** 564,574 ****
that can be easily secured as a unit. These properties are immutable and not
intended to be modified along a message path. </p>
! <p>The following describes the XML Infoset representation of message addressing
properties:</p>
- <example>
- <head>XML Infoset representation of message addressing properties.</head>
<eg xml:space="preserve"
>
! <wsa:MessageID> xs:anyURI </wsa:MessageID>
<wsa:RelatesTo RelationshipType="..."?>xs:anyURI</wsa:RelatesTo>
<wsa:To>xs:anyURI</wsa:To>
--- 560,568 ----
that can be easily secured as a unit. These properties are immutable and not
intended to be modified along a message path. </p>
! <p>The following shows the XML Infoset representation of message addressing
properties:</p>
<eg xml:space="preserve"
>
! <wsa:MessageID>xs:anyURI </wsa:MessageID>
<wsa:RelatesTo RelationshipType="..."?>xs:anyURI</wsa:RelatesTo>
<wsa:To>xs:anyURI</wsa:To>
***************
*** 577,582 ****
<wsa:ReplyTo>endpoint-reference</wsa:ReplyTo>
<wsa:FaultTo>endpoint-reference</wsa:FaultTo>
! </eg>
! </example>
<p>The following describes the attributes and elements listed in the schema overview
above:</p>
--- 571,576 ----
<wsa:ReplyTo>endpoint-reference</wsa:ReplyTo>
<wsa:FaultTo>endpoint-reference</wsa:FaultTo>
! <wsa:ReferenceParameters>xs:any*</wsa:FaultTo>
! </eg>
<p>The following describes the attributes and elements listed in the schema overview
above:</p>
***************
*** 667,671 ****
<label> /[reference parameters]*</label>
<def>
! <p>Each element information item of found in [reference parameters]
(including all of its [children], [attributes] and [in-scope
namespaces]) is represented as is.</p>
--- 661,665 ----
<label> /[reference parameters]*</label>
<def>
! <p>Each element information item found in [reference parameters]
(including all of its [children], [attributes] and [in-scope
namespaces]) is represented as is.</p>
Received on Friday, 22 April 2005 15:06:52 UTC