A potential client is using some terms that I have never come across.

What is or how do I - compile an xml schema?

What are the Saxonica schema tools? I know about Saxon 9A and B Processor

Regards.

If the question is specific to Saxon then it's probably best to ask on the saxon-help mailing list or forum.

The commercial edition of Saxon, Saxon-SA, includes an XML Schema processor. This allows you to validate instance documents against an XSD schema definition, and also to write schema-aware XSLT stylesheets and XQuery queries, which means that type information from the schema can be used to assist in compiling the query (giving the potential better diagnostics and better performance).

Like stylesheets and queries, schemas are processed once into an internal form so that they can be used repeatedly; this process is often called "compiling", though it does not actually generate executable code (in the case of a schema, it generates a finite state automaton which can be used to validate instance documents against the grammar defined in the schema.)

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

Saxonica is the name of the company that makes and supports the Saxon product.

Saxon SA ('SA', not 'A') is the schema aware version, Saxon B is the none-schema aware version of the product.

'Compiling' the stylesheet happens every time you run a stylesheet, but if you are going to be running the stylesheet again and again you can pre-compile it, using either the Saxon command line tool or Saxon for Java: http://www.saxonica.com/documentatio...compiling.html

__________________
/- Sam Judson : Wrox Technical Editor -/

this is what i have been told to do:

Use Saxonica Schema tools to export or import a compiled schema. The export format is an XML file, known as an SCM file (for schema component model).

So in this case I would use Saxon 9sA, but how do i get the SCM file as output?

Regards.

From the command line

java com.saxonica.Validate -xsd:schema.xsd -scmout:schema.scm

Will compile the schema and output the schema component model as an XML file to schema.scm

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

Okay so now i understand how to do step 1. The following is step 2:

Reverse engineer Saxon's SCM output and transforming it back into XSD documents, one document per target namespace, which would have all the named model groups and attribute groups expanded, all the types-derived-by-extension expanded, and so on. It would require two pieces of work: (a) capturing XSD annotations in the SCM model, and (b) writing the reverse SCM-to-XSD transformation (using XSLT). (there is a little difficulty in this that the xs:annotations we intend to use are now not exported by Saxon-A, but Michael has promised to fix it for us. Note this includes all children of xs:annotations like xs:documentation and xs:appInfo).


How do I do this?

Regards.

I think that what you are doing is sufficiently specialized it would be best to take this off-list. I've had some previous correspondence with Prasenjit Biswas about this project.

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

it would be best to take this off-list...

Where do i take it too?

Prasenjit Biswas has asked me if I can do it.

REgards

It's mike at saxonica dot com

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

I sent you an email, my address is jbampton at gmail dot com will send you another as I have a couple of questions