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

[Bug 28418] New: [XT30] error-0047a XTDE0057 has been removed from spec (possibly erroneously)

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Apr 2015 04:15:41 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28418-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28418

            Bug ID: 28418
           Summary: [XT30] error-0047a XTDE0057 has been removed from spec
                    (possibly erroneously)
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0 Test Suite
          Assignee: abel.online@xs4all.nl
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

This error was still there in the 2012 WD, but disappeared in the 2013 WD. In
the 2012 WD there were two identical errors with different descriptions:

   [ERR XTDE0047] It is a non-recoverable dynamic error if the invocation of 
   the stylesheet specifies both an initial mode and an initial template.

   [ERR XTDE0047] It is a non-recoverable dynamic error if the invocation of 
   the stylesheet specifies both an initial mode and an initial template.

I could not find anything in the mail archive or in Bugzilla, so I am not sure
whether this was done by accident or purposely. The only mail with a reasonable
comment about these dynamic errors is in
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2012Oct/0038.html

> Most of the ones that aren't catchable are "stylesheet invocation 
> errors" like not supplying a required parameter; in principle we could 
> invent another category for these, but I don't think it's worth the 
> hassle; just treat them as dynamic errors which can't be caught.

It could be argued that the error is redundant, because it is up to the API to
decide what happens here. However, the above comment implies that there was no
intend to remove the error.

>From the testing standpoint, I think that, as long as this error does not
exist, the test should not exist. I will tentatively mark it XSLT20 only, but
if the error comes back, we should change the test back as well.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 7 April 2015 04:15:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 April 2015 04:15:44 UTC