- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 27 Mar 2006 19:48:03 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv18432
Modified Files:
ws-addr-wsdl.xml
Log Message:
Used alternate words instead of lowercase RFC2119 terms
Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.84
retrieving revision 1.85
diff -C2 -d -r1.84 -r1.85
*** ws-addr-wsdl.xml 24 Mar 2006 15:34:39 -0000 1.84
--- ws-addr-wsdl.xml 27 Mar 2006 19:48:00 -0000 1.85
***************
*** 146,150 ****
implementation of the specification.</p>
<p>WS-Addressing is defined in terms of the XML Information Set [<bibref
! ref="XMLInfoSet"/>]. WS-Addressing may be used with SOAP [<bibref
ref="SOAP12-PART1"/>] as described in &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>]. The examples in this specification use an XML 1.0
--- 146,150 ----
implementation of the specification.</p>
<p>WS-Addressing is defined in terms of the XML Information Set [<bibref
! ref="XMLInfoSet"/>]. WS-Addressing can be used with SOAP [<bibref
ref="SOAP12-PART1"/>] as described in &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>]. The examples in this specification use an XML 1.0
***************
*** 228,232 ****
to access the referenced endpoint. The alternatives are provided by the
different endpoints of the embedded service. In the case of WSDL 1.1, additional
! ports may be conveyed by the WSDL 1.1 service definition which are not
alternative access channels to the endpoint. In that case, if the InterfaceName
or ServiceName elements are also included in the metadata section of the EPR,
--- 228,232 ----
to access the referenced endpoint. The alternatives are provided by the
different endpoints of the embedded service. In the case of WSDL 1.1, additional
! ports can be conveyed by the WSDL 1.1 service definition which are not
alternative access channels to the endpoint. In that case, if the InterfaceName
or ServiceName elements are also included in the metadata section of the EPR,
***************
*** 313,317 ****
<p>
WS-Addressing defines an empty global element,
! wsaw:UsingAddressing, that may be used to indicate
that an endpoint conforms to the WS-Addressing
specification. The wsdl:required attribute MAY be
--- 313,317 ----
<p>
WS-Addressing defines an empty global element,
! wsaw:UsingAddressing, that can be used to indicate
that an endpoint conforms to the WS-Addressing
specification. The wsdl:required attribute MAY be
***************
*** 387,391 ****
defined by &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>].The presence of this element
! may extend the semantics of the endpoint's WSDL
binding. </p>
<example>
--- 387,391 ----
defined by &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>].The presence of this element
! can extend the semantics of the endpoint's WSDL
binding. </p>
<example>
***************
*** 476,480 ****
<div3>
<head>Other Uses of UsingAddressing Extension Element</head>
! <p>The wsaw:UsingAddressing element may also be used in other contexts
(e.g., as a policy assertion in a policy framework). Its use
and that of related elements and attributes including
--- 476,480 ----
<div3>
<head>Other Uses of UsingAddressing Extension Element</head>
! <p>The wsaw:UsingAddressing element MAY also be used in other contexts
(e.g., as a policy assertion in a policy framework). Its use
and that of related elements and attributes including
***************
*** 491,495 ****
<p>
WS-Addressing defines a wsaw:Anonymous element that
! may only be used in conjunction with
wsaw:UsingAddressing (or its equivalent wsoap:module)
element. The usage of wsaw:Anonymous element is
--- 491,495 ----
<p>
WS-Addressing defines a wsaw:Anonymous element that
! is only used in conjunction with
wsaw:UsingAddressing (or its equivalent wsoap:module)
element. The usage of wsaw:Anonymous element is
***************
*** 610,614 ****
<div2 id="wsdlsoapmodule">
<head>WSDL SOAP Module</head>
! <p> In WSDL 2.0, a SOAP Module component may be used to declare the use of the
WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
SOAP Module component is semantically equivalent to the {addressing}
--- 610,614 ----
<div2 id="wsdlsoapmodule">
<head>WSDL SOAP Module</head>
! <p> In WSDL 2.0, a SOAP Module component can be used to declare the use of the
WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
SOAP Module component is semantically equivalent to the {addressing}
***************
*** 637,641 ****
<div1 id="mapvaluesinwsdl">
<head>Specifying Message Addressing Properties in WSDL</head>
! <p>This section describes how the values of certain message addressing properties may be
specified in WSDL. In some cases the values of message addressing properties are
specified using existing WSDL constructs, in other cases new WSDL extensions are
--- 637,641 ----
<div1 id="mapvaluesinwsdl">
<head>Specifying Message Addressing Properties in WSDL</head>
! <p>This section describes how the values of certain message addressing properties can be
specified in WSDL. In some cases the values of message addressing properties are
specified using existing WSDL constructs, in other cases new WSDL extensions are
***************
*** 669,673 ****
<div3 id="explicitaction">
<head>Explicit Association</head>
! <p>WS-Addressing defines a global attribute, wsaw:Action, that may be used to
explicitly define the value of the [action] property for messages in a WSDL
description. The type of the attribute is xs:anyURI and it is used as an
--- 669,673 ----
<div3 id="explicitaction">
<head>Explicit Association</head>
! <p>WS-Addressing defines a global attribute, wsaw:Action, that can be used to
explicitly define the value of the [action] property for messages in a WSDL
description. The type of the attribute is xs:anyURI and it is used as an
***************
*** 758,762 ****
that for IRI schemes other than URNs which aren't path-based
(i.e. those that outlaw the "/" character), the default action
! value may not conform to the rules of the IRI scheme. Authors
are advised to specify explicit values in the WSDL in this
case.</p>
--- 758,762 ----
that for IRI schemes other than URNs which aren't path-based
(i.e. those that outlaw the "/" character), the default action
! value might not conform to the rules of the IRI scheme. Authors
are advised to specify explicit values in the WSDL in this
case.</p>
***************
*** 902,906 ****
that for IRI schemes other than URNs which aren't path-based
(i.e. those that outlaw the "/" character), the default action
! value may not conform to the rules of the IRI scheme. Authors
are advised to specify explicit values in the WSDL in this
case.</p>
--- 902,906 ----
that for IRI schemes other than URNs which aren't path-based
(i.e. those that outlaw the "/" character), the default action
! value might not conform to the rules of the IRI scheme. Authors
are advised to specify explicit values in the WSDL in this
case.</p>
***************
*** 1065,1069 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1065,1069 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1072,1076 ****
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1072,1076 ----
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1079,1083 ****
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but may be included to facilitate longer running
message exchanges.</td>
</tr>
--- 1079,1083 ----
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but could be included to facilitate longer running
message exchanges.</td>
</tr>
***************
*** 1092,1096 ****
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1092,1096 ----
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1124,1128 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1124,1128 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1149,1153 ****
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1149,1153 ----
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1176,1180 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1176,1180 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1183,1187 ****
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1183,1187 ----
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1190,1194 ****
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but may be included to facilitate longer running
message exchanges.</td>
</tr>
--- 1190,1194 ----
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but could be included to facilitate longer running
message exchanges.</td>
</tr>
***************
*** 1252,1256 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1252,1256 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1259,1263 ****
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1259,1263 ----
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1266,1270 ****
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but may be included to facilitate longer running
message exchanges.</td>
</tr>
--- 1266,1270 ----
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but could be included to facilitate longer running
message exchanges.</td>
</tr>
***************
*** 1279,1283 ****
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1279,1283 ----
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1312,1316 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1312,1316 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1319,1323 ****
<td align="center">N*</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1319,1323 ----
<td align="center">N*</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1337,1341 ****
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1337,1341 ----
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1366,1370 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1366,1370 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1373,1377 ****
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1373,1377 ----
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1380,1384 ****
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but may be included to facilitate longer running
message exchanges.</td>
</tr>
--- 1380,1384 ----
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but could be included to facilitate longer running
message exchanges.</td>
</tr>
***************
*** 1425,1429 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1425,1429 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1450,1454 ****
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1450,1454 ----
<td align="center">N</td>
<td>Indicates relationship to a prior message. Unused in this MEP,
! but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1477,1481 ****
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but may be included to
facilitate longer running message exchanges.</td>
</tr>
--- 1477,1481 ----
<td>[source endpoint]</td>
<td align="center">N</td>
! <td>Message origin. Unused in this MEP, but could be included to
facilitate longer running message exchanges.</td>
</tr>
***************
*** 1484,1488 ****
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but may be included to facilitate longer running message
exchanges.</td>
</tr>
--- 1484,1488 ----
<td align="center">N</td>
<td>Intended receiver for replies to this message. Unused in this
! MEP, but could be included to facilitate longer running message
exchanges.</td>
</tr>
***************
*** 1491,1495 ****
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but may be included to facilitate longer running
message exchanges.</td>
</tr>
--- 1491,1495 ----
<td align="center">N</td>
<td>Intended receiver for faults related to this message. Unused in
! this MEP, but could be included to facilitate longer running
message exchanges.</td>
</tr>
Received on Monday, 27 March 2006 19:48:14 UTC