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

[Bug 27839] New: [xslt 3.0]unparsed-entity-uri (&public-id) dependency on context node

From: <bugzilla@jessica.w3.org>
Date: Thu, 15 Jan 2015 12:06:16 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-27839-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 27839
           Summary: [xslt 3.0]unparsed-entity-uri (&public-id) dependency
                    on context node
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          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

In the vast majority of cases where we have constructs that depend on the
context item, we have introduced a variant of the construct that allows the
relevant item to be supplied explicitly as an operand. Examples are xsl:copy,
xsl:number, fn:id, fn:key. This allows the construct to be used without the
artifice of having to set the context item using something like xsl:for-each;
it is also useful internally within an implementation because it allows the
form of the construct that uses the context implicitly to be rewritten to the
form where the dependency is explicit, for example id('x') can be rewritten as
id('x', /).

The unparsed-entity-uri() and unparsed-entity-public-id() functions have not
had this treatment: they can only be applied to the document containing the
context item.

I would therefore like to propose introducing a two-argument form of these
functions taking a node as the second argument, defaulting to the context node
if the argument is not supplied.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 15 January 2015 12:06:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 15 January 2015 12:06:17 UTC