ISSUE-164: Correct default for charging time if unknown in battery

Updated by Anssi, as per your suggestions with minor edits: https://dvcs.w3.org/hg/dap/rev/b84afc1ef2b0

See email http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0000.html

http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0013.html

[[

> I updated the spec as per Tim's and your feedback, which hopefully clarifies
> this.

Yep, that takes care of the inconsistency, which was my major concern.

We still have two paragraphs (above and below the WebIDL) that essentially describe the same thing:
[[
If the implementation is unable to report the battery status information for any of the attributes, the BatteryManager will emulate a fully charged battery by setting all the values to those corresponding values of a fully charged battery. 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.
]]
[[
When the promise is resolved with the BatteryManager object and the implementation is unable to provide any battery information, the default values are set as follows (which is equivalent to a fully charged battery): charging MUST be set to true, chargingTime MUST be set to 0, dischargingTime MUST be set to positive Infinity, and level MUST be set to 1.0.
]]
Can we consolidate those into one paragraph, or is there some subtlety that I'm missing? Each time I read through that part of the spec, I found myself trying to figure out what the second paragraph is telling me that the first wasn't.

Also, with this latest edit, I think we can also s/the implementation is unable to report the remaining charging time while the battery is charging but not full/the implementation is unable to report the remaining charging time/ in the description of the chargingTime. That extra phrase ("while the battery is charging but not full") was added to address my previous feedback, but I think we don't need it anymore. Mounir, WDYT?

Regards, Cathy.

]]

http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0019.html

[[

> Yep, that takes care of the inconsistency, which was my major concern.
>
> Can we consolidate those into one paragraph, or is there some subtlety that I'm missing? Each time I read through that part of the spec, I found myself trying to figure out what the second paragraph is telling me that the first wasn’t.

The text above the IDL reads more like an introduction, while the text below contains the normative assertions.

To clarify this, I moved the introductory-ish text that contains no normative assertions to the Introduction section, and made the other half of the text talking about the defaults a note that I placed below the normative text introducing the concept:

https://dvcs.w3.org/hg/dap/rev/3ab4af97cf9e

Please let us know if this addresses your concern, or whether we should revert back to the previous. To ease the review, here are the updated sections:

https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html#introduction
https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html#the-batterymanager-interface

> Also, with this latest edit, I think we can also s/the implementation is unable to report the remaining charging time while the battery is charging but not full/the implementation is unable to report the remaining charging time/ in the description of the chargingTime. That extra phrase ("while the battery is charging but not full") was added to address my previous feedback, but I think we don't need it anymore. Mounir, WDYT?

Dropped "while the battery is charging but not full”:

https://dvcs.w3.org/hg/dap/rev/eb02dc5983af

Mounir - feel free to revert or make further clarification as needed.
]]

http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0024.html

[[
> To clarify this, I moved the introductory-ish text that contains no normative
> assertions to the Introduction section,

Personally I think it flows better when that paragraph is in the BatteryManager Interface section.

> and made the other half of the text
> talking about the defaults a note that I placed below the normative text
> introducing the concept:
>

This is perfect! Thanks Anssi!

Regards, Cathy.
]]

http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0027.html

[[
> Personally I think it flows better when that paragraph is in the BatteryManager Interface section.

I agree

You can have non-normative text in the normative section to make it clear in context.

regards, Frederick
]]

http://lists.w3.org/Archives/Public/public-device-apis/2014Jul/0029.html

[[
I moved the text back to the BatteryManager interface section:

https://dvcs.w3.org/hg/dap/rev/07b650ad4c98

Thanks,

-Anssi
]]