This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 5.3 says: "If the XML API is namespace-aware, the tool must ensure that proper ([namespace name], [local name], [normalized value]) namespace tuples are created when converting the non-XML mode DOM into an Infoset." But which are the "proper" namepace tuples? The example implies they are created by attributes with xmlns: in the name, but those have no special meaning in HTML5 and do not normally declare a namespace, so it's not clear, without being more specific, what is "proper".
RDFA-SPEC-SECTIONS [conformance-criteria-for-xmlns:-prefixed-attributes]
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 document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Fixed Change Description: Included one more example to be more clear how the "proper" namespace tuple is generated: http://dev.w3.org/cvsweb/html5/rdfa/drafts/ED-rdfa-in-html-20100504/Overview.html.diff?r1=1.7&r2=1.8&f=h """ If the XML API is namespace-aware, the tool must ensure that ([namespace name], [local name], [normalized value]) namespace tuples are created when converting the non-XML mode DOM into an Infoset. Given a standard xmlns: definition, xmlns:foo="http://example.org/bar#", the [namespace name] is http://www.w3.org/2000/xmlns/, the [local name] is foo, and the [normalized value] is http://example.org/bar#, thus the namespace tuple would be (http://www.w3.org/2000/xmlns/, foo, http://example.org/bar#). """ Rationale: Further defining what "proper" means is helpful to implementers.
mass-move component to LC1