[Bug 5808] Define a way to coerce HTML5 parser output to an XML 1.0 4th ed. + Namespaces 1.0 infoset

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


Henri Sivonen <hsivonen@iki.fi> changed:

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




--- Comment #4 from Henri Sivonen <hsivonen@iki.fi>  2008-07-23 06:39:07 ---
(In reply to comment #3)
> Done, 

Thanks.

> but I didn't always follow your suggestions. 

"Construct the DOM as if appropriate namespace declarations were in scope.",
"Construct the DOM as if these were default namespace declarations." and
"Construct the DOM as if these were namespace prefix declarations." are vague
compared to saying that it is permissible to a) drop NS declarations and b)
synthetize NS declarations.

> In particular, I made bad
> names and attributes just get mutated so that bad characters turn into "_"
> characters, with clashes being dealt with by dropping attributes, instead of
> suggesting using a mapping function.

I'd much prefer having a mapping function that can't cause clashes. That way, I
don't need to deal with attribute name clashes. Also, when the mapping function
cannot cause element name clashes, implementation that don't maintain separate
stack comparison name and an app-exposed name for elements would automatically
be protected. (The Validator.nu parser maintains a stack comparison name and an
exposed name separately already to allow pointer compares instead of
case-insensitive string compares when an SVG camelCase name is the exposed name
on the stack.)


-- 
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, 23 July 2008 06:39:49 UTC