Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Schema Query re import and defines

From: "Michael Kay" <mike@--------.--->
To: "'Kelso, Simon'" <skels@--------.--->, <xmlschema-dev@--.--->
Date: 5/12/2006 10:47:00 PM
Impossible to give a definitive answer without seeing a sample. And it might
be impossible even then, because the XML Schema spec give a lot of latitude
to implementations on this kind of thing.
 
Michael Kay
http://www.saxonica.com/


  _____  

From: xmlschema-dev-request@w... [mailto:xmlschema-dev-request@w...] On
Behalf Of Kelso, Simon
Sent: 10 May 2006 22:16
To: xmlschema-dev@w...
Subject: Schema Query re import and defines



Hi

Im not sure if I am mailing to the correct group or not.  We are having a
few problems with consistency with validation tools for XML schemas. We have
a main schema, extensions schema and an plug-in schema that combines the
two.  Descriptions on each are shown below:

Main Schema - contains data dictionary of all types, elements etc

Extensions Schema - contains business area specific types not contained in
the Main Schema - however these can be made up of types 'Imported' from the
main schema, therefore this schema imports from the Main Schema (note that
it uses IMPORT as it is a different namespace as the main schema.

The plug-in schema - which 'Redefines' types from the Main schema and
'Imports' from the Extensions Schema.

One validation tool validates our schema's ok, however one tool says that
the item being redefined is declared twice (therefore fails validation) -
this is because the plug-in schema is indirectly importing the definition
(From the Main Schema)  via the Extensions schema, while at the same time
doing a redefine from the Main Schema.  What tool is correct ? and is it
valid what we are doing ?

Thanks

Simon.




transparent
Print
Mail
Digg
delicious
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