On 9/5/11 2:38 PM, Adam Barth wrote:
On Mon, Sep 5, 2011 at 2:33 PM, Charles Pritchard<[email protected]> wrote:
On Sep 5, 2011, at 12:06 PM, Adam Barth<[email protected]> wrote:
On Sun, Sep 4, 2011 at 2:08 PM, Charles Pritchard<[email protected]> wrote:
On 9/4/11 6:39 AM, Anne van Kesteren wrote:
On Sun, 04 Sep 2011 15:12:45 +0200, Arthur Barstow<[email protected]>
wrote:
The CfC to publish a new WD of DOM Core was blocked by this RfC. I will
proceed with a request to publish a new WD of DOM Core in TR/. The name DOM
Core will be used for the upcoming WD. If anyone wants to propose a name
change, please start a *new* thread.
Given that the specification replaces most of DOM2 and DOM3 I suggest we
name it DOM4, including for the upcoming WD (or alternatively a WD we
publish a couple of weeks later).
I propose calling it "Web Core".
WC1 (Web Core version 1).
WebCore is one of the major implementation components of WebKit.
Calling this spec Web Core might be confusing for folks who work on
WebKit. It would be somewhat like calling a spec Presto. :)
Or calling a browser "Chrome".
:)
Web Core does implement web core, doesn't it?
Yes, but it also implements HTML5, which isn't part of Web Core.
HTML5 includes DOMCore in its dependencies.
http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#dependencies
From the DOMCore goals: "moving features from HTML5 that ought to be
part of the DOM platform here, while preventing a dependency on HTML5".
DOMCore specifies the EventTarget, from which Node, Element and Document
inherit, as well as the Event class, from which even non-node classes,
such as web messaging, inherit. And the DOMException enumeration.
The web core sub-directory contains modules (such as workers) which
include DOMCore as the root of their dependency chain. The naming seems
appropriate to me.
All that said, I'll re-assert: I'm fine with Anne taking the name of
DOMCore in the direction of his choosing. I still believe that "Web
Core" as a name and semantic has more utility than "DOM4", both in the
authoring of specifications and the implementation of various specs
which build upon EventTarget and/or Event as their root interface.
-Charles
