[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

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

---

---

"Vun Kannon, David" wrote:
> 
>         Indeed, it would seem that this is a golden opportunity to put
> namespaces to good use. I'm fine with the addition of <eval>, as long as it
> is <ms:eval>, not <xsl:eval>. 

Clearly, Microsoft intends for these features to become part of standard
XSL. After all, changing the namespace doesn't solve the fundamental
problem: stylesheets that use the feature work exclusively with
Microsoft's processor. That's Double-Plus Ungood.

Many of Microsoft's extensions are poorly thought out:

<xsl:cdata>:

"The CDATA sections are useful for quoting tags and preventing them from
being interpreted. For this reason, the CDATA section is especially useful
for generating XSL tags in the output."

Hello! If you generate a CDATA section in the output, then the less-than
symbols inside of the section will NOT represent XSL tags anymore.

---

xsl:node-name Element:

 "Inserts the name of the current node as a text string."

Most nodes are not named. Elements are only named if they have an ID. The
"inventor" is confused about the terms "node" and "name." What they mean
is "element type name" (in SGML terminology) or "tagname" (in DOM
terminology). Certainly not node name!

 Paul Prescod  - http://itrc.uwaterloo.ca/~papresco

At today's pop doubling rates, in 100 years there will be 20 billion
people, more than enough to fill the earth. In 300 years, we will have
filled up 16 earth-sized planets (roughly, our solar system). In 2300
years we will have filled up 200 billion earth-sized planets (roughly,
our galaxy). Only one technology can save us: birth control.


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

---