[Bug 8833] Please allow the title of the spec currently known as "HTML5" to be changed to an accurate title.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8833





--- Comment #14 from Dean Edridge <dean@dean.org.nz>  2010-07-26 12:26:35 ---
(In reply to comment #13)
> Section 1.6 says this:
> 
> "This specification defines version 5 of the HTML syntax, known as 'HTML5'."
> and
> "This specification defines version 5 of the XHTML syntax, known as 'XHTML5'."
> 
> I do think that the title "HTML5" is a bit misleading and degrades "XHTML5" to
> a second or third class syntax. But XHTML likely will be dead anyway...


A specification needs to make sense, regardless of whether or not xhtml "takes
off", regardless of whether 10, 10 000, or 10 000 000 web pages use xhtml5. The
spec is supposed to be a technical report, it should not contradict it self.

This could have been fixed in 2007, or 2008, but several people (at least 5
individuals) have interfered with the process and prevented it from being
fixed.


> if XHTML5
> can not be delivered with MIME-type text/html (because of an incompatibility
> with a user agent spread by a certain company since many years).

No/yes, but there is is no such thing as xhtml5 served as text/html as xhtml5
is not a syntax. A text/html web page is html, NOT xhtml, regardless of syntax.
There is no such thing as a xhtml document with a .html file extension. People
can use a "xml-compatible" syntax in their html5 web pages without having to
bother with xhtml5 and XML parsers, some call this a 'polyglot' syntax. This,
also, needs to be clarified within the spec.

xhtml5 is not a syntax, or serialization, it is a language, and as a language,
it is defined as being a XML document. Calling the spec html5 has caused a lot
of confusion over this issue; most people don't know what the difference is
between html5 and xhtml5.

---

The W3C can not continue to publish a spec called "html5" which contains two
technologies called html5. The W3C have known about this problem since at least
March 2007.

The only way to fix this issue is to, at the very least, change the title of
the spec. There would also need to be some renaming/'reshuffling', within the
spec in order to make things logical and remove the contradictions and
confusion.

-- 
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 Monday, 26 July 2010 12:26:40 UTC