Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Is schemaLocation just a hint in schema import?

From: "Antoli, Leo" <Leo.Antoli@-----.--->
To: xml-dev@-----.---.---, -------------@--.---
Date: 10/9/2006 5:48:00 PM
Hi all,

In the W3C Schema 1.0 spec you can find this note about imports:

"NOTE: The above is carefully worded so that multiple <import>ing of =
the
same schema document will not constitute a violation of clause 2 of =
Schema
Properties Correct (=A73.15.6), but applications are allowed, indeed
encouraged, to avoid <import>ing the same schema document more than =
once to
forestall the necessity of establishing identity component by =
component.
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,
regardless of the =B7actual value=B7 of schemaLocation, but such a =
strategy
risks missing useful information when new schemaLocations are offered."



Does it mean that you can't have 2 schemas defining different elements =
for
the same namespace and then import both from another schema? 
Should everything for a given schema be defined in just one schema =
file? If
you have a big schema definition for different functional areas, it =
might be
useful to split the schema in several files so you don't need to import
elements that you won't be using. 

It looks like Schema 1.1 is keeping this note.

Can anybody tell me the motivation for this note in the schema spec?

Thanks.






From mike@s... Mon Oct 09 16:04:00 2006
Received: from lisa.w3.org ([128


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