ISSUE-165: Clarify language around multiple batteries
Clarify language around multiple batteries
- State:
- CLOSED
- Product:
- Battery Status API
- Raised by:
- Frederick Hirsch
- Opened on:
- 2014-08-04
- Description:
- Issue noted on behalf of Tim Volodine <timvolodine@google.com> :
level -- instead of "sum" of levels it should be "average",
dischargingTime -- should be max dischargingTime if in parallel and sum if
in series.
http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0114.html - Related Actions Items:
- No related actions
- Related emails:
- draft minutes from today's teleconference, 7 Aug 2014 (from w3c@fjhirsch.com on 2014-08-07)
- [admin] Agenda - DAP Distributed Meeting 7 August 2014 (from w3c@fjhirsch.com on 2014-08-04)
- [battery] Battery Issue summary and status (from w3c@fjhirsch.com on 2014-08-04)
- DAP-ISSUE-165: Clarify language around multiple batteries [Battery Status API] (from sysbot+tracker@w3.org on 2014-08-04)
Related notes:
Fixed: https://dvcs.w3.org/hg/dap/rev/7857ba0e4266
Anssi email: http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0000.html
Additional update (email
http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0001.html )
---
On 19 Jun 2014, at 21:52, Frederick Hirsch <w3c@fjhirsch.com> wrote:
> Thank you for updating the section on Multiple Batteries based on my proposal and also for adding the paragraph in section 6 outlining the model for using battery full as a default.
>
> I suggest changing the last sentence of the 2nd paragraph in section 6 [1] from
>
> [[
>
> This prevents leaking of information that could be used to fingerprint a user and allow web developers to use the same code path for handling battery full and battery status unknown cases.
>
> ]]
>
>
> to
>
> [[
>
> The reason for using full battery defaults for unknown attribute values is that this will not cause applications to degrade performance or functionality by default if information is not available. It also reduces the potential for fingerprinting.
>
> ]]
>
> I think this might better capture the rationale.
This is a good improvement to the text, thanks!
Fixed:
https://dvcs.w3.org/hg/dap/rev/7067a05d6a79
http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0005.html
[[
You forgot to remove the old and incorrect description for dischargingTime.
Also, since the rule is practically the same for both charging time and discharging time (max if parallel, sum if serial), I would suggest using the same text for both attributes. That'd be much easier to read.
[[
The chargingTime attribute can be set to the maximum charging time of the individual batteries if charging in parallel, and to the sum of the individual charging times if charging serially.
The dischargingTime attribute can be set to the maximum discharging time of the individual batteries if discharging in parallel, and to the sum of the individual discharging times if discharging serially.
]]
Regards, Cathy.
]]
http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0018.html
[[
Thanks Cathy! This is now fixed as per your suggestion. I also embellished the section a bit more:
https://dvcs.w3.org/hg/dap/rev/389c12d1c49c
Here’s the updated text in context:
https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html#multiple-batteries
]]
http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0025.html
[[
> Thanks Cathy! This is now fixed as per your suggestion. I also embellished the
> section a bit more:
>
> https://dvcs.w3.org/hg/dap/rev/389c12d1c49c
>
Thanks Anssi. One last bit and I'll leave you alone. :-)
At the end of the dischargingTime paragraph, s/sum of the individual batteries/sum of individual discharging times/
Regards, Cathy.
]]
http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0030.html
[[
> At the end of the dischargingTime paragraph, s/sum of the individual batteries/sum of individual discharging times/
Fixed:
https://dvcs.w3.org/hg/dap/rev/c6e758d7a9eb
Thanks,
-Anssi
]]
Display change log