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

[Bug 29978] New: [XSLT30] Update error XTSE0120 and XTSE0130 for packages (xsl:package) and xsl:transform

From: <bugzilla@jessica.w3.org>
Date: Sat, 05 Nov 2016 10:21:42 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29978-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29978

            Bug ID: 29978
           Summary: [XSLT30] Update error XTSE0120 and XTSE0130 for
                    packages (xsl:package) and xsl:transform
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Currently we have:

[ERR XTSE0120] An xsl:stylesheet element must not have any text node children.

and:

[ERR XTSE0130] It is a static error if the xsl:stylesheet element has a child
element whose name has a null namespace URI.


I propose to update these errors:

[ERR XTSE0120] An xsl:stylesheet, xsl:transform or xsl:package element must not
have any text node children.

and:

[ERR XTSE0130] It is a static error if an xsl:stylesheet, xsl:transform or
xsl:package element has a child element whose name has a null namespace URI.

We could consider adding to XTSE0130/XTSE0120 other instructions/declarations
that have a defined body, i.e. that do not allow a sequence constructor (like
xsl:fork, xsl:choose etc). In fact, we could generalize it perhaps.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 5 November 2016 10:21:49 UTC

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