Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Versioning of XML Schema and namespaces

From: Dan Vint <dvint@-----.--->
To: Fraser Crichton <fraser.crichton@---------------.--.-->, Eliot Kimber <ekimber@---------------.--->
Date: 5/11/2005 9:49:00 AM
At 04:32 PM 5/11/2005, Fraser Crichton wrote:
>So for example I create a messaging schema which incorporates components 
>from several published OASIS schemas, without versioning info in the 
>namespaces of the incorporated schemas it would be difficult for receivers 
>of my messages to work out what version of the public schemas I had 
>intended they validate against. Does that make sense?

That's my reason for using the namespace with a version.

I understand all the stated reasons for not doing this, but out of the box 
there is nothing else that will consistently and automatically trip up 
validation if I don't have the "right" file being used to validate my 
documents.

..dan
---------------------------------------------------------------------------
Danny Vint

Specializing in Panoramic Images of California and the West
http://www.dvint.com

voice: 510-522-4703


     



From John.Hockaday@g... Thu May 12 02:09:29 2005
Received: f


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