This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Microsoft XSL and Conformance
The XSLT 1.0 Spec is also careful to provide the
necessary mechanisms to built robust, portable
XSLT stylesheets, even in the face of cool extensions.
The <xsl:fallback> and element-available('qname') and
function-available('qname') let you have good, proactive
control as to what should happen if an extension on
which you depend is not available.
_________________________________________________________
Steve Muench, Consulting Product Manager & XML Evangelist
Business Components for Java Development Team
----- Original Message -----
From: "Jonathan Borden" <jborden@mediaone.net>
To: <xsl-list@mulberrytech.com>
Sent: Thursday, March 16, 2000 12:36 PM
Subject: Re: Microsoft XSL and Conformance
| Steven Livingstone wrote:
|
| >
| > Anyway, from what I understand, most, if not all, products mentioned on
| this
| > list have their own extensions and are any 100% fully compliant?
| >
| >
|
| The XSLT extension mechanism is outlined in the spec and an example of
| one was provided with James Clark's 11/99 XT implementation ... several of
| the implementations have a few nits here and there, what we are talking
| about is substantial compliance (modulo bugs) with full compliance as bugs
| are reported and fixed.
|
| In summary, XSLT extensions, provided through the extension mechanism,
| do not prevent compliance with http://www.w3.org/tr/xslt .
|
| Jonathan Borden
|
|
|
| XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list