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 8992 - Coercion to Infoset extensions mean that HTML document could produce different infosets in an HTML5 UA and an HTML+RDFa UA
Summary: Coercion to Infoset extensions mean that HTML document could produce differen...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML+RDFa (editor: Manu Sporny) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Manu Sporny
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/rdfa/#preserv...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 07:29 UTC by Maciej Stachowiak
Modified: 2011-08-04 05:06 UTC (History)
4 users (show)

See Also:

Attachments

Description Maciej Stachowiak 2010-02-14 07:29:47 UTC 
The Coercion to Infoset extensions mean that HTML document could produce different infosets in an HTML5 UA and an HTML+RDFa UA. Converting an HTML5 DOM to an XML infoset should give consistent results, regardless of whether the UA supports various extensions.
Comment 1 Manu Sporny 2010-02-16 04:29:59 UTC 
RDFA-SPEC-SECTIONS [preserving-namespaces-via-coercion-to-infoset]
Comment 2 Manu Sporny 2010-05-05 03:06:39 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 document:

http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Agreed

Change Description: 

None.

Rationale:

I agree. The HTML5 spec should be changed to include following rule in the Coercion to Infoset section:

"""
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#)
"""

Doing so would simplify the HTML+RDFa specification and ensure that the same Infoset is created for HTML5 UAs and HTML+RDFa UAs.
Comment 3 Michael[tm] Smith 2011-08-04 05:06:21 UTC 
mass-move component to LC1