Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: target namespace and namespaces

From: "Michael Kay" <mike@--------.--->
To: "'Dan Vint'" <dvint@-----.--->, <xmlschema-dev@--.--->
Date: 12/3/2004 4:24:00 PM
> Now I have 1 namespace = 2 different 
> schemas. A data stream that validates against schema 1 with 
> namespace=foo 
> will not validate against schema 2 with namespace=foo. A 
> substantial amount 
> may be legal because of the shared common information but the 
> upper wrapper 
> elements would immediately fail validation.
> 
> Is there anything that considers method 2 a legal design?
> 
> If it isn't illegal is it at least a really poor and 
> troublesome design?
> 

I think there's a real contradiction in the design philosophy here.

On the one hand, XML Schema recognizes that different people may want to
apply different validation criteria to the same document at different stages
of its lifecycle. The sender, for example, may apply stricter rules than the
recipient. So there can be more than one schema that's applicable to a given
document.

On the other hand, XML Schema suggests that knowing the target namespace is
enough information for a schema processor to go and find a schema, with the
schema location being just a hint. If there is more than one schema for a
namespace, then there is no way of telling the processor reliably which one
you want to use.

Let's hope that the WG grasps this particular nettle in its work on
versioning.

Michael Kay
http://www.saxonica.com/


From dvint@d... Fri Dec 03 16:37:33 2004
Received: from bart.w


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