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

[battery] Call for Consensus: resolve LC-2965 to proceed with Battery API as-is, consider alternatives for v2

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Mon, 15 Sep 2014 16:41:02 -0400
Message-Id: <48FD5952-A3F7-4BB0-B386-01E0DA56886A@fjhirsch.com>
Cc: Frederick Hirsch <w3c@fjhirsch.com>, tobie.langel@gmail.com
To: Device APIs Working Group <public-device-apis@w3.org>
This is a Call for Consensus (CfC) to resolve the Battery API Last Call issue LC-2965. 

We had a resolution on the teleconference but as a courtesy to those who are unable to attend the call we are following up with a CfC.


LC-2965: https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-battery-status-20140828/2965


I don't understand why this API is developed separately from other sensor

It would be much better for developers if all sensor APIs were consistent.

The API difference between DeviceOrientation and Geolocation was bad
enough. Why are we repeating such mistakes over and over again?

Sorry for the late and negative feedback.



WG members discussed this on 4 Sept 2014 teleconference, for details see http://lists.w3.org/Archives/Public/public-device-apis/2014Sep/att-0020/minutes-2014-09-04.html#item04

Proposed Resolution: 

Continue Battery API with current approach given we have two implementations and support for the API as-is and no significant technical issue to support a late-stage restart. Can consider alternatives for a v.next as appropriate.

Please indicate support or concern regarding this CfC by replying to this message by 29 Sept 2014  - silence will be considered agreement (explicit agreement, even just a +1 preferred). Earlier responses would be helpful.


regards, Frederick

Frederick Hirsch, Nokia
Chair DAP

For Tracker, this completes ACTION-715
Received on Monday, 15 September 2014 20:41:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:12 UTC