RE: [xsl] XSLT 2.0, using Schema-aware features

["Michael Kay" <mike@xxxxxxxxxxxx>]

I can see why you want this, but as David explained, it doesn't really work.
If you want to take advantage of schema-awareness at compile time, you have
to declare types in the stylesheet. At compile time the system will be able
to take advantage of its knowledge of the types, but this all relies on the
fact that at run-time, the instance document will conform to the schema. So
there's a dependency, in effect, on doing run-time schema validation of the
input document, and on checking the types expected at compile-time with
those actually delivered at run-time.

There's a different question one could ask, namely: would it be possible to
package up the product capabililities to distinguish the compile-time
product used by developers from the run-time product used to actually
execute transformations? The answer to that is yes: given a will to do it
and a commercial motivation, it's certainly technically feasible. However,
the pricing implications are far from clear. Which is more valuable, a
development kit used on a PC to develop and compile three or four
stylesheets a month, or a run-time engine executing on a web farm performing
ten thousand transformations an hour?

Michael Kay
http://www.saxonica.com/


> -----Original Message-----
> From: Bill Riegel [mailto:BRiegel@xxxxxxx] 
> Sent: 12 January 2007 16:16
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] XSLT 2.0, using Schema-aware features
> 
> I am desiring to use the Schema-aware features in Xslt 2.0 ( 
> i.e. with Saxon 8.73 ). 
> I would like the resultant xslt file to be able to run with 
> the non-schema aware version. 
> 
> Could someone indicate the best source of info describing 
> this workflow ? 
> 
> 
> Bill Riegel
> LandMark Graphics
> Phone: 713-839-3388
> Fax: 713-839-3051
> 
> 
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain 
> confidential and privileged information for the sole use of 
> the intended recipient.  Any review, use, distribution, or 
> disclosure by others is strictly prohibited.  If you are not 
> the intended recipient (or authorized to receive information 
> for the intended recipient), please contact the sender by 
> reply e-mail and delete all copies of this message.