Re: Updated charter proposal

Hi,

I agree with Jose and Bryan on keeping the Contacts in the charter.

Based on my past experience, the telephony, messaging and contacts APIs
are highly related and make sense to develop them together.

-sakari

On 6/6/12 1:37 AM, "JOSE MANUEL CANTERA FONSECA" <jmcf@tid.es> wrote:

>El 05/06/12 04:23, "Adam Barth" <w3c@adambarth.com> escribió:
>
>>On Mon, Jun 4, 2012 at 7:02 PM, Wonsuk Lee <wonsuk11.lee@samsung.com>
>>wrote:
>>>> -----Original Message-----
>>>> From: JOSE MANUEL CANTERA FONSECA [mailto:jmcf@tid.es]
>>>> Sent: Monday, June 04, 2012 11:13 PM
>>>> To: Adam Barth; public-sysapps@w3.org
>>>> Subject: Re: Updated charter proposal
>>>>
>>>> El 03/06/12 11:19, "Adam Barth" <w3c@adambarth.com> escribió:
>>>> >Based on the discussion on this list, I've put together an updated
>>>> >proposal for a charter:
>>>> >
>>>> >I was able to accomodate most of the requests folks sent to the list.
>>>> >The notable exceptions are Sensors, Calendar, and Contacts, all of
>>>> >which are deliverables for the Device APIs working group.
>>>>
>>>> It seems DAP wanted to follow the Intents approach in order to deal
>>>>better
>>>> with the security issues in a browser context. I think we do need APIs
>>>>for
>>>> them in a "System-Level" Context.
>>>
>>> I fully agree with Jose's opinion for above issues. We need to keep
>>>them in
>>> the charter.
>>
>>I agree that these deliverables fall under the general SysApps scope,
>>but we already have enough deliverables in the charter to keep us busy
>>for two years.  Rather than bite off more than we can chew, let's plan
>>to add them after we've been successful with the current group of
>>deliverables and are ready to re-charter.
>
>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 ...
>
>>
>>Adam
>>
>
>
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra política de envío y recepción de correo electrónico en el enlace
>situado más abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>

Received on Wednesday, 6 June 2012 17:09:35 UTC