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 9256 - upd:replaceNode creates namespace bindings on parent($target), not $target
Summary: upd:replaceNode creates namespace bindings on parent($target), not $target
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-16 22:24 UTC by Josh Spiegel
Modified: 2011-01-07 03:06 UTC (History)
1 user (show)

See Also:

Attachments

Description Josh Spiegel 2010-03-16 22:24:51 UTC 
In section 3.2.1 upd:mergeUpdates, semantics bullet 2. f. ii. reads:

"upd:replaceNode creates one namespace binding on the $target element corresponding to the implied namespace binding of the name of each attribute node in $replacement."

I believe here $target should be replaced with parent($target).  When $replacement contains attributes, the $target node must also be an attribute.  (see section 2.4.3.1, bullets 3/4)

This issue also applies to step 1 in upd:applyUpdates.
Comment 1 Jonathan Robie 2010-04-06 16:44:11 UTC 
We believe this is correct - I will fix this in the specification.