Re: [xml-dev] The purpose of a namespace URI is ...

[Fraser Goffin <goffinf@gmail.com>]

David you may very well be right, but on a practical level, it is more
likely that due to a change in pure *syntax*, for example wanting an
existing complexType to have a new mandatory element, a change of the
namespace may be necessary to clearly signal that break. I'm not
saying that's right, I'm just saying that whilst a new namespace may
at one level create a new language, if it substantially inherits it's
semantics from the previous version but because of a practical issue
can't really maintain the same namespace ....

That's why I said earlier that a data model can be 'damaged' because
of the 'leakage' of shortcomings of the language used to express it.
Whilst we could philosophically satisfy ourselves that if implementers
followed a particular approach to processing messages using that
language the problem wouldn't exist, again, reality would suggest that
many (perhaps most) don't do that and instead rely on features of 'off
the shelf' processors to do most of the heavy lifting but still
exhibit the processing flaw (e.g. strict XSD validation rather than
'selective/elective').

It's a conumdrum.

Fraser.


On 01/12/2012, David Carlisle <davidc@nag.co.uk> wrote:
> On 30/11/2012 20:22, Fraser Goffin wrote:
>> But isn't it usually the case that you would only change the
>> namespace for a MAJOR version change, and it is this explicit and
>> deliberate breaking change that you are signalling by doing so (ie. a
>> significant change of semantics and sometimes syntax).
>
> Well stronger than that, If you change the namespace you have changed
> the name of every token in the language so it's not a new version it's a
> new language. Sometimes that's what you want to do SGML->XML dsssl to
> xslt etc but if the language is plausibly a new _version_ of an existing
> language it ought to have the same namespace (a policy that isn't always
> followed:-)
>
> David
>
>
>