W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2014

[battery] Moving Battery API forward, next steps?

From: <frederick.hirsch@nokia.com>
Date: Mon, 23 Jun 2014 14:58:42 +0000
To: <anssi.kostiainen@intel.com>, <public-device-apis@w3.org>, <timvolodine@google.com>, <ldeluca@us.ibm.com>
CC: <frederick.hirsch@nokia.com>
Message-ID: <9F0448FB-66F3-45F3-9BB2-0F1B2EF4E6BC@nokia.com>

I believe the following open items remain for the Battery API:

1. Proposed edit to new 2nd paragraph in section 6, http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0077.html (Frederick)

2. Follow up question/comment from Cathy http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0079.html 

3. ACTION-699: Giridhar Mandyam to Review battery and how low battery threshold is handled

4.. Add warning to Battery API that (naive) implementation of API could negatively affect battery life


I believe all of your comments have been addressed, see Anssi’s message: http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0070.html

Can you please confirm or note any remaining issues?


I believe Anssi addressed the various Cordova issues as noted in this email: http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0068.html

Can you please confirm that there are no additional issues or concrete proposals for the Battery API from the Cordova community?

Giri, have you received any internal feedback related to your action?


Are you aware of any additional open issues or questions related to the Battery API?  Can you please send a summary to the list? Also, if you are able to address any of the open issues I noted above before this Thursday’s DAP call, that would be helpful.


regards, Frederick

Frederick Hirsch, Nokia
Received on Monday, 23 June 2014 14:59:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:03 UTC