RE: Updated charter proposal

Comment inline.

Thanks,
Bryan Sullivan 

-----Original Message-----
From: Adam Barth [mailto:w3c@adambarth.com] 
Sent: Tuesday, June 05, 2012 1:57 AM
To: Wonsuk Lee
Cc: JOSE MANUEL CANTERA FONSECA; public-sysapps@w3.org
Subject: Re: Updated charter proposal

On Mon, Jun 4, 2012 at 11:04 PM, Wonsuk Lee <wonsuk11.lee@samsung.com> wrote:
>> -----Original Message-----
>> From: Adam Barth [mailto:w3c@adambarth.com]
>> Sent: Tuesday, June 05, 2012 11:23 AM
>> To: Wonsuk Lee
>> Cc: JOSE MANUEL CANTERA FONSECA; public-sysapps@w3.org
>> Subject: Re: Updated charter proposal
>>
>> 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 understand. but I am confused because some items are classified to Phase 2
> and some items are removed from charter. I think meaning of removing is
> quite different with classification of Phase 2. I think it would be better
> to classify these as the phase 2 items instead of removing. What do you
> think?

The difference between listing a deliverable in Phase 2 and removing
it from the charter is that the working group will be able to work on
Phase 2 deliverables without re-chartering but working on deliverables
that have been removed will require re-chartering.

In practice, there isn't much of a difference between the two since
it's unlikely that we'll be able to actually finish all the
deliverables in the current draft in two years, when we're supposed to
re-charter anyway.  The main difference is that the more deliverables
we list in the charter, the harder the chairs will need to work to
keep the group focused and productive.

Do you have a specific list of deliverables you think we should add to
Phase 2?  I could be convinced to add two or three, but if you want to
balloon it to a laundry list, I'm going to push back.

<bryan> My sense is that we are only discussing two or three APIs that are not in the current charter. For myself, the Contacts API is an almost-essential adjunct to the Messaging API. Also, re the Sensors API, DAP may still be considering the way forward but I believe the sensitivity access to sensors will significantly limit what comes out of DAP (as it still seems focused on the browser security model). So at the least until that is resolved I would like to see the Sensors API on the Phase 2 list. This would allow the development of an ED without too much distraction to the group, as noted in earlier discussions for the other APIs.

Adam

Received on Tuesday, 5 June 2012 14:56:51 UTC