xmlvm
Category:
xmlvm
The goal of XMLVM is to offer a flexible and extensible cross-compiler toolchain. Instead of cross-compiling on a source code level, XMLVM cross-compiles byte code instructions from Sun Microsystem's virtual machine and Microsoft's Common Language Runtime. The benefit of this approach is that byte code instructions are easier to cross-compile and the difficult parsing of a high-level programming language is left to a regular compiler. In XMLVM, byte code-based programs are represented as XML documents. This allows manipulation and translation of XMLVM-based programs using advanced XML technologies such as XSLT, XQuery, and XPath.

gotAPI
gotAPI/HTML - Instant search in HTML and other developer documentation
This is a good one-stop-shop with searchable API references for HTML, CSS, JS, PHP, MySQL, XSL and much much more.
WSDL viewer
Category:
WSDL viewer
WSDL has its constructive logic, but it is hard to read / understand the content by business professionals (mostly non-programmers). Here is a small tool to visualize the web-service in a more intuitive way.

XSL Flickr
Category:
XSL Flickr
XSL Flickr is a library of templates that allow XSLT (1.0 or 2.0) stylesheets to access the Flickr Services API.

Comparing XSLT and XQuery
Category:
Comparing XSLT and XQuery
This paper will attempt an objective side-by-side comparison of the two languages: not just from the point of view of technical features, but also looking at usability, vendor support, performance, portability, and other decision factors. Is it true, for example, that XQuery is better for data and XSLT is better for documents? Is one or the other language easier to learn depending on your computing background? As well as trying to answer these questions, the paper will also illustrate how the two languages can interoperate, so that each can be used for the parts of an application where it is most appropriate.
Comparing XSLT and XQuery
Category:
Comparing XSLT and XQuery
This paper will attempt an objective side-by-side comparison of the two languages: not just from the point of view of technical features, but also looking at usability, vendor support, performance, portability, and other decision factors. Is it true, for example, that XQuery is better for data and XSLT is better for documents? Is one or the other language easier to learn depending on your computing background? As well as trying to answer these questions, the paper will also illustrate how the two languages can interoperate, so that each can be used for the parts of an application where it is most appropriate.
ActiveState XSLT cookbook code samples ratings reviews
Category:
ActiveState XSLT cookbook code samples ratings reviews
Welcome to the XSLT Cookbook, a collaborative collection of techniques from the XSLT community. This living collection allows programmers to be more productive with XSLT.
Detecting version of Microsoft XSLT engine
Category:
Signs on the Sand: Detecting version of Microsoft XSLT engine from within XSLT
Sometimes it's useful to detect which XSLT engine your XSLT stylersheet is being executed by, e.g. to shortcut processing using an engine-specific extension function or to workaround a bug in particlular engine. Now that Microsoft alone ships 3 different XSLT engines - MSXML3/MSXML4/MSXML5/MSXML6, XslTransform and XslCompiledTransform, detecting XSLT engine from within XSLT stylesheet may be vital requirement. Here is how it can be done.
Google AJAXSLT
Category:
Google AJAXSLT
GOogle code project - XSLT implemented in JavaScript
xslt2Xforms - cross browser W3C Xforms processor
Category:
xslt2Xforms - cross browser W3C Xforms processor
xslt2Xforms is a cross browser "W3C Xforms" processor. This xsl stylesheet adds the W3C Xforms support in your web project using Xhtml, Javascript and Css.
The result code is cross-browser compliant (tested on Internet Explorer 6 and Mozilla 1.7). This stylesheet seems to work with all recent xslt engines.

This is vaporware for the time being but who knows...