Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] XPath "//", speed, and Saxon

From: "Andrew Welch" <andrew.j.welch@--------->
To:
Date: 11/3/2008 12:11:00 PM
> This example from my tutorial about testing XSLT [1]

> [1] http://www.menteithconsulting.com/wiki/XTech2007/MyStylesheetRunsBut#xsltproc


It would be cool to see the same effort/analysis [insert the right
word there] for how schema awareness does a lot of what the tests will
do, but with the added benefits that go with schema awareness.

For example, you could have input like:

<title>a title</title>
<body>the body</body>

...and you write a unit test to ensure the output contains a <title> -
or you could have a result schema with a mandatory <title> element,
the template which outputs the title could have an "as" attribute and
if you had an input schema you could be sure your XPaths were actually
selecting that title in the input.  All of which seems preferable to
the unit test.

A lot of time, effort and money goes into testing, but for XSLT, I
think that effort would be better spent on fully schema aware
transforms than unit testing.  What do you think?



-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent