[no subject]

    
    Given that you've already got version on LREs, I think 
    generalizing it so you can put the version attributes on 
    top-level elements such as xsl:template does make sense: 
    it's less work for the implementor to allow it everywhere 
    than to have complex rules about where it can appear, and 
    it's a lot more useful for users at the template level than 
    at the LRE level. We also have a number of statically 
    scoped attributes such as xpath-default-namespace and it 
    makes sense for them all to have the same rules.

I was arguing from a user view, not an implementation standpoint.

I'm trying to imagine a reader, with a stylesheet having n variant
version attributes on a large percentage of the content. 
Readability nil?

I don't see the value in perpetuating something that has such
small utility.

regards DaveP



-- 
DISCLAIMER:

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent
those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk

Current Thread