- From: Marcos Caceres <marcos@marcosc.com>
- Date: Fri, 14 Nov 2014 15:05:24 -0500
- To: Arthur Barstow <art.barstow@gmail.com>, public-openw3c@w3.org
On November 14, 2014 at 12:45:06 PM, Arthur Barstow (art.barstow@gmail.com) wrote: > > Marcos - if you have a recruiting "stump speech", by all means > give it to us ;-). I don't... but if I did, it would be something like: With HTML being "done" <wink, wink, tap-twice on the nose, illuminati-gang-sign>, it's time to focus W3C's core priorities on the next phase of the Web platform. In particular, it's time to both focus on what we know are areas of pain: * offline (addressed by service workers) * installability (addressed by manifest) * composability (web components) * security (CSP, CORS, MIX) * background event handling (PUSH) * accessibility (ARIA, particularly how they relate to web components, etc.) * sensor/device (access) * Reduce pervasive surveillance but TLSing all the things (and only enabling certain APIs over TLS)... * other fun stuff Once these core things are identified, we need to make sure that these projects are well-supported by the W3C (and that we stop supporting dead end projects that are lower priority or don't require, for example, a w3c staff member assigned to them). At the same time, we want to continue to find pain points that developers are experiencing across various fields that benefit society (e.g., education). Like, is the Web platform failing education institutions because it can't do something in particular (e.g., student's can't view their course material offline)? This effort will be use-case and evidence driven: involving various educational institutions that are W3C members. The same would apply to other fields/domain. That's the gist of it.
Received on Friday, 14 November 2014 20:07:49 UTC