[Bug 8991] Change to "coercion to infoset" rules is underdefined

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8991


Manu Sporny <msporny@digitalbazaar.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




--- Comment #2 from Manu Sporny <msporny@digitalbazaar.com>  2010-05-05 03:00:37 ---
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.

-- 
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 Wednesday, 5 May 2010 03:00:40 UTC