You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/10/10 20:52:17 UTC
DO NOT REPLY [Bug 13193] -
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=13193>.
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=13193
Multiple xsd:imports on the same namespace
sandygao@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From sandygao@ca.ibm.com 2002-10-10 18:52 -------
Please read the following section in the spec:
http://www.w3.org/TR/xmlschema-1/#layer2
Especially the last paragraph (starting with NOTE:), right above "4.3":
"Given that the schemaLocation [attribute] is only a hint, it is open to
applications to ignore all but the first <import> for a given namespace, ..."
So this is not a bug, because the spec allows it.
And I believe we *should* do it this way, because it encourages better Schema
authoring practice: always have a *root* schema document for a given namespace,
which includes or redefines other documents contributing to the same namespace.
Otherwise let's assume you have 10 schema documents that all refer to both
B.xsd and C.xsd. If you decide to add another D.xsd to namespaceD, you'll have
to update all 10 documents to import this new file. But by using B.xsd as the
root document for namespaceB, you only need to update this one file to include
D.xsd.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org