This namespace URI is reserved for use with Crane's ResultXSLT^TM environment.

As of 2004-05-15, the term "ResultXSLT" was not found on any of Google, Yahoo, Ask.com or Alta Vista. We began using this term 2004-05-12 to refer to the technique of seeding a prototypical result instance with enough benign signals from which a W3C conformant XSLT 1.0 http://www.w3.org/TR/1999/REC-xslt-19991116 importable stylesheet fragment can be derived for use by a particular importing stylesheet.

We are claiming a trademark on "ResultXSLT" because we think it is the best terminology for this approach we've developed. We realize full text web searches are not legal measurements of anyone else's use of this terminology, but we are confident that had anyone else used this term it would have shown up by now.

1. Introduction

The term "Literate Programming" is from Donald E. Knuth http://www-cs-faculty.stanford.edu/~knuth/lp.html and refers to a methodology that combines a programming language with a documentation language, making programs more easily maintained.

The term "ResultXSLT" refers to our methodology that combines XSLT stylesheet fragment information with a candidate result tree. This was initially developed for our use of XSL-FO http://www.w3.org/TR/xsl because of the well-behaved nature of XSL-FO processors to ignore foreign constructs. The candidate result tree is used to determine the desired layout in an XSL-FO instance and then ResultXSLT signals are added to it in a benign (to XSL-FO) and thereby literate fashion. Our process then synthesizes an importable stylesheet fragment from the literate instance such that the stylesheet template rules produce the candidate result tree as if it did not have any literate content. An importing stylesheet then accommodates the input vocabulary.

This process can be used with any result vocabulary and is not restricted to only XSL-FO.

2. Download

This environment can be downloaded from the Free resources section of our web site.