- From: SULLIVAN, BRYAN L <bs3131@att.com>
- Date: Thu, 21 Jun 2012 16:42:50 +0000
- To: Robin Berjon <robin@berjon.com>, Adam Barth <w3c@adambarth.com>
- CC: "Sun, Dan" <Dan.Sun@verizonwireless.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
I've been out of the office for a few weeks on family leave, so missed the poll process. The System Settings (due to the discussion about the proposed Privacy API being implemented through it) and Network Interface APIs are priorities to me. I repeat below my earlier (June 2) input to the process: AT&T is prepared to contribute directly, with priority focus and if possible co-editing: * Device Capabilities API * Media Storage API * Network Interface API * Barcode Scanning API (new proposal as mentioned on the list) AT&T is prepared to contribute directly: * Security Model for Platform Applications * Execution Model for Platform Applications * Accounts API * Background Services API * Application API * Contacts API * File System API * Messaging API * Raw Sockets API * Sensors API * Secure Elements API * Web Intent Registration API We support the charter inclusion of the other APIs, and as time permits will be monitoring and commenting on the work. Thanks, Bryan Sullivan -----Original Message----- From: Robin Berjon [mailto:robin@berjon.com] Sent: Thursday, June 21, 2012 5:40 AM To: Adam Barth Cc: Sun, Dan; public-sysapps@w3.org Subject: Re: poll results On Jun 20, 2012, at 23:51 , Adam Barth wrote: >> 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. I don't have a dog in this one, but I'm a bit surprised about the System Setting one. I believe that Bryan expressed strong support several times, and that others shared that interest. Did I misread the list? -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 21 June 2012 16:43:55 UTC