Re: Microsoft extensions to XSL (was RE: how to call Javascript function in .xsl file) function in .xsl file)

["Denis Hennessy" <denis@xxxxxxxx>]

>[Denis Hennessy]
>> For my work, the dropping of script support in the current draft has
>> been a major pain.
>
>For your work, you probably shouldn't be using a draft-in-progress.

My work involves publishing XML documents on the web. Since I can't find
commercial software to help with this, I have to develop the transformation
software in-house. I'd prefer to base that on an emerging spec rather than
roll my own. It also gives me useful insights into the suitability of
evolving XSL draft for this process.

>If they are using the namespace declaration
>
><xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl";>
>
>which their examples do, then all <xsl:*> elements are from a
>namespace controlled by the W3C.  There is no <eval> element in that
>namespace, and their documentation of such, explicitly from that
>namespace, is questionable at best and criminally fraudulent at worst.

I can't speak for Microsoft but my guess is that their technology preview is
guessing at how scripting will be added to the draft. My further guess is
that if it's not added to the draft, it will be renamed to a <ms:eval>-style
extension.

>The standard doesn't provide it because there is no standard.  There
>is a draft, explicitly in progress and not done yet.  This
>functionality is intended, but not this way; investing effort in
>ECMAScript-based solutions will only waste your time.

The draft has been published for public comment which is what I'm doing. If
you already know how you're planning on adding this type of functionality,
then it would be helpful to hear your thoughts on this.

>-Chris
> absolutely not speaking in any way for the XSL WG

I wish someone would!

/dh



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list