- From: Charles McCathieNevile <chaals@opera.com>
- Date: Mon, 09 Apr 2007 19:10:52 -0400
- To: "Maciej Stachowiak" <mjs@apple.com>, "Dao Gottwald" <dao@design-noir.de>
- Cc: liorean <liorean@gmail.com>, "HTML WG" <public-html@w3.org>
On Mon, 09 Apr 2007 17:22:19 -0400, Maciej Stachowiak <mjs@apple.com> wrote: > On Apr 9, 2007, at 1:08 PM, Dao Gottwald wrote: >> liorean wrote: >>> Well, according to the charter this WG's deliverables are to include >>> among other things: >>> - "Document Object Model (DOM) interfaces providing APIs for such >>> a language." >>> - "APIs for the manipulation of linked media." >>> - "Editing APIs and user-driven WYSIWYG editing features." >> >> Is there an active DOM WG? If so, I don't think we can take over >> their work. > > The Web API WG is the successor to the DOM WG. I can't speak for the > group officially, but I don't think it would have any problem with > HTML-specific DOM APIs being defined in the HTML spec (just as SVG > defines the SVG DOM). I can't provide consensus of the group without asking them what that might be, but the understanding I have as WebAPI chair is that WebAPI does Web APIs in general, but there is no reason we need to take over something language-specific that is in some other group, unless they ask and we have resources to do so... So I don't see any particular problem with the HTML WG defining HTML-specific APIs in particular (and reviewed the charter with that question among others in my mind). Andif you want the Web API group to take on new deliverables, you wil probably need to volunteer up the manpower to do the work - we are somethwat stretched as it is. Cheers Chaals -- Charles McCathieNevile, Opera Software: Standards Group hablo español - je parle français - jeg lærer norsk chaals@opera.com Try Opera 9.1 http://opera.com
Received on Monday, 9 April 2007 23:11:06 UTC