RE: [xsl] ANNOUNCE: Petition to withdraw xsl:script from XSLT 1.1

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

Ok.  Looking at this and Steve's replies, it looks 
like they did the best thing.  Are the binding 
annexes informative or normative?

I think MSXML already enables xsl:script.  

****************************************************

MOTHER OF PEARL!!! INTEL HAS NO RIGHT TO 
THE CLIPPER PATENTS!!!!  IT'S RAINING MONEY HERE!!!!!

****************************************************

Len Bullard
Intergraph Public Safety
clbullar@ingr.com
http://www.mp3.com/LenBullard

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: Evan Lenz [mailto:elenz@xyzfind.com]

Len Bullard wrote:
> Why did they insist on embedding?

I presume because certain implementors (Microsoft and maybe some others that
I'm not aware of) already provided embedding functionality. This was, at
least eventually, implemented in full conformance to the existing XSLT 1.0
extension mechanisms. In XSLT 1.1, the Microsoft XSLT processor will be able
to use xsl:script instead of just msxsl:script. That means that other
processors may use the same namespace (the XSLT namespace) to implement the
same functionality, making embedded scripting slightly less non-portable.

While I also have qualms about embedding scripting from a software design
standpoint, arguments about the relative merit of doing so will not persuade
the W3C to remove xsl:script, because they will just point to the
misunderstanding of the issue. "We're not providing new
functionality"--which is true. Many people caught up in this debate don't
recognize this.

Evan