This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The stylesheet static-013 used for tests static-013, static-013a, and static-013b, contains the declaration <!-- Static param without select attr, but with an as-clause, implicitly mandatory--> <xsl:param name="static-param" static="yes" as="xs:integer" select="xs:date('2014-03-03')" /> In fact this does not come within the definition of "implicitly mandatory", which arises only where the parameter has an implicit default. It is the case covered by the Note: The effect of these rules is that specifying <xsl:param name="p" as="xs:date" select="2"/> is an error, but if the default value of the parameter is never used, then the processor has discretion whether or not to report the error. So all three tests should permit an error outcome, and the comments should be changed because the reference to being "implicitly mandatory" is incorrect.
I agree, I apparently misinterpreted the spec text here. - implicitly mandatory: only when there is no select attribute - explicitly mandatory: with required attribute set to yes - impl. defined: with non-castable select attribute, may raise error or not I will update the test to allow an error outcome.
I agree, I apparently misinterpreted the spec text here. - implicitly mandatory: only when there is no select attribute - explicitly mandatory: with required attribute set to yes - impl. defined: with non-castable select attribute, may raise error or not if externally supplied value is compatible, but the direct supplied value is not I have updated the test to allow an error outcome.
(sorry for the double submit, I got a "midair collision" error from BugZilla)