W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1754] New: [FS] editorial: 7.2.1, 7.2.2, 7.2.10: normalizing calls to particular functions

From: <bugzilla@wiggum.w3.org>
Date: Tue, 19 Jul 2005 19:20:36 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1Duxds-00032a-T4@wiggum.w3.org>

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

           Summary: [FS] editorial: 7.2.1, 7.2.2, 7.2.10: normalizing calls
                    to particular functions
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


7.2.1 The fn:last context function
7.2.2 The fn:position context function
7.2.10 The fn:min, fn:max, fn:avg, and fn:sum functions

Norm
[[ fn:last()     ]]_Expr == ...
[[ fn:position() ]]_Expr == ...
[[ fn:sum()      ]]_Expr == ...
    These normalization rules can't be applied in the normal way. If "fn"
    is bound to a different namespace, you don't want the rule to fire.
    On the other hand, if the function is invoked via a different prefix
    or via the default function namespace, you *do* want the rule to fire.
    So you have to do some static analysis on the expression before you
    can decide whether or not to apply the normalization. I suppose you
    could make that fit into the processing model, but it might be easier
    to treat it much like any other built-in function, and provide STA and
    DEv.
Received on Tuesday, 19 July 2005 19:20:41 UTC

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