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 6483 - [UPD] upd:replaceNode() and upd:setToUntyped()
Summary: [UPD] upd:replaceNode() and upd:setToUntyped()
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-28 12:39 UTC by Michael Kay
Modified: 2011-01-07 11:48 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2009-01-28 12:39:39 UTC 
In 3.1.8 upd:replaceNode(), it is stated (rule 1b):

If the type-name property of parent($target) is xs:untyped, then upd:setToUntyped() is invoked on each element node in $replacement.

It's not clear why this isn't done also for attributes. In 3.1.6 upd:insertAttributes, rule 1b, it is done for attributes, and I can't see a significant difference between replace and insert here.
Comment 1 Michael Kay 2009-02-24 17:54:54 UTC 
The WG agreed this was a simple omission and the spec will be fixed.