Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Are two schemas different content models?

From: "Michael Kay" <mike@--------.--->
To: <Daniel.Dui@---.--->, <xmlschema-dev@--.--->
Date: 1/23/2007 12:38:00 PM
If they are different schemas, then it's not a problem: you just need to be
careful about which schema is used on which occasion.
 
As soon as you try to combine them into one schema, it becomes a big
problem, because you can't have two global elements with the same name in
one schema.
 
Many tools (I guess XML Beans might well be an example) treat everything as
being one big schema, so they won't allow coexistence of the two
declarations.
 
Michael Kay
http://www.saxonica.com/


  _____  

From: xmlschema-dev-request@w... [mailto:xmlschema-dev-request@w...] On
Behalf Of Daniel.Dui@u...
Sent: 23 January 2007 12:11
To: xmlschema-dev@w...
Subject: Are two schemas different content models?



This topic probably has come up before, but here is my question.



I have two schemas (schema1 and schema2) and one namespace (ns). The
top-level elements in the schemas have the same name (topelem), but
different types (type1 and type2).



As far as I know the schema specs forbids having two elements with the same
name and different type in the same content model. To me, two schemas are
very different content models, but tools don't seem to think so.

For example XML Beans gives an error saying that if finds a duplicate global
element if I try to compile schema1 and schema2.

Can anyone shed some light?



Many thanks in advance

-daniel



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