- From: Sun, Dan <Dan.Sun@VerizonWireless.com>
- Date: Thu, 21 Jun 2012 10:53:01 -0400
- To: 'Adam Barth' <w3c@adambarth.com>
- CC: "public-sysapps@w3.org" <public-sysapps@w3.org>
> -----Original Message----- > From: Adam Barth [mailto:w3c@adambarth.com] > Sent: Wednesday, June 20, 2012 5:51 PM > To: Sun, Dan > Cc: public-sysapps@w3.org > Subject: Re: poll results > > On Wed, Jun 20, 2012 at 2:40 PM, Sun, Dan <Dan.Sun@verizonwireless.com> > wrote: > > I recently joined the mailing list. Sorry to miss the poll time. Can > > the listed APIs be revived from dropping? At least the first two if > > not possible to revive all four. > > > > System Settings API > > Network Interface API > > Resource Lock API > > DNS Resolution API > > Even with additional interest, these API are far enough down the > priority list that we're not likely to get to them in the first > charter. Once we actually make progress writing specifications and > shipping implementations, the working group will likely be interested > in rechartering and taking on more work. Network Interface API was close to the top of group #2 "Only Two Implementers" as below. Managing data connections between cellular network and WiFi is unavoidable for a mobile system. It should be addressed sooner than latter. Only Two Implementors --------------------- Secure Elements API 1 4 2 3 2 Idle API 1 2 2 1 2 DNS Resolution API 1 1 2 2 1 Network Interface API 2 1 2 2 2 Resource Lock API 1 1 2 1 2 Serial API 1 1 2 2 1 Application API 1 1 2 2 2 Accounts API 1 1 2 2 2 Web Intent Registration API 1 1 2 1 4 Thanks, Dan
Received on Thursday, 21 June 2012 14:53:35 UTC