This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8196 - Frag: inheriting enveloping namespace prefixes is dangerous
Summary: Frag: inheriting enveloping namespace prefixes is dangerous
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Fragment (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-05 00:19 UTC by Gilbert Pilz
Modified: 2010-03-17 11:26 UTC (History)
1 user (show)

See Also:


Attachments

Description Gilbert Pilz 2009-11-05 00:19:17 UTC
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
Comment 2 Robert Freund 2010-01-28 23:47:39 UTC
Resolved with comment#1 to ba applied to Fragment, enumerations, and eventing