Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: Versioning of XML Schema and namespaces

From: "Michael Kay" <mike@--------.--->
To: "'Dan Vint'" <dvint@-----.--->, "'Fraser Crichton'" <fraser.crichton@---------------.--.-->, "'Eliot Kimber'" <ekimber@---------------.--->
Date: 5/12/2005 9:59:00 AM
> 
> 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.

You might make it easier for the recipient to do validation by including a
version in the namespace, but you are making it hideously difficult for the
recipient to process the incoming documents using namespace-aware tools such
as XSLT and XQuery - as anyone who has tried to write code that handles the
different flavours of RSS can tell you.

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



From ekimber@i... Thu May 12 14:37:07 2005


transparent
Print
Mail
Digg
delicious
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