7356 2009-08-17 21:25:59 +0000 [XSLT 2.0] Need clarification in the definition of circularity 2010-07-27 20:40:21 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 2.0 Recommendation All All CLOSED FIXED http://www.w3.org/TR/xslt20/#dt-circularity P2 major --- 1 zongaro mike sca.w3c public-qt-comments oldest_to_newest 26496 0 zongaro 2009-08-17 21:25:59 +0000 The definition of circularity in XSLT 2.0[1] is "A circularity is said to exist if a construct such as a global variable, an attribute set, or a key is defined in terms of itself. For example, if the expression or sequence constructor specifying the value of a global variable X references a global variable Y, then the value for Y must be computed before the value of X. A circularity exists if it is impossible to do this for all global variable definitions." The error reported for a circularity is "[ERR XTDE0640] In general, a circularity in a stylesheet is a non-recoverable dynamic error. However, as with all other dynamic errors, an implementation will signal the error only if it actually executes the instructions and expressions that participate in the circularity." It's not clear from the definition or the examples whether circularity is a static property of a variable or key, or it is something that is dynamic. Consider the following example: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:param name="p" as="xs:boolean"/> <xsl:variable name="x" select="if $p then $y+1 else 17"/> <xsl:variable name="y" select="if $p then 19 else $x"/> <xsl:template match="/"> <out><xsl:sequence select="$x, $y"/></out> </xsl:template> </xsl:stylesheet> In this example, there is a variable reference for x in the expression used to define y, and a variable reference for y in the expression used to define x. If these are "references" for the purposes of the definition of circularity, then x must be computed before y, and y before x, and so there is a circularity. However, if a reference for the purposes of circularity means a reference that is actually evaluated, then there is no circularity - if p has the value true, the definition of x has a reference to y, but the definition of y does not have a reference to x, so y must be evaluated before x if p is true; if p has the value false, the definition of y has a reference to x, but the definition of x does not have a reference to y, so x must be evaluated before y if p is false. [1] http://www.w3.org/TR/xslt20/#dt-circularity 26498 1 zongaro 2009-08-18 01:34:41 +0000 Sorry - I forgot to tie that back to error XTDE0640. With the static view of what is considered a circularity, the "if-then-else" expressions in the select attributes of the two variables, in their entirety, would be considered "instructions and expressions that participate in the circularity." With the dynamic view, the "instructions and expressions that participate in the circularity" would be only those that actually cause a variable to be referenced in evaluating that same variable. I think the dynamic view of circularity was intended, otherwise it makes it unnecessarily awkward to have the definition of a global variable use an xsl:apply-templates instruction, for instance. However, neither the definition nor the examples make that clear. 36887 2 mike 2010-07-15 08:45:23 +0000 The WG looked at this. We propose to make no change for 2.0: the spec clearly states that this is a dynamic error, triggered only if the expressions causing the circularity are actually evaluated. For 2.1/3.0 we decided to allow implementations to raise a static error in respect of a cycle of statically-determined references (e.g between functions, variables, named templates and keys) irrespective of whether they are actually evaluated. Needs drafting for 3.0. 36927 3 zongaro 2010-07-15 16:48:31 +0000 May I ask for a clarification on what will happen in XSLT 3.0? Would a processor be permitted to report a static error in the case of the potential circularity I described in comment #0? Or required to report one? 36931 4 mike 2010-07-15 18:48:50 +0000 My interpretation of the direction was that we would allow this to be reported as a static error, but not require it. Some circularities (those involving xsl:apply-templates) can only be detected dynamically, so this would still be allowed. 37109 5 sca.w3c 2010-07-27 20:39:30 +0000 See 15 July 2010 Minutes - resolution was: do nothing for 2.0; for next version, allow implementations to raise a static error in respect of a cycle of statically determined references without proving that they will inevitably be evaluated.