W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2016

[Bug 29675] New: [XSLT30] Determining the static context item type when focus-setting container is a declaration

From: <bugzilla@jessica.w3.org>
Date: Fri, 27 May 2016 20:45:23 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29675-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29675

            Bug ID: 29675
           Summary: [XSLT30] Determining the static context item type when
                    focus-setting container is a declaration
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

We currently write, in section 19.2 Determining the Context Item Type:

5. If the focus-setting container is any other declaration, for example a
global variable declaration, the context item type is U{*}.

However, the present rules on streamability for global variables assume the
context item type from xsl:global-context-item.

Even though we may be dropping global variables from streaming analysis (see
bug 29670 comment #3), I think this rule should be in relation to
xsl:global-context-item (regardless whether streamability is applicable).

I propose therefore:

5. If the focus-setting container is a global xsl:variable or xsl:param
declaration, the context item type is the type from the type attribute of
xsl:global-context-item, U{} if the use attribute is "absent" or U{*} if that
declaration is absent.
6. If the focus-setting container is any other declaration, for example xsl:key
or xsl:accumulator, the context item type is U{*}.
7. Otherwise [...]

(rule (6) is there because they apply to the match selection, not the GCI)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 27 May 2016 20:45:25 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 May 2016 20:45:25 UTC