- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 03 Oct 2009 17:55:23 +0200
- To: Maciej Stachowiak <mjs@apple.com>
- CC: Sam Ruby <rubys@intertwingly.net>, Adrian Bateman <adrianba@microsoft.com>, HTML WG <public-html@w3.org>, Tony Ross <tross@microsoft.com>
Maciej Stachowiak wrote: > > On Oct 3, 2009, at 2:31 AM, Julian Reschke wrote: > >> Maciej Stachowiak wrote: >>> ... >>> That is true. >>> Is it ok that in an XML document, the API would give different >>> answers than the built-in XML namespace mechanism? Would it be >>> acceptable to encourage consumers to process XML content based on >>> "effective namespace URI" instead of based on actual Namespaces in >>> XML processing? >> > ... >> >> I would hope that that API gave the same answers for XML documents, >> and would only differ in HTML. > > Sam suggested an API that is implementable in pure ECMAScript > (presumably it works by looking at ancestor elements to find namespace > declarations). That would not give the same answer for an XML document > as namespaceURI. > ... Given an XML document, the DOM in UAs does support L2 (or am I missing something?). In which case a pure script implementation could just delegate to namespaceURI, and thus return the same result. BR, Julian
Received on Saturday, 3 October 2009 16:11:01 UTC