W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14565] Chain of normative statements connecting MIME type to HTML vs. XHTML is broken or unobvious

From: <bugzilla@jessica.w3.org>
Date: Thu, 27 Oct 2011 20:22:10 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RJWSo-0005Jq-Cl@jessica.w3.org>

--- Comment #5 from Henri Sivonen <hsivonen@iki.fi> 2011-10-27 20:22:09 UTC ---
(In reply to comment #3)
> >  * A normative requirement that says which parser must be used for which input
> > MIME types.
> For text/html, this is now done (by fixing a bogus requirement that was
> attempting to do this before).


> For XML, it's done in the context of navigation.

Where? I tried following reverse links for XML MIME type but didn't find a
navigation-related fetch result dispatched on XML MIME type.

> I've added a few paragraphs defining these, but it's not very satisfactory. 


> Instead, the spec specifies (in the text/html definition) that the act of using
> the text/html label declares that the resource is HTML. Is that sufficient?

Yes, thanks. The problems around polyglot, non-conforming streams, etc., are
why I said left as an exercise to the editor. :-)

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 27 October 2011 20:22:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:06 UTC