W3C home > Mailing lists > Public > xsl-editors@w3.org > January to March 2002

RE: XSLT 2.0 WD feedback: Issue (evaluate-function)

From: Kay, Michael <Michael.Kay@softwareag.com>
Date: Wed, 2 Jan 2002 16:53:10 +0100
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210622B8A3@softwareag.com>
To: "'Matt G.'" <matt_g_@hotmail.com>, xsl-editors@w3.org
Thanks (on behalf of the WG) for this feedback, which we will consider
carefully: though I can't promise when, or with what result. 

I'd be interested to know what you think of the proposed facilities in
Appendix F as a way of getting entities and entity references into the
serialized result document. They have been put forward somewhat tentatively,
so it would be useful to have feedback as to whether or not they meet the

Mike Kay

> -----Original Message-----
> From: Matt G. [mailto:matt_g_@hotmail.com]
> Sent: 02 January 2002 07:08
> To: xsl-editors@w3.org
> Subject: XSLT 2.0 WD feedback: Issue (evaluate-function)
> This message pertains to the document: XSL Transformations 
> (XSLT) Version 
> 2.0 W3C Working Draft 20 December 2001
> On the topic of "evaluation-function" issue, I'd like to 
> suggest that the 
> value of this feature will help to encourage the adoption of 
> XPath, in many 
> XML vocabularies.  While it may be adopted for modeling 
> relationships within 
> a document (that's the use for which I'd like to have been 
> able to employ 
> it), I question the characterization by some that this is an 
> abuse.  To me, 
> it seems a far more reasonable approach than inventing one's 
> own syntax for 
> tersely modeling such relationships (as I had to do).  
> Furthermore, with 
> regard to the implications on static optimization, it seems 
> to me that 
> stylesheet processors would still have the opportunity to optimize 
> stylesheets that don't use this function.  The decision would 
> then be left 
> up to the user as to whether maximizing runtime performance 
> or minimization 
> of development time is more important, and on a case-by-case basis.
> Also, I have one issue that I'm not sure has been addressed 
> (my apologies 
> for not having read the WD fully, yet--I just skimmed through 
> the sections 
> that looked like they might address this): creating parsed entity 
> definitions (in the output document's internal subset) & 
> references (in the 
> result tree, only) seems like it could make XSLT much more 
> suitable for use 
> as a tool for translating between vocabularies used as 
> authoring formats.  
> Also, along those lines, what about a mechanism (either 
> style-sheet global 
> or maybe as an inherited property of templates) for 
> overriding the output 
> format for specified  character entities?
> Thanks for considering my feedback & congratulations on 
> getting the WD 
> released!
> Matthew Gruenke
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos: 
> http://photos.msn.com/support/worldwide.aspx
Received on Wednesday, 2 January 2002 10:53:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:22 UTC