Hi,
(CCed archive.)
These things need defining:
Scenario A: No browser changes (changes to infoset coercion for non-
browser class of products):
1) Define how to look up mapping from prefix "foo" to value in terms
of DOM Level 2 concepts in the XML case.
(There's a match if there's an attribute with local name "foo" and
namespace "http://www.w3.org/2000/xmlns/";.)
2) Define how to look up mapping from prefix "foo" to value in terms
of DOM Level 2 concepts in the HTML case.
(There's a match if there's an attribute with local name "xmlns:foo"
and no namespace.)
3) For infoset-oriented products, adjust infoset coercion to say
that where the HTML5 parsing algorithm today emits an attribute in no
namespace with local name "xmlns:foo" and value "bar", create a
namespace information item with prefix "foo" and namespace name "bar".
4) Define how to look up mapping from prefix "foo" to value in terms
of Infoset concepts. (There's a match if there's a namespace
information item with prefix "foo".)
Scenario B: Browser changes (unlikely to pass in the WG; included here
for completeness and contrast):
1) Define that where the HTML5 parsing algorithm today emits an
attribute in no namespace with local name "xmlns:foo", instead emit an
attribute in the "http://www.w3.org/2000/xmlns/"; namespace with local
name "foo".
2) Define how to look up mapping from prefix "foo" to value in terms
of DOM Level 2 concepts. (There's a match if there's an attribute with
local name "foo" and namespace "http://www.w3.org/2000/xmlns/";.)
(And in all lookup cases, if there's no match, walk to parent element
node / element information item and try again.)
--
Henri Sivonen
[email protected]
http://hsivonen.iki.fi/
