W3C home > Mailing lists > Public > public-html@w3.org > October 2008

RE: HTML5 Specification - List of sections and corresponding work estimates

From: Dailey, David P. <david.dailey@sru.edu>
Date: Mon, 27 Oct 2008 13:59:45 -0400
Message-ID: <1835D662B263BC4E864A7CFAB2FEEB3D01A2EB26@msfexch01.srunet.sruad.edu>
To: "Ian Hickson" <ian@hixie.ch>, <public-html@w3.org>

Thanks Ian,

It sounds like a good idea. 

A couple of things come to mind: the scope of some of these may overlap
with existing initiatives within W3C. The WebApps Working Group [1]
comes to mind. The Graphics activity and the Forms working group are
other obvious examples where the scope of work within HTML5 has
occasionally crept into sometimes disputed territory. 

Secondly, with regard to item 2 "Interaction events" , my concern is
that the range of events now relevant to web development (due to
presence of the web over mobile devices) has grown to include
multi-touch devices, accelerometers and more. The differentiation of
click from select or pan from drag has resulted in the independent
reinvention of certain proprietary solutions which could, in the long
run, prove antithetical to interoperability.  I understand that the
WebApps Working Group is considering such expanded concepts of
"interaction." If so then maybe that would be a place to which to
offload such work.

cheers
David


[1] http://www.w3.org/2008/webapps/charter/ 


-----Original Message-----
From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
Behalf Of Ian Hickson
Sent: Monday, October 27, 2008 1:25 PM

Recently, people have asked me for a list of sections that could be spun

off from HTML5 into their own specs, with other editors, to lighten the 
workload for taking HTML5 to REC.

[ ... ]

2. Interaction events

Scope: defining the relationship between user interaction (clicks, mouse

movements, key presses, etc) and DOM2 Events, hit testing, and
documenting 
any special behavior relating to HTML features.

Skills and knowledge needed: JS, DOM, HTML, reverse-engineering
browsers. 
Access to multiple browsers and platforms necessary.

Estimated workload:
 - 6 months at 40h/week researching, reverse engineering and specifying
 - 4 months at 20h/week responding to immediate feedback
 - 12 months at 5h/week responding to further feedback
 - 24 months at 1h/week responding to further feedback
Received on Monday, 27 October 2008 18:01:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:58 UTC