-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15.6.2018 8:54, David Carlisle d(_dot_)p(_dot_)carlisle(_at_)gmail(_dot_)com
wrote:
This was discussed at great length when namespaces were
introduced. Although some vocabularies chose to change the
namespace at version changes it's a really bad idea. If you change
the namespace then you change the name of every construct in the
language, that isn't a new version it is a new, incompatible,
language.
And just to extend this little bit -- fact that namespace change
creates new incompatible language is often used for versioning. As
long as new versions of vocabulary are backward compatible and
semantics of individual element is not changed then namespace is not
changed. But when breaking change has to be included into vocabulary
then namespace should be changed to make sure that old tools will
break on a new "incompatible" content. This is quite common pattern
especially in data-exchange vocabularies. But XSLT
versioning/namespace policy is based on a similar idea.
- --
- ------------------------------------------------------------------
Jirka Kosek e-mail: jirka(_at_)kosek(_dot_)cz http://xmlguru.cz
- ------------------------------------------------------------------
Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
- ------------------------------------------------------------------
Bringing you XML Prague conference http://xmlprague.cz
- ------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iEYEARECAAYFAlsnd3MACgkQzwmSw7n0dR4j/gCgwDrCTxfhwkhUXbJUIUZWHtZh
21IAoI+UwHUniGErL3sqxyH3+VsFQWyS
=P8wJ
-----END PGP SIGNATURE-----
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--