This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In Section 6, "XPath Level 1 Expression Language", of WS-Fragment it states that "The namespace bindings are evaluated against any namespace declarations that are in scope where the XPath appears within the SOAP message." This may lead to unpredictable behavior because, in general, the person/software that composed the wsf:Expression cannot know, a priori, what namespace declarations will be in scope (i.e. they don't know what the complete SOAP envelope will look like). Strawman Proposal: Use something like the <prefixMapping> element from CMDBf [1] [1] http://www.dmtf.org/standards/published_documents/DSP0252_1.0.0.pdf
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/att-0193/wsfrag-8196.zip
Resolved with comment#1 to ba applied to Fragment, enumerations, and eventing