W3C home > Mailing lists > Public > public-sysapps@w3.org > June 2012

Re: Updated charter proposal

From: Adam Barth <w3c@adambarth.com>
Date: Wed, 6 Jun 2012 13:48:38 -0700
Message-ID: <CAJE5ia8Hz91uX4-KP==iqbbC4SovNSORzzNG2F=Qj0vrfGLMoQ@mail.gmail.com>
To: Robin Berjon <robin@berjon.com>
Cc: JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>, Wonsuk Lee <wonsuk11.lee@samsung.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
On Wed, Jun 6, 2012 at 1:09 PM, Robin Berjon <robin@berjon.com> wrote:
> On Jun 6, 2012, at 18:19 , Adam Barth wrote:
>> On Wed, Jun 6, 2012 at 1:37 AM, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es> wrote:
>>> I think it is important to add Contacts to phase 1 just to complete the
>>> set of Core APIs for Communication i.e. Messaging, Contacts and Telephony,
>>> they are a pack that should go together, IMO, and be a priority. On the
>>> other hand, we have very good starting points for Contacts, namely, the
>>> existing W3C Draft from DAP and the recent work from Mozilla B2G ...
>>
>> There's no way we're going to be "complete" in any sense of the word
>> after phase 1.  Phase 1 is about getting traction and building
>> momentum.
>
> I don't think that Jose meant that the group or its deliverables are going to be complete after phase 1. Rather, he is pointing to the fact that Messaging, Contacts, and Telephony form some kind of coherent basic gang that it would be good to complete. I think I agree: if you put those together you can start writing some of the most fundamental apps in a common phone with just SysApps. Doing so should provide a useful litmus test for the viability of the system as a whole.

If that's the case, I would suggest we move them all out of phase 1.
The phase 1 deliverables should be easy wins rather than large
constellations of complexity.

Adam
Received on Wednesday, 6 June 2012 20:49:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 June 2012 20:49:38 GMT