Fwd: Battery Status API returns to W3C Candidate Recommendation (Call for Implementations)

Hi,

As discussed over the past few days, the Battery Status API has been
republished as a Candidate Recommendation, to take into account the
substantive change we brought to it, and the ongoing discussion on
possible further mitigations (or changes to the existing ones) for
potential abuse of that API.

Regards,

Dom


-------- Forwarded Message --------
Subject: Battery Status API returns to W3C Candidate Recommendation
(Call for  Implementations)
Resent-Date: Thu, 07 Jul 2016 13:23:55 +0000
Resent-From: w3c-ac-members@w3.org
Date: Thu, 7 Jul 2016 21:23:40 +0800
From: Xueyuan Jia <xueyuan@w3.org>


Dear Advisory Committee Representative,
Chairs,

Battery Status API has now returned to W3C Candidate Recommendation:
https://www.w3.org/TR/2016/CR-battery-status-20160707/

In March 2016, the Director approved the publication of the Battery
Status API as a Proposed Recommendation and invited the Advisory
Committee to review the specification:
https://lists.w3.org/Archives/Member/w3c-ac-members/2016JanMar/0053.html

While that review did not raise objections, a bug was separately
reported on the specification, leading to a minor but substantive change
to the specification. Such a change, per the W3C Process Document [1],
requires the specification to return to Candidate Recommendation.

In addition, some concerns were recently raised [2] about potential
privacy-invasive usage of the information provided by the Battery Status
API, which the Working Group wants to review in more depth and possibly
address with new informative mitigation strategies.

The Working Group is particularly interested in feedback from
implementors on the privacy concerns mentioned in [2].

The Device and Sensors Working Group already knows of two
implementations that satisfy its implementation criteria:
https://w3c.github.io/test-results/battery-status/20160621.html
based on the following test suite:
http://w3c-test.org/battery-status/

The group expects to have collected enough feedback to request
transition to Proposed Recommendation by September 1st 2016 by email to
its (archived) public mailing list <public-device-apis@w3.org>.

Patent disclosures relevant to this specification may be found on the
Device and Sensors Working Group's patent disclosure page in conformance
with W3C policy:
http://www.w3.org/2004/01/pp-impl/43696/status

This Call for Implementations follows section 6.4 "Candidate
Recommendation" of the W3C Process Document:
http://www.w3.org/2015/Process-20150901/#candidate-rec

Thank you,

For Tim Berners-Lee, W3C Director, and
Philipp Hoschka, Ubiquitous Web Domain Lead;
Dominique Hazael-Massieux, Device and Sensors Working Group Staff Contact;
Xueyuan Jia, W3C Marketing & Communications


[1] https://www.w3.org/2015/Process-20150901/#rec-pr
[2]
https://lists.w3.org/Archives/Public/public-device-apis/2016Jul/0000.html

==========================
Quoting from
Battery Status API
W3C Candidate Recommendation 07 July 2016

This version:
    http://www.w3.org/TR/2016/CR-battery-status-20160707/
Latest published version:
    http://www.w3.org/TR/battery-status/

Abstract:
This specification defines an API that provides information about the
battery status of the hosting device.

Status of This Document:
This section describes the status of this document at the time of its
publication. Other documents may supersede this document. A list of
current W3C publications and the latest revision of this technical
report can be found in the W3C technical reports index at
http://www.w3.org/TR/.

A minor but substantive change has been made to the Battery Status API
since the W3C Proposed Recommendation of March 2016 (diff), with the
association of the Battery Manager promise to the Navigator object
rather than the browsing context. In addition, concerns about possible
privacy-invasive usage of the Battery Status API have been raised, which
the Working Group intends to review to determine if additional
mitigation strategies are needed. This specification is thus returning
to Candidate Recommendation status.

The updated implementation report of the API shows all features have
been implemented by two independent deployed browsers, meeting the
primary CR exit criteria, so the Working Group intends to proceed to
Proposed Recommendation once the substantive change and the privacy
concerns have been sufficiently reviewed, no sooner than 01 September 2016.

This document was published by the Device and Sensors Working Group as a
Candidate Recommendation. This document is intended to become a W3C
Recommendation. If you wish to make comments regarding this document,
please send them to public-device-apis@w3.org (subscribe, archives). W3C
publishes a Candidate Recommendation to indicate that the document is
believed to be stable and to encourage implementation by the developer
community. This Candidate Recommendation is expected to advance to
Proposed Recommendation no earlier than 01 September 2016. All comments
are welcome.

Publication as a Candidate Recommendation does not imply endorsement by
the W3C Membership. This is a draft document and may be updated,
replaced or obsoleted by other documents at any time. It is
inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February
2004 W3C Patent Policy. W3C maintains a public list of any patent
disclosures made in connection with the deliverables of the group; that
page also includes instructions for disclosing a patent. An individual
who has actual knowledge of a patent which the individual believes
contains Essential Claim(s) must disclose the information in accordance
with section 6 of the W3C Patent Policy.

This document is governed by the 1 September 2015 W3C Process Document.
==========================

Received on Thursday, 7 July 2016 13:30:49 UTC