W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2013

[Bug 23179] New: [XSLT 3.0] Motionless expression to get the value of a text node

From: <bugzilla@jessica.w3.org>
Date: Fri, 06 Sep 2013 20:58:40 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-23179-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23179

            Bug ID: 23179
           Summary: [XSLT 3.0] Motionless expression to get the value of a
                    text node
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

One would expect that when the context node is a text node (or comment or PI)
that there is some motionless way to get the string value (or typed value) of
the node. Naively, for example, one might expect that the pattern

match="text()[. = 'intro']"

is motionless. But it isn't, because our analysis has no way of taking into
account the fact that "." in this context refers to a text node. This requires
type analysis.

To make matters worse, there is no alternative way of getting the value of the
node in a way that is analysed as motionless. 

This also affects accumulators, because the new-value expressions in an
accumulator must be motionless, so they will often need to fire when text nodes
are encountered. There's no other way of accessing the content of a text node
as input to an accumulator.

I can't see any way forward on this other than introducing some limited type
inferencing.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 6 September 2013 20:58:42 UTC

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