Ah, the info I wanted is in the SDK download. For XSLT support, here's what
I could glean from the XSLT docs and the What's New page.

XSLT elements documented as NOT implemented:
============================================
	xsl:transform 
	xsl:import 
	xsl:strip-space
	xsl:preserve-space 
	xsl:apply-imports 
	xsl:call-template 
	xsl:namespace-alias 
	xsl:number 

XSLT elements documented as PARTIALLY implemented:
==================================================

xsl:copy does not yet implement the use-attribute-sets attribute.

xsl:element does not yet implement the use-attribute-sets attribute.

xsl:output only implements method="xml" and version="1.0", and does not yet
implement the doctype-public, doctype-system, cdata-section-elements, and
media-type attributes.

The documentation for xsl:processing-instruction has for all its examples
xsl:pi instead of xsl:processing-instruction. Hopefully it supports the
unabbreviated element name.

xsl:sort only implements the select and order attributes, and does not yet
implement the lang, data-type, or case-order attributes.

xsl:stylesheet does not yet implement the extension-element-prefixes and
exclude-result-prefixes attributes.

xsl:template does not yet implement the name attribute.


XSLT elements documented as FULLY implemented:
==============================================
	xsl:apply-templates
	xsl:attribute
	xsl:choose
	xsl:comment
	xsl:copy-of
	xsl:for-each
	xsl:if
	xsl:include
	xsl:otherwise
	xsl:output
	xsl:param
	xsl:processing-instruction
	xsl:sort
	xsl:stylesheet
	xsl:template
	xsl:value-of
	xsl:variable
	xsl:with-param
	xsl:when

XSLT extension elements available:
==================================
	msxsl:script

Apparently the msxsl:script element can break a document's well-formedness
with respect to namespaces because the msxsl prefix itself does not have to
be declared, and the docs don't say what namespace to use if you wanted to
declare it.


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