Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] linkedin discussion of "can you sell an XSLT?"

From: "Michael Kay" <mike@--------.--->
To: <xsl-list@-----.------------.--->
Date: 6/5/2009 2:54:00 PM
> 
> I was going to say to make things "final" you could restrict 
> it to xsl:include only....  Or introduce a final attribute.
> 
> Personally I would be quite happy if it were limited to include only.
> 

You can override template rules (but not named templates or global
variables) with an xsl:include; you can also extend or modify keys, decimal
formats, namespace aliases, attribute sets, imported schemas, and various
other things. So limiting it to xsl:include doesn't really solve the
problem.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent