Altova Mailing List Archives
>xml-dev Archive Home
>Recent entries
>Thread Prev - Best practices: Namespaces, versions and RDDL
[Thread Next]
Re: Best practices: Namespaces, versions and RDDL
To: vdv@--------.---
Date: 3/22/2001 11:26:00 PM
> Does it make sense ? yes, but I think it's a much better policy not to change namespace URI on version changes. For example early XSL(T) drafts had a similar policy to the one you describe of adding to a base URI, but fortunately they changed that before REC and now have a fixed URI and a separate version attribute for version changes. To a namespace aware processor, if you change the namespace URI you have changed the name of _every_ construct in the language. In most contexts, two languages which do not have a single name in common would not be considered versions of each other, but rather two separate languages. Thus I think the rule should be: If the new system is close enough to the old that you just want to increment a version number rather than giving it a different name, use the same namespace. So in th eyear 2021, MathML version 77 should still use http://www.w3.org/1998/Math/MathML, but if then we want to make a clean break and have NewMathML version 1 then at that point switch to http://www.w3.org/2022/Math/NewMathML David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre. For further information visit http://www.star.net.uk/stats.asp
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.

