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

[Bug 5338] [UPD] Revalidation mode: which static context?

From: <bugzilla@wiggum.w3.org>
Date: Wed, 02 Jan 2008 18:40:56 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1JA8WO-0007N7-Sx@wiggum.w3.org>

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

           Summary: [UPD] Revalidation mode: which static context?
           Product: XPath / XQuery / XSLFO / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            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


The specification for upd:revalidate() describes the effect in terms of the
revalidation mode "in the static context". But which static context?

For a query that does updates at the top level, it should presumably be the
revalidation mode defined in the main query module. For updates done within a
transform (copy-modify) expression, it should presumably be the revalidation
mode defined in the module containing the transform expression. 

(The description of revalidation mode says its scope is global. But it doesn't
say what this means. Does it mean it's an error to define different values in
different modules? If so, what error?)
Received on Wednesday, 2 January 2008 18:41:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:49 GMT