W3C home > Mailing lists > Public > public-html@w3.org > December 2012

[Bug 20199] New: HTML parser in toolchain vs polyglot: Say that such an HTML parser may produce polyglots

From: <bugzilla@jessica.w3.org>
Date: Mon, 03 Dec 2012 06:18:52 +0000
To: public-html@w3.org
Message-ID: <bug-20199-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20199

            Bug ID: 20199
           Summary: HTML parser in toolchain vs polyglot: Say that such an
                    HTML parser may produce polyglots
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
               URL: http://www.w3.org/TR/html-polyglot/#introduction
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot
                    Graff)
          Assignee: eliotgra@microsoft.com
          Reporter: xn--mlform-iua@xn--mlform-iua.no
        QA Contact: public-html-bugzilla@w3.org
                CC: eliotgra@microsoft.com, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org

The XML/HTML task force concluded that there is a dichotomy between "HTML
parser in tool chain" vs polyglot.  See:
http://www.w3.org/TR/html-xml-tf-report/#uc01

However, I believe this is a false conflict since an "HTML parser in an XML
toolchain" could be made to output polyglot markup. Thus there is not really a
conflict here - one can have both!

By adding this fact to the polyglot spec, we also take issue with the belief
that polyglot markup can change the face of the Web - from tag soup to
well-formed. 

Also, since some are very eager to promote the HTML parser solution, why not
promote it in polyglot markup as well?

Also, a related use case is that polyglot markup is easier to exchange between
different authoring tools. E.g. between a HTML WYSYWYG editor and an XHTMNL
WYSYWYG editor. 

So, at the end of (or after) the paragraph that currently begins "All web
content need not be authored in polyglot markup", add a sentence such as this: 

"For authors that, in order to consume non-well-formed Web content, place an
HTML parser in their XML toolchain or which use an XHTML editor that can import
HTML, it may also be an option to have the HTML parser transform the the Web
content to polyglot markup in order to combine the benefits of the HTML parser
in XML tool chain solution with the benefits of Polyglot Markup."

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 3 December 2012 06:19:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:36 UTC