- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 29 Jan 2010 04:25:34 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv26963
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
wsfrag.html wsfrag.xml
Log Message:
8196
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.155
retrieving revision 1.156
diff -u -d -r1.155 -r1.156
--- wseventing.html 28 Jan 2010 15:05:47 -0000 1.155
+++ wseventing.html 29 Jan 2010 04:25:32 -0000 1.156
@@ -76,22 +76,22 @@
7.2 <a href="#AccessControl">Access Control</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_2166">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2248">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2168">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2250">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2319">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2453">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2321">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2455">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2655">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2676">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2681">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2699">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2657">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2678">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2683">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2701">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2726">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2747">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2728">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2749">Multiple Event Information Metadata Sections</a><br/>
B <a href="#Schema">XML Schema</a><br/>
C <a href="#WSDL">WSDL</a><br/>
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -635,7 +635,20 @@
Namespace Declarations: The [in-scope namespaces]
property <a href="#XMLInfoset">[XML Infoset]</a> of
/s:Envelope/s:Body/*/wse:Filter.
- </p></li></ul></dd></dl><p>
+ </p></li></ul><p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the XPath expression appears
+ within the SOAP message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
+ </p></dd></dl><p>
Other components of the outline above are not further
constrained by this specification.
</p><p>
@@ -1494,7 +1507,7 @@
that indicate a particular security mechanism used to protect
the WS-Eventing operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2166" id="iddiv2_1_2166"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2168" id="iddiv2_1_2168"/>9.1 EventSource Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Eventing specification's definition of an event source
is through the use of the Web Services
@@ -1575,7 +1588,7 @@
compatible with those Policy Alternatives available of the
Notification WSDLs that the event source advertises.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2248" id="iddiv2_1_2248"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2250" id="iddiv2_1_2250"/>9.2 SubscriptionManager Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Eventing specification's definition of a subscription manager
is through the use of the Web Services
@@ -1660,7 +1673,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2319" id="iddiv2_1_2319"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2321" id="iddiv2_1_2321"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1712,7 +1725,7 @@
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2453" id="iddiv2_1_2453"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2455" id="iddiv2_1_2455"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1816,7 +1829,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2645" id="idexample_1_2645"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2647" id="idexample_1_2647"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wse="http://www.w3.org/2009/09/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1836,7 +1849,7 @@
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><div class="div3">
-<h4><a name="iddiv3_1_2655" id="iddiv3_1_2655"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2657" id="iddiv3_1_2657"/>A.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an event source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1847,7 +1860,7 @@
be equal to the value of its wse:EventDescriptions/@targetNamespace. An
event source MUST NOT have more than one EventDescriptions document.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2676" id="iddiv3_1_2676"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2678" id="iddiv3_1_2678"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST be possible to determine how a
given wse:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1859,7 +1872,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4_1_2681" id="iddiv4_1_2681"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2683" id="iddiv4_1_2683"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wse:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1873,7 +1886,7 @@
of the wse:eventType element corresponding to the type of the
event being transmitted.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2699" id="iddiv4_1_2699"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2701" id="iddiv4_1_2701"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
The information about an Event Type contained in the eventType element
binds to a Wrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1897,7 +1910,7 @@
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2720" id="idexample_1_2720"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2722" id="idexample_1_2722"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1932,7 +1945,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2726" id="iddiv3_1_2726"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2728" id="iddiv3_1_2728"/>A.2.1 Retrieving Notification WSDLs</h4><p>
Although there are many ways in which an event source can make
Notification WSDLs available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1948,7 +1961,7 @@
Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2747" id="iddiv2_1_2747"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2749" id="iddiv2_1_2749"/>A.3 Multiple Event Information Metadata Sections</h3><p>
When WS-MetadataExchange is used to retrieve metadata about an event
source, recipients of mex:Metadata elements that contain Metadata
Sections with both the
@@ -2538,4 +2551,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288">8288</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</a></td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986">7986</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986">7986</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- wsfrag.xml 29 Jan 2010 04:10:58 -0000 1.49
+++ wsfrag.xml 29 Jan 2010 04:25:32 -0000 1.50
@@ -1134,12 +1134,6 @@
</example>
<p>
- The namespace bindings are evaluated against any namespace
- declarations that are in scope where the XPath appears within the SOAP
- message.
- </p>
-
- <p>
The <follower> production allows for special-casing of
the final tokens of the XPath allowing it to end in either an attribute
or text.
@@ -1216,6 +1210,21 @@
message using the same serialization as for the XPath 1.0 language.
This serialization mechanism MUST NOT be used in the PutRequest message.
</p>
+
+ <p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the expression appears within the SOAP
+ message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
+ </p>
</div1>
<div1 id="XPath10">
@@ -1410,6 +1419,21 @@
</example>
<p>The nodes in the node-set MAY be serialized in any order.</p>
+
+ <p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the expression appears within the SOAP
+ message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
+ </p>
</div1>
@@ -2128,6 +2152,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8191">8191</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/28 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -d -r1.47 -r1.48
--- wsfrag.html 29 Jan 2010 04:10:58 -0000 1.47
+++ wsfrag.html 29 Jan 2010 04:25:32 -0000 1.48
@@ -628,10 +628,6 @@
The <qualified_name> production allows the XML naming
tokens to be either namespace-qualified or unqualified:
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /ns1:a/ns2:b/c</pre></div></div><p>
- The namespace bindings are evaluated against any namespace
- declarations that are in scope where the XPath appears within the SOAP
- message.
- </p><p>
The <follower> production allows for special-casing of
the final tokens of the XPath allowing it to end in either an attribute
or text.
@@ -671,6 +667,19 @@
Text and attribute nodes MUST be serialized in the GetResponse
message using the same serialization as for the XPath 1.0 language.
This serialization mechanism MUST NOT be used in the PutRequest message.
+ </p><p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the expression appears within the SOAP
+ message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
</p></div><div class="div1">
<h2><a name="XPath10" id="XPath10"/>7 XPath 1.0 Expression Language</h2><p>
The XPath 1.0 expression language uses an XPath to reference specific
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -d -r1.108 -r1.109
--- wsenum.html 29 Jan 2010 04:18:41 -0000 1.108
+++ wsenum.html 29 Jan 2010 04:25:32 -0000 1.109
@@ -69,11 +69,11 @@
4.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
5 <a href="#Security">Security Considerations</a><br/>
6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 6.1 <a href="#iddiv2_1_2017">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_2019">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2112">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2298">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2114">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2300">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -514,7 +514,20 @@
Namespace Declarations: The
[in-scope namespaces] property <a href="#XMLInfoset">[XML Infoset]</a>
of <b>[Body]</b>/wsen:Enumerate/wsen:Filter.
- </p></li></ul></dd></dl><p>
+ </p></li></ul><p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the XPath expression appears
+ within the SOAP message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
+ </p></dd></dl><p>
Other components of the outline above are not
further constrained by this specification.
</p><p>
@@ -1301,7 +1314,7 @@
that indicate a particular security mechanism used to protect
the WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2017" id="iddiv2_1_2017"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_2019" id="iddiv2_1_2019"/>6.1 Enumeration Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Enumeration specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1404,7 +1417,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2112" id="iddiv2_1_2112"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2114" id="iddiv2_1_2114"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1476,7 +1489,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2298" id="iddiv2_1_2298"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2300" id="iddiv2_1_2300"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -1986,4 +1999,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157">8157</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157">8157</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -d -r1.101 -r1.102
--- wsenum.xml 29 Jan 2010 04:18:41 -0000 1.101
+++ wsenum.xml 29 Jan 2010 04:25:32 -0000 1.102
@@ -897,6 +897,21 @@
</p>
</item>
</ulist>
+
+ <p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the XPath expression appears
+ within the SOAP message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
+ </p>
</def>
</gitem>
</glist>
@@ -3672,6 +3687,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8157">8157</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/28 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -d -r1.149 -r1.150
--- wseventing.xml 28 Jan 2010 15:05:47 -0000 1.149
+++ wseventing.xml 29 Jan 2010 04:25:32 -0000 1.150
@@ -1117,6 +1117,21 @@
</p>
</item>
</ulist>
+
+ <p>
+ The namespace bindings are evaluated against any namespace
+ declarations that are in scope where the XPath expression appears
+ within the SOAP message.
+ Note that the evaluation of expressions that rely on such context
+ dependent bindings is fragile in the face of transformations that alter
+ namespace prefixes. Such transformations might occur during the
+ transmission, processing, storage, or retrieval of a request. Clients
+ that wish to isolate expressions from the effects of any changes to the
+ namespace prefixes in the containing SOAP message are advised to
+ construct expressions in a manner that avoids the use of namespace
+ prefixes. For example, use an expression such as
+ "/a[namespace-uri()='http://www.example.com']" not "/ns1:a".
+ </p>
</def>
</gitem>
</glist>
@@ -4642,6 +4657,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986">7986</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/28 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Friday, 29 January 2010 04:25:37 UTC