[battery] CfC for Battery API Last Call - decision is not to publish right now

The CfC period for publishing a Last Call of the Battery API ends today with the decision that we will NOT publish a Last Call of the Battery API at this time.

We discussed this on yesterday’s DAP call and the consensus on the call was not to advance this specification to Last Call until we have a stable draft that has been reviewed by the WG [1].

Some specific reasons not to advance to Last Call right now include the following:

1. there have been numerous editorial updates based on feedback during the CfC period, so we would like a chance to review those changes before progressing

2. We need to confirm that all specific concrete feedback has been addressed, some related actions include Anssi ACTION-702

3. The examples could use some simplification and revision, Anssi took an action, ACTION-700

4. We may wish to consider an update relating to the handling of low battery thresholds, Giri took an action, ACTION-699

5. we might wish to add a warning related to battery usage caused by this API

I do not expect a significant delay because of these changes, if we have an updated draft in a few weeks we can consider LC publication then.

Thanks for the review, list discussion and to the editors for timely updates. Let’s continue with the actions and review on the public list.

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Chair DAP
@fjhirsch

[1] http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/att-0059/minutes-2014-06-12.html#item06

On Jun 6, 2014, at 11:11 AM, Frederick Hirsch <w3c@fjhirsch.com> wrote:

> This is a Call for Consensus to publish a new Last Call for the Battery API specification on 19 June 2014, ending 24 July 2014 (a five week Last Call to account for holidays).
> 
> The draft is here:  https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html
> 
> This is a return to Last Call from CR to address the normative changes as noted in the status section:
> 
> [[
> 
> 	• Expose BatteryManager via getBattery() returning a Promise instead of a synchronous accessor. (Section 5)
> 	• Specify the behavior when a host device has more than one battery. (Section 6.1)
> ]]
> 
> The document also now links to the test suite on the cover page (upon publication this should also be noted in the status section and a link to a diff from the previous publication should also be added).
> 
> Much thanks to Mounir for the updated draft, please review it as part of this CfC.  As Mounir noted in his email, links to the commits are available for your review [1].
> 
> Please send all comments regarding this CfC to the public-device-apis@w3.org mailing list by next Friday, 13 June. Silence will be considered as agreement with publishing a new Last Call, but a positive response is preferred and encouraged (even a +1 will do).
> 
> regards, Frederick
> 
> Frederick Hirsch, Nokia
> Chair DAP
> @fjhirsch
> 
> 
> [1] http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0023.html
> 
> [[
> 
> It contains a list of changes in the "State of this Document" section.
> Otherwise, a detailed list of commits can be found here:
> 
> https://dvcs.w3.org/hg/dap/rev/104f34bf5872
> https://dvcs.w3.org/hg/dap/rev/f9fb2068c558
> (editorial changes)
> 
> https://dvcs.w3.org/hg/dap/rev/77dbe211ed07
> https://dvcs.w3.org/hg/dap/rev/d03d51adec91
> ]]
> 
> 
> 
>

Received on Friday, 13 June 2014 21:46:56 UTC