W3C home > Mailing lists > Public > public-html@w3.org > November 2007

Re: Feedback on the ping="" attribute (ISSUE-1)

From: Dimitri Glazkov <dimitri.glazkov@gmail.com>
Date: Thu, 8 Nov 2007 09:11:35 -0600
Message-ID: <fb15ac210711080711o5039738cm58ff9838f8182eb0@mail.gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: ian@hixie.ch, public-html@w3.org

On Nov 8, 2007 7:54 AM, T.V Raman <raman@google.com> wrote:
>
> Well said Roy!
>
> The more I see these discussions, the more I remain convinced
> that the HTML5 exercise should limit itself to what it originally
> claimed it was doing, namely documenting the actual behavior of HTML4.
>

Believe it or not, I actually lean toward agreeing with this position.
Procedurally, I think there are two distinct efforts and attempting to
conflate them hinders both. I am primarily interested in the SQL
storage, threading model, and the other new parts of the spec that I
would characterize as "tectonic-shifting", but also realize the
importance of keeping on with the HTML4 "as-it-occurs-in-the-wild"
evolution. It doesn't seem right to have these two efforts operate in
the same discussion and spec space.

In my head, I currently separate them as: HTML4++ discussion is on
public-html list, Web Applications discussion is on WHATWG list. Given
that WHATWG list is not part of the W3C, I don't understand how Web
API WG fits into the picture. It seems (and says so right here:
http://www.w3.org/2007/03/HTML-WG-charter#deliverables) that
client-side storage bits should be handled by this WG, but it doesn't
look like it.

Should the new features be separated more cleanly from HTML5 into the
deliverables of Web API WG? I don't understand the political or
historic context surrounding W3C groups, so this is more of a plea for
clarity than a suggestion.

:DG<
Received on Thursday, 8 November 2007 15:11:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:09 GMT