- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 27 Oct 2009 01:11:48 +0000 (UTC)
- To: Toby Inkster <tai@g5n.co.uk>
- Cc: RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>
On Mon, 26 Oct 2009, Toby Inkster wrote: > On Mon, 2009-10-26 at 18:40 +0100, Julian Reschke wrote: > > Which of course is caused by the fact that you simply can't serve > > XHTML as text/html. The media type is authoritative, so recipients > > will treat it as HTML. > > I think this is something that is often overstated. > > RFC 2854 notes that "different versions [of HTML] are distinguishable by > the DOCTYPE declaration contained within them", so -- assuming that > XHTML is a "version" of HTML, whatever that means -- it is not incorrect > behaviour to detect an XHTML DOCTYPE and perform version-specific > parsing on the content. > > I realise that many popular user agents (especially desktop browsers) do > not do this, but that doesn't make it wrong to do so. This is one of the main things that HTML5 fixes in its updated text/html registration: http://www.whatwg.org/specs/web-apps/current-work/multipage/iana.html#text/html -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 27 October 2009 01:12:12 UTC