- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Fri, 27 Aug 2021 09:47:27 +0000
- To: W3C Devices and Sensors WG <public-device-apis@w3.org>, Fuqiao Xue <xfq@w3.org>
- CC: "public-privacy (W3C mailing list)" <public-privacy@w3.org>
Hi All, This CfC ended with no concerns. Fuqiao - please work with the editor to prepare a transition request. Thanks, -Anssi > On 12. Aug 2021, at 18.32, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote: > > Hi DAS WG, > FYI PING, > > This is a Call for Consensus to publish the Geolocation API as a Candidate Recommendation (CR). > > Please review the latest Working Draft [1] and reply to public-device-apis@w3.org by 26 August 2021 if you have any concerns with this publication plan. > > Silence is considered consent. > > Since the First Public Working Draft (FPWD) published 27 May 2021, the API has received the following normative changes: > > • Return 0 when watchPosition() errors #100 > • Callback with error if doc is not fully active #97 > • Gracefully handle documents that are not fully active #90 > • Add "geolocation task queue" #87 > > For details, please refer to the change log [2]. > > The spec has received wide review [3] at FPWD time. (The above-mentioned normative changes since FPWD are implementation details that bring the spec inline with implementations and don't change or invalidate the wide reviews received at FPWD time.) > > The rationale for the rapid progression along the Rec Track is to update the outdated 7 Sep 2010 CR of this API by modernizing it to the extend possible while retaining compatibility with existing implementations. > > Thanks, > > -Anssi (DAS WG co-chair) > > > [1] https://www.w3.org/TR/geolocation/ > > [2] https://www.w3.org/TR/geolocation/#change-log > > [3] https://github.com/w3c/geolocation-api/issues/43
Received on Friday, 27 August 2021 09:47:51 UTC