This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20199 - HTML parser in toolchain vs polyglot: Say that such an HTML parser may produce polyglots
Summary: HTML parser in toolchain vs polyglot: Say that such an HTML parser may produc...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Eliot Graff
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2012-12-03 06:18 UTC by Leif Halvard Silli
Modified: 2013-04-24 01:36 UTC (History)
4 users (show)

See Also:


Description Leif Halvard Silli 2012-12-03 06:18:52 UTC
The XML/HTML task force concluded that there is a dichotomy between "HTML parser in tool chain" vs polyglot.  See:

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."
Comment 1 Eliot Graff 2013-04-24 01:36:01 UTC
    EDITOR'S RESPONSE: This is an Editor's Response to your comment. If
    you are satisfied with this response, please change the state of
    this bug to CLOSED. If you have additional information and would
    like the Editor to reconsider, please reopen this bug. If you would
    like to escalate the issue to the full HTML Working Group, please
    add the TrackerRequest keyword to this bug, and suggest title and
    text for the Tracker Issue; or you may create a Tracker Issue
    yourself, if you are able to do so. For more details, see this

    Status: Rejected
    Rationale: This seems to be an edge case rather than a use case that we want to highlight (and by doing so, promote).