You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2002/10/02 10:49:21 UTC
DO NOT REPLY [Bug 13191] New: -
Multiple xsd:imports on the same namespace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13191>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13191
Multiple xsd:imports on the same namespace
Summary: Multiple xsd:imports on the same namespace
Product: Xerces-C++
Version: Nightly build (please specify the date)
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Validating Parser (Schema) (Xerces 1.5 or up only)
AssignedTo: xerces-c-dev@xml.apache.org
ReportedBy: dws@decisionsoft.co.uk
I mentioned this on the mailing list and recieve a postitive response (this is
mainly a paste of that mail).
We have seen some schemas where the definition of a namespace is split
between several schemas, each defining a subset of the namespace. An
example of what I mean is attached:
schemaA.xsd defines namespaceA, and imports both schemaB.xsd and
schemaC.xsd into namespaceB. It then defines an element of each of the
types defined in schemas B and C, in namespaceB.
It appears that xerces ignores the second import, so the type defined in
schemaC.xsd is not available when it is used to define the element.
XMLspy, however accepts this use, and validates the instance fine. Also,
the IBM XML Schema quality checker[1], claims there is no error in
schemaA.xsd.
As schemas and namespaces get larger, and more complicated, I expect
this sort of separation to become more and more widespread.
I tested this on the CVS version as of 26/9/2002. Xerces J also suffers from the
same problem.
David
[1] http://www.alphaworks.ibm.com/tech/xmlsqc
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org