Note: Investigate any geolocation-specific security and privacy considerations that are not
-mitigated by the Generic Sensor API [GENERIC-SENSOR], and define geolocation-specific
+
Note: Investigate any geolocation-specific security and privacy considerations that are not
+mitigated by the Generic Sensor API [GENERIC-SENSOR], and define geolocation-specific
mitigations.
4. Model
The term geolocation refers to the real-world geographic location of the
-hosting device represented in geographic coordinates [WGS84].
-
Note: An implementation can use multiple location information sources to acquire geolocation information, and this specification is agnostic with respect
+hosting device represented in geographic coordinates [WGS84].
+
Note: An implementation can use multiple location information sources to acquire geolocation information, and this specification is agnostic with respect
to those sources.
- This section extends the automation section defined in the Generic Sensor API [GENERIC-SENSOR] to provide mocking information about the geolocation of the hosting device for the purposes of
-testing a user agent’s implementation of GeolocationSensor API.
-
The mentioned use cases can roughly be grouped into four categories:
@@ -975,7 +1089,7 @@
Getting a one-off geolocation fence alert (aka. background geofencing).
-
Note: Only the foreground operations were possible with [GEOLOCATION-API],
+
Note: Only the foreground operations were possible with [GEOLOCATION-API],
the background operations are completely novel.
Core constraints when obtaining the gelocation are accuracy (how close to the
actual position of the user is the determined position) and latency (how long does the user want to wait for a result). Both are tradeoffs:
@@ -984,7 +1098,7 @@
In the following, we list use cases based on the previously defined categories.
-
Note: The categories are not mutually exclusive and overlaps exist.
+
Note: The categories are not mutually exclusive and overlaps exist.
A task might start in the foreground, then continue in the background (for example,
while the user quickly responds to an incoming email),
and then eventually terminate in the foreground when the user multitasks back.