This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29978 - [XSLT30] Update error XTSE0120 and XTSE0130 for packages (xsl:package) and xsl:transform
Summary: [XSLT30] Update error XTSE0120 and XTSE0130 for packages (xsl:package) and xs...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-05 10:21 UTC by Abel Braaksma
Modified: 2016-11-16 17:31 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2016-11-05 10:21:42 UTC
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.
Comment 1 Abel Braaksma 2016-11-05 10:22:53 UTC
Or we could say "If a top-level element contains...", since top-level elements are defined as being one of xsl:package, xsl:transform, xsl:stylesheet, xsl:override.
Comment 2 Michael Kay 2016-11-10 23:58:17 UTC
I have applied the suggested changes, which are editorial in that they do not change the technical intent.
Comment 3 Sharon Adler 2016-11-16 17:31:18 UTC
SCA closed this bug.