RE: Next Steps for W3C Coremob

Really closing the gap (as described by Dom in [1]) is a much longer effort than 6 months; all that can likely be achieved in that timeframe is a preliminary assessment of easily-identified gaps. What we need is a more long-term effort to:
- identify what's important, to build the apps and overall app experience that users want
- identify and prioritize gaps in the set of important things
- develop and promote plans to close them
- engage with WGs over time to help ensure progress toward closing the gaps
- repeat the above periodically, as this is not a "one and done" activity

Like Web & TV, CoreMob is a focused effort (on mobile) with broader purpose than just closing gaps; it's about promoting broad support for what's needed by developers to create mobile applications that users want. That means identifying which gaps are important - there are many, and we have to prioritize.

[1] http://www.w3.org/QA/2013/03/closing_the_gap_with_native_ap.html

Thanks,
Bryan Sullivan 

-----Original Message-----
From: Arthur Barstow [mailto:art.barstow@nokia.com] 
Sent: Monday, March 11, 2013 9:54 AM
To: ext Dominique Hazael-Massieux
Cc: public-coremob@w3.org
Subject: Re: Next Steps for W3C Coremob

On 3/11/13 10:44 AM, ext Dominique Hazael-Massieux wrote:
> As Charles indicated, merging with "closing the gap" isn't quite an 
> option due to the difference of timescales (closing the gap is a 
> 6-month focused effort, whereas I see CoreMob as a tool for the longer 
> term). 

OK, then make MindingTheGaps a 6-month focused effort of CoreMob ;).

Received on Monday, 11 March 2013 17:50:28 UTC