- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Mon, 22 Jun 2020 08:11:17 +0000
- To: W3C Devices and Sensors WG <public-device-apis@w3.org>
Hi All, This CfC passed with no concerns. [To clarify the relationship between the Geolocation API and Geolocation Sensor specification: DAS WG is chartered to maintain the Geolocation API. This maintenance commitment means no new features are added to the Geolocation API. DAS WG also has the Geolocation Sensor spec as its deliverable. New feature development happens in the Geolocation Sensor specification. The two specifications coexist.] Thanks, -Anssi (DAS WG co-chair) > On 11. Jun 2020, at 22.47, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote: > > Hi DAS WG, > > This is a Call for Consensus to publish the Geolocation API as an Amended Recommendation. > > Please review the latest Editor's Draft [1] (change summary at [2]). > > If you have any concerns with this plan, please respond on this list by 18 June 2020. Silence is considered consent. > > Rationale: Since the Recommendation published 8 November 2016 [3], the spec has been adopted by DAS WG and subsequently hardened for security and privacy in line with the group's maintenance commitment. These changes are substantive, but add no new features. > > (As a W3C Process quirk, we'll publish a revised CR and PR before we get to publish an Amended Recommendation.) > > Thanks, > > -Anssi (DAS WG co-chair) > > [1] https://w3c.github.io/geolocation-api/ > [2] https://github.com/w3c/geolocation-api/issues/42 > [3] https://www.w3.org/TR/geolocation-API/
Received on Monday, 22 June 2020 08:11:37 UTC