- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Fri, 13 Sep 2002 14:35:33 -0400
- To: www-tag@w3.org
/ "Dare Obasanjo" <dareo@microsoft.com> was heard to say:
|> -----Original Message-----
|> From: Norman Walsh [mailto:Norman.Walsh@Sun.COM]
|> Sent: Friday, September 13, 2002 11:20 AM
|> To: www-tag@w3.org
|>
|> / "Dare Obasanjo" <dareo@microsoft.com> was heard to say:
|> | Does this mean that the namespace of a given XML vocabulary should
|> | never change?
|>
|> But I think one could go a step further in answer to your question.
|>
|> From the point of view of applications that examine the
|> namespace name and local name of an element to determine the
|> vocabulary to which it belongs, it isn't simply a "should
|> never", it's a "can never".
|>
|> To those applications, if you change the namespace name, you
|> haven't changed the namespace of the vocabulary, you've *changed the
|> vocabulary* by definition.
|>
|> That may be a lot more painful than you'd like for a
|> transition from V1.0 to V1.1.
|
| Really? SOAP doesn't seem to work this way
I didn't say that was the only way to determine the vocabulary to
which an element belongs. Certainly other strategies exist and SOAP
must have one.
Be seeing you,
norm
--
Norman.Walsh@Sun.COM | Wisdom is only a comparative quality, it will
XML Standards Architect | not bear a single definition.--Marquess of
Sun Microsystems, Inc. | Halifax
Received on Friday, 13 September 2002 14:36:12 UTC