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

[Bug 4174] Revalidation and non-globally defined elements

From: <bugzilla@wiggum.w3.org>
Date: Tue, 09 Jan 2007 18:47:24 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1H4M0K-0001kf-Em@wiggum.w3.org>

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

           Summary: Revalidation and non-globally defined elements
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: john.snelson@oracle.com
         QAContact: public-qt-comments@w3.org


In section 3.2.3 of the XQuery Update specification, revalidation is defined in
terms of the XQuery "validate" expression. I understand why the specification
does this, but it seems like this could be a problem since "validate" can only
validate an element which has a globally defined schema element for it. This
effectively means that with a revalidation mode of "strict", you could not
successfully modify any element that didn't have a globally defined schema
element for it.

Would there be any merit in storing the original type of the element when
upd:setToUntyped() is called, and using that somehow for validation?
Received on Tuesday, 9 January 2007 18:47:29 UTC

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