Fwd: Request for Comments Wake Lock API; deadline Sept 30 (anticipating CR transition)

> Begin forwarded message:
> 
> From: Frederick Hirsch <w3c@fjhirsch.com>
> Subject: Request for Comments Wake Lock API; deadline Sept 30 (anticipating CR transition)
> Date: September 2, 2017 at 7:36:03 PM EDT
> To: Christine Runnegar <runnegar@isoc.org>, tjwhalen@google.com, hillbrad@fb.com, dveditz@mozilla.com
> Cc: chairs@w3.org, Dominique Hazael-Massieux <dom@w3.org>, Fuqiao Xue <xfq@w3.org>, Андрей Логвинов <alogvinov@yandex-team.ru>
> 
> Dear Chairs of PING, WebAppSec WG, Web Security IG and other interested groups:
> 
> The Device & Sensors Working Group has made updates to the Wake Lock API on our way to Candidate Recommendation status:
> 
> https://www.w3.org/TR/wake-lock/
> 
> We are seeking review from PING, WebAppSec WG and Web Security IG before transitioning to Candidate Recommendation. Reviews from other groups are also naturally welcome.
> 
> We had a previous wide review about a year ago in July 2016  [1] and have received feedback and made a number of changes since then. These include support for system wake lock use cases,  addressing feedback from the TAG [2], updates to promise handling, changes to clarify state transitions when the device is manually 
> locked, updates to the security and privacy considerations (including update to self-review questionnaire [3]) and  editorial fixes.
> 
> We would appreciate to receive your feedback before the end of September; the preferred method for feedback is to file issues in our github repository:
> 
> https://github.com/w3c/wake-lock/issues
> 
> (alternatively, send a mail to our public mailing list  public-device-apis@w3.org with a subject prefixed with [wake-lock] )
> 
> Thank you
> 
> regards, Frederick 
> 
> Frederick Hirsch
> Chair, W3C Devices and Sensors WG (DAS)
> 
> [1] https://lists.w3.org/Archives/Member/chairs/2016JulSep/0015.html
> 
> [2] https://github.com/w3c/wake-lock/issues/85
> 
> [3] https://github.com/w3c/wake-lock/issues/89
> 
>