W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2004

RE: [XSLT2.0] Error XT1560

From: Michael Kay <mhk@mhk.me.uk>
Date: Wed, 13 Oct 2004 18:03:20 +0100
To: "'Colin Paul Adams'" <colin@colina.demon.co.uk>, <public-qt-comments@w3.org>
Message-ID: <E1CHmXi-0001y6-2u@frink.w3.org>

We try to keep the rules for different kinds of declaration consistent with
each other. The general rule we have adopted for most declarations is along
the lines used for global variables: it's an error to have two of the same
name at the same import precedence, unless there is one of higher import
precedence, and this error applies whether or not the object is actually
referenced.

Arguments based on a feature being awkward to implement tend to carry rather
little weight with the Working Group.

I discussed the request with the WG chair and we decided that there was no
justification to log this as a formal issue. (We have discretion in
responding to comments submitted after the last call date.)

Michael Kay


> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of Colin 
> Paul Adams
> Sent: 13 October 2004 12:30
> To: public-qt-comments@w3.org
> Subject: [XSLT2.0] Error XT1560
> 
> 
> I would like to request that whether or not to report this error, be
> made implementation dependent in one case.
> 
> Namely, when the clash occurs for a named output definition that is
> not referenced by an xsl:result-document.
> As far as I can tell, this must be harmless, and checking for the
> error would be awkward for my implementation.
> -- 
> Colin Paul Adams
> Preston Lancashire
> 
> 
Received on Wednesday, 13 October 2004 17:04:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:22 UTC