[6198] in www-talk@info.cern.ch
Versioning HTML at the server (was Re: Netscape v NCSA, Progress? )
daemon@ATHENA.MIT.EDU (Chris Lilley, Computer Graphics Un)
Tue Oct 18 06:08:43 1994
Date: Tue, 18 Oct 1994 11:04:39 +0100
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: lilley@v5.cgu.mcc.ac.uk
From: lilley@v5.cgu.mcc.ac.uk (Chris Lilley, Computer Graphics Unit)
To: Multiple recipients of list <www-talk@www0.cern.ch>
In message <941017222851.6448@utopia> Kee Hinckley wrote:
> This isn't a problem unique to Netscape. Table support in NCSA's
> 2.5 beta results in the same issue. In fact it's worse, a table
> read in a browser without table support looks like trash.
The table support is less of a problem; at least it forms part of an
established standard-in-progress (HTML 3.0). Other browser writers
can make software that understands the same markup without having to
guess at the full spec from a few examples.
However, yes, how does a client tell the server "I understand HTML 3.0"
or, more tricky, "I understand tables inline JPEG and this-bit but not
that-bit"
How should we serve HTML 3 to the Web? Is it still text/html ? Should
the same URL point to two different versions using server-side trickery?
--
Chris
