W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2010

[Bug 9976] New: Base Polyglot Markup's XML requirements on Canonical XML (C14N)

From: <bugzilla@jessica.w3.org>
Date: Mon, 21 Jun 2010 21:37:20 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9976-2486@http.www.w3.org/Bugs/Public/>

           Summary: Base Polyglot Markup's XML requirements on Canonical
                    XML (C14N)
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://dev.w3.org/html5/html-xhtml-author-guide/html-x
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot
        AssignedTo: eliotgra@microsoft.com
        ReportedBy: xn--mlform-iua@xn--mlform-iua.no
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org,

As I noted in Bug 9965, Canonical XML - aka C14N - have some requirements that
looks like relevant design principles for Polyglot Markup - at least in some
stake holders' opinions. For example C14n requires:

* that <li/> should be written as <li></li>
* that document uses UTF-8
* that class="   one     two" is written class="one two" 
* XML declaration must be removed

For overview: http://www.w3.org/TR/xml-c14n#Terminology

Hence i suggest as a design principle for the Polyglot Markup that the XML
requirements should be based on Canoncical XML - except when that principle is
incompatible with HTML5. (One place where it is incompatible is in C14N's
requirement to remove the DOCTYPE).)

Positive: Adopting such a principle would make it simpler to justify and agree
about the design of Polyglot Markup. 

Negative: The requiremetns of C14N are, however, stricter than the the _real_
requirements of Polyglot Markup.

JUSTIFICATION: It seems to be the case that quite a few people with a stake in
Polyglot Markup wants to base the polyglot requirements on something that is
stricter thant the the _real_ requirements. And because of that, I think it is
important to have something solid to base those extra requirements on. Rather
than randomly picking one's favorite restrictions/permissions.

(For example, there are conditionas when it is not necessary to write <li/> as
<li></li> - even when the document is meant to be polyglot. But instead of
defining the exceptions  - or our own restrictions - we could simply pick
Canonical XML's rulings as base.)

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, 21 June 2010 21:37:22 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:51 UTC