Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


[xml-dev]Changing Namespaces Between Specification Versions (was:

From: "Paul Spencer" <xml-dev-list@--------.--.-->
To: "'Michael Kay'" <mike@--------.--->, "'Liam Quin'" <liam@--.--->,
Date: 4/21/2009 1:14:00 PM
Many people do change namespaces between versions. I prefer not to, but have
been persuaded to allow it in the past, where the argument has been that the
meaning of a name has changed, so the namespace should change as well.

Michael, what are your reasons for not doing this?

Does anyone else have views either way?

Paul Spencer 

-----Original Message-----
From: Michael Kay [mailto:mike@s...] 
Sent: 24 March 2009 21:07
To: 'Liam Quin'; 'xml-dev'
Subject: RE: [xml-dev] XIN: XML implicit namespace definitions


<snip>

This would actually remove one of the reasons why it's currently a really
bad idea to change namespaces between versions of a spec.


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



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