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

[Bug 29927] New: [XSLT30] (probably editorial) xsl:evaluate as an optional feature

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Oct 2016 03:50:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29927-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29927

            Bug ID: 29927
           Summary: [XSLT30] (probably editorial) xsl:evaluate as an
                    optional feature
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: editorial
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The text in section 10.4.4 xsl:evaluate as an optional feature mentions that
xsl:evaluate can be either statically or dynamically disabled.

I have no clue how it could ever be dynamically disabled, but I guess that rule
is there for a reason.

I raise this bug, however, because we don't specify the "should" in the final
paragraph as implementation-defined. I think it should be
(implementation-dependent doesn't seem to make sense here).

I propose to add the line:

"If a processor supports the dynamic evaluation features, it is
implementation-defined how a processor allows users to turn off dynamic
evaluation and it is implementation-defined whether this this is static or
dynamic."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 11 October 2016 03:50:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC