>An interesting bug has been opened due to a failing unit test with in the XSL Tooling project. It basically has to do with some interpretation of the XSLT 1.0 specification and parameters. What should be an error and what should be a warning when it comes to interpreting the specification.
This particular bug has to do with code like the following:
<xsl:template name="somename">
<xsl:param name="test">
<!-- Do some other stuff here -->
</xsl:template>
<xsl:template match="/">
<xsl:call-template name="somename"/>
</xsl:template>
Currently with the XSL Validation that is implemented in 0.5M6, the above will return an error on both the xsl:param and the xsl:call-template. The xsl:param will be reported as an error because it doesn’t contain a default value either via a select or wrapped int he xsl:param itself. The call-template will be marked as an error because it doesn’t specify the test parameter.
I think the above is a pretty common pattern, and probably should be treated as a warning instead of as an error. However, we’d like community feedback on this. Should the default setting for this be a warning or an error? Please provide comments in Bug 226582.
