Lists Home |
Date Index |
- From: Paul Prescod <firstname.lastname@example.org>
- To: xml-dev <email@example.com>
- Date: Sun, 29 Aug 1999 13:08:02 -0400
David Megginson wrote:
> 2. If the intention of XHTML is to continue to create new Namespaces
> for future versions of XHTML, you run into a serious deployment
> problem where old software will not work properly with new
How can you know, in 1999, whether Internet Explorer 5.0 will work with
HTML 6 documents? You cannot. If robust behavior is your primary goal
then you must presume not.
It is extremely suspect that an HTML 2.0 browser could just display an
applet-bearing page without the applet and presume that that's "good
enough." And EVEN IF that assumption is usually valid in the world of
human-read documents there is no way you can build an ecommerce
infrastructure on the hope that future versions will magically degrade
nicely. We need a real graceful degradation strategy.
> If you don't believe that versioning is a problem on
> the Web, then look at the lack of even Java 1.1 applets for general
> use (because Netscape 3.0 doesn't have a Java 1.1 VM).
What would you have JavaSoft do? Pretend that Java 1.1 programs are
really Java 1.0 programs so that the crash occurs deep in the JVM
instead of at the point that the problem is first detected? "Hmmm. It's
looking for a method I don't have. I'll just return NULL and hope it
No version 1.x software can magically handle version 2.x data without a
well-defined graceful degradation mechanism. You are asking the XHTML
people to pretend that they have that mechanism when they do not.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)