This specification defines an API that lets webapps setup geographic boundaries around specific locations and then receive notifications when the hosting device enters or leaves those areas.
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 https://www.w3.org/TR/.
This document has been published as a Working Group Note to reflect the fact that the Geolocation Working Group is no longer progressing it arong the W3C Recommendation Track. A record of discussion relating to this specification can be found in the Geolocation Working Group's email archive. The email list was email@example.com.
There are no changes from the previous Working Draft.
The Geolocation Working Group was chartered to define a secure and privacy-sensitive interface for using client-side location information in location-aware Web applications. The group published an update to the Geolocation API specification as a Recommendation. However, the work on the Geofencing API specification did not complete.
Publication as a Working Group Note 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 March 2017 W3C Process Document.