Cart
[Home] [By Thread] [By Date] [Recent Entries]
Mark Baker writes:
> >Fortunately, XML isn't source code (or compiled code), so we don't
> >have the same problem -- I was using that example only to demonstrate
> >that once there's software deployed that recognizes a certain set of
> >XHTML Namespaces (preferably a set with one member), it will be very
> >difficult to introduce any new Namespaces.
>
> Which begs the question, when is it proper/suitable/desirable/"right" to
> create a new namespace?
The same time you'd create a new Java package, or change a company's
domain name -- i.e. when it's no longer identifiable as the same
thing. If the HTML WG decides that <a> should mean 'answer' rather
than 'anchor', they should create a new Namespace; until then, leave
it be.
All the best,
David
--
David Megginson david@m...
http://www.megginson.com/
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
