- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jul 2020 11:17:42 +0000
- To: public-device-apis-log@w3.org
The System Wake Lock API has been worked on in the DAS WG as part of the Wake Lock API [since 2015](https://www.w3.org/TR/2015/WD-wake-lock-20150212/). It has never been a WICG deliverable, so the title of this issue is misleading ("Leave System WakeLock API in WICG").
The DAS WG recorded a consensus [1] to split the Wake Lock API into two separate DAS WG deliverables in Feb 2020:
>The rationale for the split is to allow the screen wake lock subset of the spec that has strong use cases, implementation experience, and web developer support to advance along the W3C Rec Track on its own merits, while allow the system wake lock to be further developed in parallel before its advancement.
That CfC passed with no concerns and no new information has been brought to the group's attention that would support the objector's proposal.
Also, we feel the objector fails to clearly articulate the value of reversing to WICG, especially considering the expertise for this problem space has been in the DAS WG since 2015 with many of the W3C member organizations committed to the DAS WG and this deliverable.
The DAS WG believes moving this work off of the standards track would be considered harmful.
[1] https://lists.w3.org/Archives/Public/public-device-apis/2020Feb/0011.html
--
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/101#issuecomment-654783959 using your GitHub account
Received on Tuesday, 7 July 2020 11:17:47 UTC