12051 2011-02-13 01:49:21 +0000 WS-E: Problem with Filter XPath suggestion 2011-09-13 21:35:01 +0000 1 1 1 Unclassified WS-Resource Access Eventing CR All All CLOSED REMIND http://www.w3.org/2002/ws/ra/snapshots/cr/wseventing.html hasProposal P2 normal --- 1 lli5 public-ws-resource-access-notifications dug public-ws-resource-access-notifications oldest_to_newest 45445 0 lli5 2011-02-13 01:49:21 +0000 WS-Eventing Section 4.1 states that: 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". This paragraph implies that xpath expression: /a[namespace-uri()='http://www.example.com'] is equivalent to: /ns1:a However, it is not. The first expression will evaluate false on XML: <ns1:a xmlns:ns1="http://www.example.com" /> whereas the second one is true (given the proper namespace context). The XPath expression equivalent to the second one is: /*[local-name()='a' and namespace-uri()='http://www.example.com'] Proposal: Use the equivalent XPath expression instead. 45609 1 dug 2011-02-15 17:50:42 +0000 Enum needs this fix too 45610 2 bob 2011-02-15 17:52:39 +0000 resolved as proposed and also to be applied to enum