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

Re: [battery] proposed additional edit for attribute defaults

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Tue, 1 Jul 2014 09:31:05 +0000
To: Frederick Hirsch <w3c@fjhirsch.com>
CC: W3C Device APIs WG <public-device-apis@w3.org>, "timvolodine@google.com" <timvolodine@google.com>, Mounir Lamouri <mounir@lamouri.fr>, "cathy.chan@nokia.com" <cathy.chan@nokia.com>
Message-ID: <242DC98E-F8B3-4167-9005-38C78E2CD845@intel.com>
Hi Frederick,

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

Thanks,

-Anssi
Received on Tuesday, 1 July 2014 09:31:42 UTC

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