CfC: Call for Consensus to transition Battery API to Proposed Recommendation (PR) : deadline 10 March

This is a Call for Consensus (CfC) to request a transition of the Battery API [1]  to Proposed Recommendation (PR) and publish the PR once transition is approved.

No substantial changes have been made to the Battery API since the W3C Candidate Recommendation of December 2014 [2], however document now has more detailed privacy considerations, including advice regarding the implications of high precision readouts, based on feedback from implementation experience [3]. It also has updated references.

The implementation report [4] report of the API shows all features have been implemented by two independent deployed browsers, meeting the CR exit criteria. We had no CR features marked as 'at-risk'.

There is a known issue with some WebIDL implementations that are not specific to the Battery API;  the interoperability effect of that issue is minimal, since it only
affects error handling in case where the API is mis-used, which is in practice detected at development time rather than usage time.

If you have any questions or concerns about this CfC please respond by next week, 10 March. Positive response is preferred and encouraged (even a +1 is useful), and silence will be considered as agreement with the proposal. Please respond by 10 March 2016.

Please note that a request to advance to Proposed Recommendation (PR) means that the group believes the specification is stable and appropriate for advancement to Recommendation status.  

Thanks

regards, Frederick

Frederick Hirsch
Chair, W3C Device APIs WG (DAP)

www.fjhirsch.com
@fjhirsch

[1] Editors draft: https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html

[2] CR draft: https://www.w3.org/TR/2014/CR-battery-status-20141209/

[3] https://lists.w3.org/Archives/Public/public-device-apis/2015Aug/0000.html

[4] https://w3c.github.io/test-results/battery-status/20160226.html

Received on Friday, 4 March 2016 01:17:29 UTC