- From: Jirka Kosek <jirka@kosek.cz>
- Date: Mon, 17 Mar 2014 14:02:09 +0100
- To: Anne van Kesteren <annevk@annevk.nl>
- CC: "www-dom@w3.org" <www-dom@w3.org>
- Message-ID: <5326F251.4000706@kosek.cz>
On 17.3.2014 12:17, Anne van Kesteren wrote: > I recommend searching the archives (public-webapi, not www-dom, and > maybe public-webapps too). We've been over this a few times. The basic > idea is that we don't really need namespaces and CSS namespaces was a > sunk cost mistake. The trap of using "we". :-) I went through some old archived threads, and my general impression was that in order to finish Selectors API 1 on time idea of NSResolver was just postponed. Since DOM4 is object model not only for HTML, but also for XML, it should support namespaces on all places where user would expect it, including Selectors API. If the consensus is that XML should not be fully supported in DOM4, then the spec should at least clearly say what is not supported. Otherwise you will get repeated requests why only subset of selectors is supported in Selectors API. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------
Received on Monday, 17 March 2014 13:02:36 UTC