W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2009

[Bug 6483] New: [UPD] upd:replaceNode() and upd:setToUntyped()

From: <bugzilla@wiggum.w3.org>
Date: Wed, 28 Jan 2009 12:39:39 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-6483-523@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6483

           Summary: [UPD] upd:replaceNode() and upd:setToUntyped()
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 28 January 2009 12:39:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:38 UTC