W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2012

Battery API Last Call Comment Status

From: <Frederick.Hirsch@nokia.com>
Date: Tue, 17 Jan 2012 21:48:57 +0000
To: <public-device-apis@w3.org>
CC: <Frederick.Hirsch@nokia.com>
Message-ID: <4E4AE785-B7C7-4825-B320-6671EB7C6571@nokia.com>
I took an action to summarize the status of Battery API Last Call comments.

Of 5 comments, two are confirmed closed, one is resolved but awaiting official confirmation (LC-2575), one is partly resolved with additional changes suggested (LC-2574), and one needs a proposal (LC-2577).

(1) LC-2574 (Additional proposal to consider) "events need to be queued using the task queue defined in HTML5." Anne

* Additional updates suggested.

Anssi updated spec, see http://lists.w3.org/Archives/Public/public-device-apis/2011Dec/0013.html

Additional suggestions from Anne, see  http://lists.w3.org/Archives/Public/public-device-apis/2012Jan/0006.html

* Conformance requirements with respect to the attributes could be merged. E.g. "The attribute must be set to false if the battery is discharging" and
 "When the battery charging state is updated, the user agent must queue a task which sets the charging attribute's value" would be better if all the requirements 
where in the latter statement and you would just define the attribute as returning its value.

* In the list of attributes event handler attributes are listed as well, except they are not defined there. 
They are defined in the next subsection. Somewhat duplicitous if you ask me.

(2) LC-2575 (Resolved, confirmation needed from Anne), should there be a privacy section, Anne

Resolution implemented, privacy section added, see http://dev.w3.org/2009/dap/system-info/battery-status.html#security-and-privacy-considerations

* Awaiting confirmation from Anne that resolved.

(3) LC-2576 (Closed), level attribute should be listed after the dischargingTime attribute, Sergiu

* Change implemented, confirmed as resolved

(4) LC-2577 (Proposal needed), no way to distinguish whether battery present, Wayne

Discussion died down on task force list after general agreement that fingerprinting not an issue

* Is this still an issue? If so, concrete proposal needed

(5) LC-2580 (Closed) "charging attribute to be set to true, even though the battery is actually discharging", Wayne

* Resolution agreed on list and implemented in spec, confirmed by Wayne on list. I have updated issue to reflect resolution agreed on list.

regards, Frederick

Frederick Hirsch

For tracker, this should complete ACTION-497
Received on Tuesday, 17 January 2012 21:49:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:52 UTC