W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2005

RE: Error: missing category comment for xsl:param

From: Michael Kay <mhk@mhk.me.uk>
Date: Mon, 31 Oct 2005 08:30:36 -0000
To: "'R. Bijlsma'" <R.Bijlsma@xs4all.nl>, <xsl-editors@w3.org>
Message-ID: <E1EWV44-00035n-Ur@lisa.w3.org>

I suspect the omission was deliberate. The text you quote is immediately
followed by a statement that unlike xsl:variable, xsl:param cannot appear
anywhere in a "template", but only in certain positions.

In fact, if there is an error, it is in the sentence you quote. The content
model for xsl:template is given (in 5.3) as:

<!-- Category: top-level-element -->
<xsl:template
  match = pattern
  name = qname
  priority = number
  mode = qname>
  <!-- Content: (xsl:param*, template) -->
</xsl:template>

with the implication that the xsl:param element precedes the "template"
rather than being part of it.

However, the XSL Working Group is not currently spending any time on fixing
minor terminological inconsistencies in the XSLT 1.0 spec. If there were
serious differences between implementations in this area, then we might
consider issuing a clarification, but I'm not aware of any. Although XSLT
1.0 is quite likely to remain in use for some years, it's not clear that
implementors at this stage of the game would change their products in
response to new errata.

Michael Kay
(personal response)

 

> -----Original Message-----
> From: xsl-editors-request@w3.org 
> [mailto:xsl-editors-request@w3.org] On Behalf Of R. Bijlsma
> Sent: 30 October 2005 16:25
> To: xsl-editors@w3.org
> Subject: Error: missing category comment for xsl:param
> 
> 
>    Dear xsl editors,
> 
>    I found an error that is not mentiond in the errata in the 
> following
> document:
> 
> XSL Transformations (XSLT)
> Version 1.0
> W3C Recommendation 16 November 1999
> 
> 
>    The error is a missing Category: instruction comment in the 
>    following part:
> 
> --------------------------------------------------------------
> -------------------------------------
> <!-- Category: top-level-element -->
> <xsl:param
>   name = qname
>   select = expression>
>   <!-- Content: template -->
> </xsl:param>
> --------------------------------------------------------------
> -------------------------------------
> 
>    I conclude this from the following statement, which is in the same
> document:
> 
> 'As well as being allowed at the top-level, both xsl:variable and
> xsl:param are also allowed in templates.'
> 
> 
>    For xsl:variable, for which the same holds, according to 
> above statement,
>    the instruction comment is present, confirming that it 
> should be also
> present in the piece  about xsl:param.
> 
> --------------------------------------------------------------
> -------------------------------------
> <!-- Category: top-level-element -->
> <!-- Category: instruction -->
> <xsl:variable
>   name = qname
>   select = expression>
>   <!-- Content: template -->
> </xsl:variable>
> --------------------------------------------------------------
> -------------------------------------
> 
>    Best Regards,
>                            Rita Bijlsma
> 
> 
> 
> 
> 
> 
Received on Monday, 31 October 2005 08:30:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:58 GMT