[Bug 19925] Drop XHTML from the title of the document

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19925

--- Comment #16 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
I concur with the arguments of the bug filer.

As part of solving this bug, I have update the the title become

   «Polyglot Markup: A robust profile of the HTML5 vocabulary»

See
http://dev.w3.org/cvsweb/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html?annotate=1.96

With this change, I have fixed the part of the bug that relates to the title of
the document - the 'XHTML' word has been removed. The addition of the words
'robust' and 'profile' seems very much in line with the bug filer’s
argumentation. As for the term 'the HTML5 vocabulary', then it is a reference
to the subtitle of the HTML5 specification ('A vocabulary and associated APIs
for HTML and XHTML'), and thus bears a reference to HTML as the both a XHTML
and HTML vocabluarly.

I will try to incorporate more of the bug filer’s proposals in a later commit,
upon which I’ll close the bug. But I will reveal that much heed will given to
'robust'.

Just a brief justification for the removal of 'XHTML': Polyglot Markup already
puts have many requirements that or not just a the bare minimum for creating a
XHTML/HTML document. For example, the requirement to use both xml:@lang and
@lang is not because XHTML-compatible parsers are not required to understand
what @lang means. Even SVG has a @lang attribrute (though with different
semantics from xml:@lang), which SVG-supporting XML parsers must support.
Likewise, the requirement of polyglot markup to use @type="text/javascript" and
@type="text/css" is *also not* because XHTML parsers are not required to
support the *omission* of those attributes.

Btw, I even considered removing 'polyglot', but Larry has given good arguments
for keeping it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 18 April 2013 23:47:16 UTC