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

RE: Updated charter proposal

From: Suresh Chitturi <schitturi@rim.com>
Date: Wed, 6 Jun 2012 18:47:15 +0000
To: JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>, Adam Barth <w3c@adambarth.com>, Wonsuk Lee <wonsuk11.lee@samsung.com>
CC: "public-sysapps@w3.org" <public-sysapps@w3.org>
Message-ID: <8B118C943801754098C9B36B567EABA30CA24F@XMB104ADS.rim.net>
> -----Original Message-----
> From: JOSE MANUEL CANTERA FONSECA [mailto:jmcf@tid.es]
> Sent: Wednesday, June 06, 2012 3:38 AM
> To: Adam Barth; Wonsuk Lee
> Cc: public-sysapps@w3.org
> Subject: Re: Updated charter proposal
> 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 ...

Yes, certainly the draft from DAP can be used as  good starting point considering that DAP spent good amount of time resolving the formatting (e.g. vCard, etc.) issues, and hopefully this group won't need to go through it again.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 6 June 2012 18:48:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:09 UTC