29980 2016-11-05 10:53:20 +0000 [XSLT30] XTSE0760 uses informal argumentation in its description 2016-11-11 10:11:39 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Candidate Recommendation PC Windows NT RESOLVED FIXED P2 editorial --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 128064 0 abel.braaksma 2016-11-05 10:53:20 +0000 Most errors are affirmative, formal and concise, without containing the (informal) argument that lead to introducing the error. Not so for XTSE0760: [ERR XTSE0760] Because arguments to a stylesheet function call must all be specified, the xsl:param elements within an xsl:function element must not specify a default value: this means they must be empty, and must not have a select attribute. I propose a different wording here: [ERR XTSE0760] It is an error for xsl:param elements that are children of xsl:function to have a select attribute or to be non-empty. Or, if we want to keep the gist of the hint of the original description: [ERR XTSE0760] It is an error to specify default values for function arguments, xsl:param elements that are children of xsl:function *must* have no select attribute and *must* be non-empty. 128148 1 mike 2016-11-11 10:11:39 +0000 I have made the existing text into an ordinary paragraph, and then added the formal error condition below: <p>Because arguments to a stylesheet function call <rfc2119>must</rfc2119> all be specified, the <elcode>xsl:param</elcode> elements within an <elcode>xsl:function</elcode> element <rfc2119>must not</rfc2119> specify a default value: this means they <rfc2119>must</rfc2119> be empty, and <rfc2119>must not</rfc2119> have a <code>select</code> attribute.</p> <p><error spec="XT" type="static" class="SE" code="0760"> <p>It is a static error if an <elcode>xsl:param</elcode> child of an <elcode>xsl:function</elcode> element has either a <code>select</code> attribute or non-empty content.</p> </error> </p> Editorial change made silently with no entry in the change log.