W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

Re: ISSUE-148 (modularize d3e): Consider modularizing DOM3 Events [DOM3 Events]

From: Doug Schepers <schepers@w3.org>
Date: Wed, 03 Nov 2010 17:35:45 +0100
Message-ID: <4CD18F61.6040603@w3.org>
To: "www-dom@w3.org" <www-dom@w3.org>
CC: Garrett Smith <dhtmlkitchen@gmail.com>, Sergey Ilinsky <castonet@yahoo.co.uk>
Hi, Garrett-

We discussed this in a teleconference, and again at the WebApps WG 
face-to-face meeting at TPAC (W3C's tech plenary) [1].  Anne van 
Kesteren from Opera, the new editor of Web DOM Core, represented the 
viewpoint of modularizing DOM3 Events.

I understand and agree with the goals of modularization, but there are 
also other goals that modularization makes more difficult; it's always a 
judgment call in deciding which spec covers which functionality.

Anne specifically advocated splitting out parts of DOM3 Events and 
putting them instead into Web DOM Core, but the general tenor of the 
majority of browser vendors expressed a desire to finalize DOM3 Events, 
and did not feel that the benefits of modularizing or otherwise 
reorganizing the spec outweighed the benefits of finalizing this spec 
with the set of features currently defined.  So, we have resolved not to 
modularize the spec in the way you have suggested.

This is not to say that this may not be revisited in a later DOM spec, 
such as Web DOM Core.

Please let us know whether or not you are satisfied with this resolution.

[1] http://lists.w3.org/Archives/Public/public-webapps/2010OctDec/0430.html

-Doug Schepers
W3C Team Contact, SVG, WebApps, and Web Events WGs

Web Applications Working Group Issue Tracker wrote (on 10/6/10 8:58 AM):
> ISSUE-148 (modularize d3e): Consider modularizing DOM3 Events [DOM3 Events]
> http://www.w3.org/2008/webapps/track/issues/148
> Raised by: Doug Schepers
> On product: DOM3 Events
> Garrett Smith in<http://lists.w3.org/Archives/Public/www-dom/2010OctDec/0003.html>:
> [[
> I think we're all well aware of the monstrosity that has become D3E.
> D3E should be cut way back; it is too large and too complicated.
> Individual events and keyboard specificity are not "core" features;
> they are details and particulars of specific events. These events
> should be moved each to a separate specification.
> Moving specific event specification details to independent
> specifications will help reveal the real "core" of DOM 3 Events; so
> that core can be looked at more closely and independently questioned;
> e.g. "should useCapture be optional" and ditto for the extracted/moved
> event "Should we specify keyCode and charCode".
> To put this idea to action, I suggest starting with the a complicated
> part of the spec that seems the least core. For example, keyboard
> events, which itself is about 30 pages long. I would extract that from
> the spec and move it to another document and see how it reads on its
> own.
> If further help is wanted, then a request can be made for an associate editor.
> ]]
Received on Wednesday, 3 November 2010 16:35:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:16 UTC