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

[Bug 10692] New: Fix coercion to Infoset for HTML5 to correctly preserve xmlns attributes

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Sep 2010 03:41:45 +0000
To: public-html@w3.org
Message-ID: <bug-10692-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10692

           Summary: Fix coercion to Infoset for HTML5 to correctly
                    preserve xmlns attributes
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://www.w3.org/2010/02/rdfa/track/issues/3
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: msporny@digitalbazaar.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


This bug is related to RDFa Working Group ISSUE-3:

http://www.w3.org/2010/02/rdfa/track/issues/3

RDFa uses the xmlns: pattern to declare prefix mappings, it is important that
namespace information that is declared in non-XML mode HTML5 documents are
mapped to an Infoset correctly. In order to ensure this mapping is performed
correctly, the "Coercing an HTML DOM into an infoset" rules defined in [HTML5]
must be extended. The spec-ready text can be found here:

http://www.w3.org/TR/rdfa-in-html/#preserving-namespaces-via-coercion-to-infoset

Note, that this text is not a replacement for the current Coercion to Infoset
rules, but is an addition to the current Coercion to Infoset rules in the HTML5
specification. The goal is to preserve the old behavior of placing the xmlns:
value in a non-namespaced tuple and add additional behavior on top of the old
behavior that properly creates the correct Infoset namespace tuple. 

In other words, the change does not break backward compatibility, but is meant
to ensure that xmlns: values can be extracted in the same way in Javascript and
DOM environments without regard for whether or not the source document was an
HTML5 document or an XHTML5 document.

Any solution that achieves this desired effect would be an acceptable
resolution to this bug.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 23 September 2010 03:41:47 UTC

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