https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2019-10-02T22:44:33ZSaxonica Developer CommunitySaxon - Bug #4331: XTSE3051 is not raisedhttps://saxonica.plan.io/issues/4331?journal_id=142712019-10-02T22:44:33ZMichael Kaymike@saxonica.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li><li><strong>Applies to branch</strong> <i>trunk</i> added</li></ul><p>Yes, this looks like a bug. I've made it into test accept-916 in the W3C test suite.</p> Saxon - Bug #4331: XTSE3051 is not raisedhttps://saxonica.plan.io/issues/4331?journal_id=142722019-10-02T23:00:31ZMichael Kaymike@saxonica.com
<ul></ul><p>The problem is that at the stage where we read the list of names in `xsl:accept/@names, we only know the name of the function and not its arity.</p>
<p>In fact the spec doesn't say very much about the case where <code>xsl:accept/@names</code> or <code>xsl:expose/@names</code> uses a NameTest with no arity to refer to a function (or a set of functions with the same name and different arity). It doesn't seem to be prohibited, but at the same time the spec has little to say about what it means. We can certainly interpret it as meaning "all functions with that name", and I don't think anything breaks if we do so, but it's not clear that this is what the spec intended.</p> Saxon - Bug #4331: XTSE3051 is not raisedhttps://saxonica.plan.io/issues/4331?journal_id=142832019-10-03T09:58:29ZMichael Kaymike@saxonica.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>Fix Committed on Branch</strong> <i>9.9, trunk</i> added</li></ul><p>Added a check for the case where xsl:accept accepts all functions with a given name (regardless of arity) and one of those functions is specified in xsl:override.</p> Saxon - Bug #4331: XTSE3051 is not raisedhttps://saxonica.plan.io/issues/4331?journal_id=144402019-10-24T17:25:07ZMichael Kaymike@saxonica.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>In Progress</i></li></ul><p>Reopened, because I've noticed the proposed XSLT 3.0 Erratum XT30.E36, which proposes to interpret the spec as follows:</p>
<p>In 3.5.3.1 Visibility of Components (tenth paragraph):</p>
<p>Replace the text:</p>
<p>The value may be a NamedFunctionRef only in the case of stylesheet functions, and distinguishes functions with the same name and different arity.</p>
<p>With:</p>
<p>The value may be a NamedFunctionRef only in the case of stylesheet functions, and distinguishes functions with the same name and different arity. A NameTestXP30 on its own (that is, with no arity) cannot be used to identify a function.</p> Saxon - Bug #4331: XTSE3051 is not raisedhttps://saxonica.plan.io/issues/4331?journal_id=148912020-02-06T15:49:43ZMichael Kaymike@saxonica.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>I have changed the code and the tests so <code>xsl:accept</code> and <code>xsl:expose</code> now:</p>
<ul>
<li>
<p>Don't allow an arity on the name of a component other than a function (clearly an error in the spec, which we weren't catching)</p>
</li>
<li>
<p>Require an arity on the name of a function (not clearly stated in the spec, resolution proposed in draft erratum E36)</p>
</li>
</ul> Saxon - Bug #4331: XTSE3051 is not raisedhttps://saxonica.plan.io/issues/4331?journal_id=150002020-03-05T10:09:41ZO'Neil Delprattoneil@saxonica.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Fixed in Maintenance Release</strong> <i>9.9.1.7</i> added</li></ul><p>Patch applied in the 9.9.1.7 maintenance release.</p>