Lists Home |
Date Index |
- From: Paul Prescod <email@example.com>
- To: xml-dev <firstname.lastname@example.org>
- Date: Sun, 29 Aug 1999 17:31:14 -0400
David Megginson wrote:
> 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
Wouldn't it be considered extremely bad practice to make version 1.1 of
a Java package be backwards incompatible with version 1.0? Well the
various versions of HTML are *incompatible* in a very basic sense:
documents conforming to one do not conform to another.
> If the HTML WG decides that <a> should mean 'answer' rather
> than 'anchor', they should create a new Namespace; until then, leave
> it be.
So if HTML 6.0 has <a xlink:href=""> and not <a href=""> they should
keep the same namespace? And if next year's <a> element allows
<xlink:locator> sub-elements? And removes the href attribute?
When is different different enough? I claim that as soon as any
application could break because of the difference, that's different
What's the point of the namespace if you cannot rely on consistency in
the objects that claim to derive from it?
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)