29094 2015-08-28 08:32:30 +0000 [xslt 3.0] conflict between xsl:accept and xsl:override 2015-10-29 12:42:31 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 1 mike mike abel.braaksma public-qt-comments oldest_to_newest 122832 0 mike 2015-08-28 08:32:30 +0000 Consider: <xsl:use-package name="Q"> <xsl:accept component="variable" name="v" visibility="hidden"/> <xsl:override> <xsl:variable name="v" select="93.7"/> </xsl:override> </xsl:use-package> The current spec suggests that the xsl:override wins (xsl:accept says "In the absence of a matching xsl:override element ...) and essentially assigns no semantics to the xsl:accept declaration in this case. I think it would be consistent with the decision on bug #26781 to raise an error in the case where xsl:accept names a component explicitly (not by wildcard) and there is an xsl:override for the same component. 123363 1 abel.braaksma 2015-09-30 02:19:19 +0000 An alternative thought is: the user wants to hide this component from his current stylesheet (principal package), but override the value for the used package. Which I think is a valid thought in and of itself. 123601 2 mike 2015-10-07 21:06:36 +0000 Comment #1 suggests a possible interpretation of my example, but I think if we wanted to provide that particular capability it would make more sense to do so by allowing the declaration within xsl:override to specify visibility="hidden". But that's new functionality that I think we can live without. I therefore propose the rule: It is a static error if a token in the names attribute of an xsl:accept element, other than a wildcard, matches the symbolic name of a component declared within an xsl:override element that is a sibling of the xsl:accept element. 123630 3 mike 2015-10-09 11:32:57 +0000 The WG accepted the proposed change. New text added as follows: <item diff="add" at="S-bug29094"> <p>If a component is explicitly accepted from a used package (by name, rather than by a matching wildcard, and if the same component is the subject of an <elcode>xsl:override</elcode> declaration, then a static error occurs (see below). There is no conflict, however, if a component declared within <elcode>xsl:override</elcode> also matches a wildcard in an <elcode>xsl:accept</elcode> element.</p> <p> <error spec="XT" type="static" class="SE" code="3051"> <p>It is a <termref def="dt-static-error">static error</termref> if a token in the <code>names</code> attribute of <elcode>xsl:accept</elcode>, other than a wildcard, matches the symbolic name of a component declared within an <elcode>xsl:override</elcode> child of the same <elcode>xsl:use-package</elcode> element.</p> </error> </p> </item>