28418 2015-04-07 04:15:41 +0000 [XT30] error-0047a XTDE0057 has been removed from spec (possibly erroneously) 2015-10-29 09:50:36 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC Windows NT CLOSED FIXED P2 normal --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 119274 0 abel.braaksma 2015-04-07 04:15:41 +0000 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. 119275 1 abel.braaksma 2015-04-07 04:16:17 +0000 (this bug was originally reported by Vitaliy Yudenkov) 119298 2 abel.braaksma 2015-04-07 07:35:08 +0000 > I will tentatively mark it XSLT20 only, but if the error comes back, we > should change the test back as well. Currently fixed as described. Leaving the bug open though, because I think it warrants some discussion. 119545 3 abel.braaksma 2015-04-15 18:12:10 +0000 Moving the bug from XT30 to XSLT 30, so it can be discussed by the WG. 119800 4 mike 2015-04-23 08:09:02 +0000 I think the error condition disappeared as part of the reorganization of the "stylesheet invocation" section. I think it was right to remove it. It's an API error. The API might be designed so that there is no way of triggering this error, e.g public void setInitialModeOrTemplate(QName name, boolean isMode) or in the case of invocation from an XML-based test suite, the schema for the test suite metadata might prevent both an initial mode and an initial template being present (in which case the error you get is not XTDE0047, but a validation error on validating the test suite). I think the test case should be dropped. Chances are, any product that passes this test probably catches this error in the test driver, not in the product under test. 119828 5 mike 2015-04-23 17:03:14 +0000 Agreed to retain the status quo in the spec and drop the test case.