- From: Daniel Park <soohongp@gmail.com>
- Date: Tue, 29 May 2012 18:59:02 +0900
- To: Mounir Lamouri <mounir@lamouri.fr>
- Cc: public-sysapps@w3.org
Making the priority of APIs seems to me very tough and diverse. As usaul, I'd recommend the group to work on the *use cases & requirements* according to the level of voice of market/customer. Standard deliverables might be timely for the business opportunities. Otherwise, it will be failed or less worth... So, I strongly suggest to work on the *use cases & requirements* prior to API ordering. In addition, I fully agree with Robin's comment on the scope of APIs (as wide as we consider devices, not limited to mobile) Regards, Daniel -- Soohong Daniel Park Samsung Electronics, SWC On Fri, May 25, 2012 at 6:53 PM, Mounir Lamouri <mounir@lamouri.fr> wrote: > On 05/24/2012 06:22 PM, Adam Barth wrote: >> Concretely, I think we should pick a handful of deliverables to work >> on in the near term and then add more deliverables as we build up >> momentum and success. > > I agree. > >> For example, here's a set of deliverables that >> might make sense for the first round: >> >> * Security Model >> * Execution Model >> * Raw Socket API >> * DNS Resolution API >> * USB API > > Security and Execution model are indeed priorities but I wouldn't push > Raw socket, DNS Resolution and USB APIs. > > What about those: > - Alarm API > - Messaging API > - System Settings API > - Sensors API (btw, is that really going to leave DAP?) > - Telephony API > > I think we could find some people at Mozilla to edit those > specifications. At least, I could volunteer for the two firsts. > > Cheers, > -- > Mounir >
Received on Tuesday, 29 May 2012 09:59:39 UTC