To get the real benefit of schema-aware XSLT processing, you
really need to start defining match patterns in terms of
schema-declared elements and types, for example
<xsl:template
match="schema-element(invoice)/delivery-address/postcode">
[snip]
It's a fair investment to get started (time learning the
ropes, and time establishing schemas for all your documents)
but once you're over the curve, it makes the debugging cycle
a completely different experience - instead of wrong or
absent output, you get accustomed to expecting early error
messages, often at compile time.
The problem here is that template match="schema-element(abc)" gets
rejected by the non-SA processor. The leads onto some questions:
-Does the SA processor require a source schema for every transform (when
using schema-element() etc)?
-Is it possible to store the validated source (the PSVI?) and supply
that for subsequent transforms?
The point to my questions is that I wouldn't want to validate the same
source document every time I wanted to transform it. If I could
validate it once and then use that per request that would solve that
issue.
Other than the 2.0 spec, are there any good resources out there for SA
processing?
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--