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 ------- Additional Comments From [EMAIL PROTECTED] 2003-06-03 08:43 ------- This is a reply from the xerces-j team. I agree with their reading of the spec but we deal with schemas we have no control over here that do this. Currently we have to pre-process them (perl hack) to validate them. This is obviously sub-optimal. Does anyone else have views on this? Kevin did you adjust this bug because you also have the problem? bug #13193 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
