From 655428b00e4a5a3f8c9b1d01f9689259dc96a83c Mon Sep 17 00:00:00 2001 From: tomayac Date: Thu, 27 Sep 2018 10:48:20 -0400 Subject: [PATCH 1/5] Add use cases scaffolding --- use-cases.html | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 use-cases.html diff --git a/use-cases.html b/use-cases.html new file mode 100644 index 0000000..6172928 --- /dev/null +++ b/use-cases.html @@ -0,0 +1,80 @@ + + + + Geolocation Sensor API Use Cases + + + + + +
+

+ This document provides a collection of use cases and usage scenarios for + web pages and applications using Geolocation. +

+
+
+

+ This document provides informative background to the + Geolocation Sensor specification. + Comments on the document should be filed as issues at + https://github.com/w3c/geolocation-sensor/issues. +

+
+
+

Terminology

+

+
+
+

Use Cases

+

+
+

+

+
+
+
+

Acknowledgments

+

+
+ + \ No newline at end of file From 69f230d8619e5eb58460319e219ba27b8136a86a Mon Sep 17 00:00:00 2001 From: tomayac Date: Fri, 28 Sep 2018 06:49:42 -0400 Subject: [PATCH 2/5] Slightly rephrase old use cases and add new ones --- use-cases.html | 215 ++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 211 insertions(+), 4 deletions(-) diff --git a/use-cases.html b/use-cases.html index 6172928..862d16e 100644 --- a/use-cases.html +++ b/use-cases.html @@ -62,16 +62,223 @@

Terminology

-

+

+ Use cases can roughly be grouped in four categories: +

+
    +
  • Foreground operations: +
      +
    • Getting a one-off geolocation update.
      • +
    • Getting continuous geolocation updates (aka. geotracking).
      • +
    +
    • +
  • Background operations: +
      +
    • Getting continuous geolocation updates (aka. geotracking).
      • +
    • Getting a one-off geolocation fence alert (aka. geofencing).
      • +
    +
    • +
+

+ Core constraints when obtaining 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: one can trade faster results for lower accuracy and vice versa. + A common theme is to first obtain a rough estimation that then gets refined, + for example based initially on surrounding WiFi signals (which is fast to obtain) + and then eventually based on precise GPS data (which may take some time to find a signal). +

Use Cases

-

+

+ In the following, we list use cases based on the previously defined categories. +

+ +
+

Foreground—One-off geolocation update

+ +
+

Location-tagged status updates in social networking applications

+ +

+ A social network application allows its users to automatically tag their + status updates with location information. It does this by monitoring the + user's position with the Geolocation Sensor API. Each user can control the + granularity of the location information (e.g. city or neighborhood level) + that is shared with the other users. Any user can also track his network + of friends and get real-time updates about their current location. +

+
+ +
+

Find points of interest in the user's area

+

+ Someone visiting a foreign city could access a web application that + allows users to search or browse through a database of tourist + attractions. Using the Geolocation Sensor API, the web application has access to + the user's approximate position and it is therefore able to rank the + search results by proximity to the user's location. +

+
+ +
+ +
+

Foreground—Continuous geolocation updates

+ +
+

Up-to-date local information

+ +

+ A widget-like web application that shows the weather or news that are + relevant to the user's current area can use the Geolocation Sensor API to + register for location updates. If the user's position changes, the widget + can adapt the content accordingly. +

+
+ +
+

Alerts when points of interest are in the user's vicinity

+ +

+ A tour-guide web application can use the Geolocation Sensor API to monitor the + user's position and trigger visual or audio notifications when interesting + places are in the vicinity. An online task management system can trigger + reminders when the user is in the proximity of landmarks that are + associated with certain tasks. +

+
+ +
+

Show the user's position on a map

+ +

+ A user finds themselves in an unfamiliar city area. They want to check their + position so they use their handheld device to navigate to a web-based + mapping application that can pinpoint their exact location on the city map + using the Geolocation Sensor API. They then ask the web application to provide + driving directions from their current position to their desired destination. +

+
+ +
+ +
+

Background—Continuous geolocation updates

+ +
+

Turn-by-turn route navigation

+ +

+ A mapping application can help the user navigate along a route by + providing detailed turn-by-turn directions. The application does this by + registering with the Geolocation Sensor API to receive repeated location updates + of the user's position. These updates are delivered as soon as the + implementing user agent determines that the position of the user has + changed, which allows the application to anticipate any changes of + direction that the user might need to do. + The application can be in the foreground, but likewise can be backgrounded, + for example, when the user turns their device off to save battery + on a long highway route section without side roads. +

+
+ +
+

Tracking sports activity

+ +

+ A web application can track a user's sports activity, for example, + a marathon run or a bicycle race. Therefore, the application does not + need to be on the screen, but would be backgrounded while the user + performs their activity, maybe with their handheld device strapped to their arm. +

+
+ +
+

Annotating content with location information

+ +

+ A group of friends is hiking through the Scottish highlands. Some of + them write short notes and take pictures at various points throughout the + journey and store them using a web application that can work offline on + their handheld devices. Whenever they add new content, the application + automatically tags it with location data from the Geolocation Sensor API (which, + in turn, uses the on-board GPS device). Every time they reach a town or a + village, and they are again within network coverage, the application + automatically uploads their notes and pictures to a popular blogging website, + which uses the geolocation data to construct links that point to a + mapping service. Users who follow the group's trip can click on these + links to see a satellite view of the area where the notes were written and + the pictures were taken. Another example is a life blog where a user + creates content (e.g., images, video, audio) that records their every day + experiences. This content can be automatically annotated with information + such as time, geographic position or even the user's emotional state at + the time of the recording. +

+
+ +
+

Real estate search

+

+ A web application on a handheld device can notify a user of interesting + available properties in a neighborhood they are passing by where the property + fits the user's previously specified search criteria, for example, + 3 bedroom apartments with balcony. +

+
+
+
-

-

+

Background—One-off geolocation fence alert

+ +
+

Retail special offers

+

+ Given their previous consent, a user with a retailer's web application + installed on their handheld device can be alerted about special offers + or location-based coupons when they are in vicinity of a physical presence of the retailer. + Further, the in-store experience can be enriched, for example, the + retailer can let the user know something they have looked at before + is actually available for pick up nearby. +

+
+ +
+

Reminder and to-do applications

+

+ Reminder and to-do web applications can use a geofence to remind the + user to do something when they cross it, for example, to buy milk + when they are near the supermarket. +

+
+ +
+

Travel applications

+

+ Travel applications can show venue specific data like WiFi passwords, + the user's booking confirmation etc. only within geofence boundaries. +

+
+ +
+

Ticketing or booking confirmations

+

+ Ticketing or booking applications can bring up a ticket notification with a QR + or bar code once the user is near the venue of a concert or sports event + or when they reach their rental car counter or similar. +

+
+ +
+

Ride share applications

+

+ Users can be informed if their designated driver reaches a pre-defined pickup point. +

+
+

Acknowledgments

From 87f31c1ca1c50177902cc4c3e0d01e4d05d99740 Mon Sep 17 00:00:00 2001 From: tomayac Date: Mon, 5 Nov 2018 16:35:36 +0100 Subject: [PATCH 3/5] Refine use cases --- use-cases.html | 156 +++++++++++++++++++++++++++---------------------- 1 file changed, 86 insertions(+), 70 deletions(-) diff --git a/use-cases.html b/use-cases.html index 862d16e..deafcd3 100644 --- a/use-cases.html +++ b/use-cases.html @@ -17,6 +17,8 @@ editors: [ { name: "Anssi Kostiainen", company: "Intel", companyURL: "http://www.intel.com/" }, + { name: "Marijn Kruisselbrink", company: "Google", + companyURL: "https://www.google.com/" }, { name: "Thomas Steiner", company: "Google", companyURL: "https://www.google.com/" }, ], @@ -49,7 +51,7 @@

This document provides a collection of use cases and usage scenarios for - web pages and applications using Geolocation. + web pages and applications that rely on Geolocation Sensor data.

@@ -60,54 +62,57 @@ https://github.com/w3c/geolocation-sensor/issues.

-
+

Terminology

- Use cases can roughly be grouped in four categories: + The mentioned use cases can roughly be grouped into four categories:

  • Foreground operations:
    • Getting a one-off geolocation update.
      • -
    • Getting continuous geolocation updates (aka. geotracking).
      • +
    • Getting continuous geolocation updates (aka. foreground geotracking).
  • Background operations:
      -
    • Getting continuous geolocation updates (aka. geotracking).
      • -
    • Getting a one-off geolocation fence alert (aka. geofencing).
      • +
    • Getting continuous geolocation updates (aka. background geotracking).
      • +
    • Getting a one-off geolocation fence alert (aka. background geofencing).

- Core constraints when obtaining gelocation are accuracy + 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: one can trade faster results for lower accuracy and vice versa. - A common theme is to first obtain a rough estimation that then gets refined, +

+

+ A common theme is to first obtain a rough estimation that then gets refined over time, for example based initially on surrounding WiFi signals (which is fast to obtain) and then eventually based on precise GPS data (which may take some time to find a signal).

-
+ +

Use Cases

In the following, we list use cases based on the previously defined categories. + We note that the categories are not mutually exclusive and that 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.

-
+

Foreground—One-off geolocation update

-
-

Location-tagged status updates in social networking applications

- +
+

Locate a user on a map

- A social network application allows its users to automatically tag their - status updates with location information. It does this by monitoring the - user's position with the Geolocation Sensor API. Each user can control the - granularity of the location information (e.g. city or neighborhood level) - that is shared with the other users. Any user can also track his network - of friends and get real-time updates about their current location. + A mapping application can use the Geolocation Sensor API data of a user + to locate them on the map, essentially responding to the question + "Where am I right now?"

@@ -117,14 +122,14 @@

Find points of interest in the user's area

Someone visiting a foreign city could access a web application that allows users to search or browse through a database of tourist attractions. Using the Geolocation Sensor API, the web application has access to - the user's approximate position and it is therefore able to rank the + the user's approximate current position and is therefore able to rank the search results by proximity to the user's location.

-
+

Foreground—Continuous geolocation updates

@@ -142,7 +147,7 @@

Up-to-date local information

Alerts when points of interest are in the user's vicinity

- A tour-guide web application can use the Geolocation Sensor API to monitor the + A tour guide web application can use the Geolocation Sensor API to monitor the user's position and trigger visual or audio notifications when interesting places are in the vicinity. An online task management system can trigger reminders when the user is in the proximity of landmarks that are @@ -154,19 +159,34 @@

Alerts when points of interest are in the user's vicinity

Show the user's position on a map

- A user finds themselves in an unfamiliar city area. They want to check their + A user finds themselves in an unfamiliar area. They want to check their position so they use their handheld device to navigate to a web-based - mapping application that can pinpoint their exact location on the city map + mapping application that can pinpoint their exact location on the map using the Geolocation Sensor API. They then ask the web application to provide - driving directions from their current position to their desired destination. + driving directions from their current position to their desired destination, + essentially responding to the question "Where am I going?".

-
+

Background—Continuous geolocation updates

+
+

Location-tagged status updates in social networking applications

+ +

+ A social networking application allows its users to automatically tag their + status updates with location information. It does this by monitoring the + user's position with the Geolocation Sensor API. Each user can control the + granularity of the location information (e.g., city or neighborhood level) + that is shared with the other users. Any user can also see their network + of friends and get real-time updates about their current location, + granted they have opted in to their location data being shared. +

+
+

Turn-by-turn route navigation

@@ -184,7 +204,7 @@

Turn-by-turn route navigation

-
+

Tracking sports activity

@@ -195,56 +215,21 @@

Tracking sports activity

-
-

Annotating content with location information

- -

- A group of friends is hiking through the Scottish highlands. Some of - them write short notes and take pictures at various points throughout the - journey and store them using a web application that can work offline on - their handheld devices. Whenever they add new content, the application - automatically tags it with location data from the Geolocation Sensor API (which, - in turn, uses the on-board GPS device). Every time they reach a town or a - village, and they are again within network coverage, the application - automatically uploads their notes and pictures to a popular blogging website, - which uses the geolocation data to construct links that point to a - mapping service. Users who follow the group's trip can click on these - links to see a satellite view of the area where the notes were written and - the pictures were taken. Another example is a life blog where a user - creates content (e.g., images, video, audio) that records their every day - experiences. This content can be automatically annotated with information - such as time, geographic position or even the user's emotional state at - the time of the recording. -

-
- -
+

Real estate search

A web application on a handheld device can notify a user of interesting available properties in a neighborhood they are passing by where the property fits the user's previously specified search criteria, for example, - 3 bedroom apartments with balcony. + 3 bedroom apartments with balcony.

-
+

Background—One-off geolocation fence alert

-
-

Retail special offers

-

- Given their previous consent, a user with a retailer's web application - installed on their handheld device can be alerted about special offers - or location-based coupons when they are in vicinity of a physical presence of the retailer. - Further, the in-store experience can be enriched, for example, the - retailer can let the user know something they have looked at before - is actually available for pick up nearby. -

-
- -
+

Reminder and to-do applications

Reminder and to-do web applications can use a geofence to remind the @@ -253,7 +238,7 @@

Reminder and to-do applications

-
+

Travel applications

Travel applications can show venue specific data like WiFi passwords, @@ -261,7 +246,7 @@

Travel applications

-
+

Ticketing or booking confirmations

Ticketing or booking applications can bring up a ticket notification with a QR @@ -270,18 +255,49 @@

Ticketing or booking confirmations

-
+

Ride share applications

Users can be informed if their designated driver reaches a pre-defined pickup point.

+ +
+

Retail special offers

+

+ Given their previous consent, a user with a retailer's web application + installed on their handheld device can be alerted about special offers + or location-based coupons when they are in vicinity of a physical presence of the retailer. + Further, the in-store experience can be enriched, for example, the + retailer can let the user know something they have looked at before + is actually available for pick up nearby. +

+
+

Acknowledgments

-

+

+ The use cases mentioned in this document are partly based on previous work in + [GEOLOCATION]. +

+ +
+

References

+
+
+ [GEOLOCATION] +
+
+ Geolocation API Specification 2nd Edition, + W3C Recommendation 8 November 2016 (GitHub reference added 31 January 2018). + Andrei Popescu, Editor. World Wide Web Consortium. See https://www.w3.org/TR/geolocation-API/. +
+
+
+ \ No newline at end of file From 4b3271dfea7bf4d4bd72387fbe9e996549a9ae37 Mon Sep 17 00:00:00 2001 From: tomayac Date: Thu, 8 Nov 2018 14:19:47 +0100 Subject: [PATCH 4/5] Add use cases directly to spec --- compile.sh | 0 index.bs | 135 ++++++++++++++++++++++ use-cases.html | 303 ------------------------------------------------- 3 files changed, 135 insertions(+), 303 deletions(-) mode change 100644 => 100755 compile.sh delete mode 100644 use-cases.html diff --git a/compile.sh b/compile.sh old mode 100644 new mode 100755 diff --git a/index.bs b/index.bs index 3ca0c9a..1f92f40 100644 --- a/index.bs +++ b/index.bs @@ -301,6 +301,141 @@ Abstract Operations {#abstract-operations} 1. Return |geo|. +Use Cases {#use-cases} +========= + +## Categorization of use cases ## {#use-cases-categorization} + +The mentioned use cases can roughly be grouped into four categories: + +* **Foreground** operations: + * Getting a **one-off geolocation update**. + * Getting **continuous geolocation updates** (*aka.* foreground geotracking). +* **Background** operations: + * Getting **continuous geolocation updates** (*aka.* background geotracking). + * Getting a **one-off geolocation fence alert** (*aka.* background geofencing). + +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: +one can trade faster results for lower accuracy and vice versa. + +A common theme is to first obtain a rough estimation that then gets refined over time, +for example based initially on surrounding WiFi signals (which is fast to obtain) +and then eventually based on precise GPS data (which may take some time to find a signal). + +In the following, we list use cases based on the previously defined categories. + +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. + +## Foreground—One-off geolocation update ## {#use-cases-foreground-one-off} + +### Locate a user on a map ### {#use-case-locate-a-user-on-a-map} + +A mapping application can use the Geolocation Sensor API data of a user to locate them +on the map, essentially responding to the question "Where am I right now?" + +### Find points of interest in the user's area ### {#use-case-find-points-of-interest-in-the-users-area} + +Someone visiting a foreign city could access a web application that allows users +to search or browse through a database of tourist attractions. Using the Geolocation Sensor API, +the web application has access to the user's approximate current position +and is therefore able to rank the search results by proximity to the user's location. + +## Foreground—Continuous geolocation updates ## {#use-cases-foreground-continuous} + +### Up-to-date local information ### {#use-case-up-to-date-local-information} + +A widget-like web application that shows the weather or news that are relevant +to the user's current area can use the Geolocation Sensor API to register for location updates. +If the user's position changes, the widget can adapt the content accordingly. + +### Alerts when points of interest are in the user's vicinity ### {#use-case-alerts-when-points-of-interest-are-in-the-users-vicinity} + +A tour guide web application can use the Geolocation Sensor API to monitor the user's position +and trigger visual or audio notifications when interesting places are in the vicinity. +An online task management system can trigger reminders when the user is in the proximity +of landmarks that are associated with certain tasks. +This use case assumes active usage of the application in the foreground. + +### Show the user's position on a map ### {#use-case-show-the-users-position-on-a-map} + +A user finds themselves in an unfamiliar area. They want to check their position +so they use their handheld device to navigate to a web-based mapping application +that can pinpoint their exact location on the map using the Geolocation Sensor API. +They then ask the web application to provide driving directions from their current position +to their desired destination, essentially responding to the question "Where am I going?". + +## Background—Continuous geolocation updates ## {#use-cases-background-continuous} + +### Location-tagged status updates in social networking applications ### {#use-case-location-tagged-status-updates-in-social-networking-applications} + +A social networking application allows its users to automatically tag their status updates with +location information. It does this by monitoring the user's position with the Geolocation Sensor API. +Each user can control the granularity of the location information (e.g., city or neighborhood level) +that is shared with the other users. Any user can also see their network of friends +and get real-time updates about their current location, +granted they have opted in to their location data being shared. +This use case intentionally conflates foreground location tagging and background location sharing. + +### Turn-by-turn route navigation ### {#use-case-turn-by-turn-route-navigation} + +A mapping application can help the user navigate along a routeby providing detailed turn-by-turn directions. +The application does this by registering with the Geolocation Sensor API to receive +repeated location updates of the user's position. These updates are delivered as soon as the implementing +user agent determines that the position of the user has changed, which allows the application +to anticipate any changes of direction that the user might need to do. +The application can be in the foreground, but likewise can be backgrounded, for example, +when the user turns their device off to save battery on a long highway route section without side roads. + +### Tracking sports activity ### {#use-case-tracking-sports-activity} + +A web application can track a user's sports activity, for example, a marathon run or a bicycle race. +Therefore, the application does not need to be on the screen, but would be backgrounded +while the user performs their activity, maybe with their handheld device strapped to their arm. + +### Real estate search ### {#use-case-real-estate-search} + +A web application on a handheld device can notify a user of interesting available properties +in a neighborhood they are passing by where the property fits the user's previously specified search criteria, +for example, 3 bedroom apartments with balcony. +This is based on the assumption that the number of possible matches is high, +that is, impossible to realize with geofences as the amount of required geofences would be too high. + +## Background—One-off geolocation fence alert ## {#use-cases-background-geofence} + +### Reminder and to-do applications ### {#use-case-reminder-and-todo-applications} + +Reminder and to-do web applications can use a geofence to remind the user to do something when they cross it, +for example, to buy milk when they are near the supermarket. + +### Travel applications ### {#use-case-travel-applications} + +Travel applications can show venue specific data like WiFi passwords, +the user's booking confirmation etc. only within geofence boundaries. + +### Ticketing or booking confirmations ### {#use-case-ticketing-or-booking-confirmations} + +Ticketing or booking applications can bring up a ticket notification with a QR or bar code +once the user is near the venue of a concert or sports event or when they reach their rental car counter or similar. + +### Ride share applications ### {#use-case-ride-share-applications} + +Users can be informed if their designated driver reaches a pre-defined pickup point. + +### Retail special offers ### {#use-case-retail-special-offers} + +Given their previous consent, a user with a retailer's web application installed on their handheld device +can be alerted about special offers or location-based coupons when they are +in vicinity of a physical presence of the retailer. Further, the in-store experience can be enriched, +for example, the retailer can let the user know something they have looked at before is actually available for pick up nearby. + Acknowledgements {#acknowledgements} ================ diff --git a/use-cases.html b/use-cases.html deleted file mode 100644 index deafcd3..0000000 --- a/use-cases.html +++ /dev/null @@ -1,303 +0,0 @@ - - - - Geolocation Sensor API Use Cases - - - - - -
-

- This document provides a collection of use cases and usage scenarios for - web pages and applications that rely on Geolocation Sensor data. -

-
-
-

- This document provides informative background to the - Geolocation Sensor specification. - Comments on the document should be filed as issues at - https://github.com/w3c/geolocation-sensor/issues. -

-
-
-

Terminology

-

- The mentioned use cases can roughly be grouped into four categories: -

-
    -
  • Foreground operations: -
      -
    • Getting a one-off geolocation update.
      • -
    • Getting continuous geolocation updates (aka. foreground geotracking).
      • -
    -
    • -
  • Background operations: -
      -
    • Getting continuous geolocation updates (aka. background geotracking).
      • -
    • Getting a one-off geolocation fence alert (aka. background geofencing).
      • -
    -
    • -
-

- 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: one can trade faster results for lower accuracy and vice versa. -

-

- A common theme is to first obtain a rough estimation that then gets refined over time, - for example based initially on surrounding WiFi signals (which is fast to obtain) - and then eventually based on precise GPS data (which may take some time to find a signal). -

-
- -
-

Use Cases

-

- In the following, we list use cases based on the previously defined categories. - We note that the categories are not mutually exclusive and that 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. -

- -
-

Foreground—One-off geolocation update

- -
-

Locate a user on a map

-

- A mapping application can use the Geolocation Sensor API data of a user - to locate them on the map, essentially responding to the question - "Where am I right now?" -

-
- -
-

Find points of interest in the user's area

-

- Someone visiting a foreign city could access a web application that - allows users to search or browse through a database of tourist - attractions. Using the Geolocation Sensor API, the web application has access to - the user's approximate current position and is therefore able to rank the - search results by proximity to the user's location. -

-
- -
- -
-

Foreground—Continuous geolocation updates

- -
-

Up-to-date local information

- -

- A widget-like web application that shows the weather or news that are - relevant to the user's current area can use the Geolocation Sensor API to - register for location updates. If the user's position changes, the widget - can adapt the content accordingly. -

-
- -
-

Alerts when points of interest are in the user's vicinity

- -

- A tour guide web application can use the Geolocation Sensor API to monitor the - user's position and trigger visual or audio notifications when interesting - places are in the vicinity. An online task management system can trigger - reminders when the user is in the proximity of landmarks that are - associated with certain tasks. -

-
- -
-

Show the user's position on a map

- -

- A user finds themselves in an unfamiliar area. They want to check their - position so they use their handheld device to navigate to a web-based - mapping application that can pinpoint their exact location on the map - using the Geolocation Sensor API. They then ask the web application to provide - driving directions from their current position to their desired destination, - essentially responding to the question "Where am I going?". -

-
- -
- -
-

Background—Continuous geolocation updates

- -
-

Location-tagged status updates in social networking applications

- -

- A social networking application allows its users to automatically tag their - status updates with location information. It does this by monitoring the - user's position with the Geolocation Sensor API. Each user can control the - granularity of the location information (e.g., city or neighborhood level) - that is shared with the other users. Any user can also see their network - of friends and get real-time updates about their current location, - granted they have opted in to their location data being shared. -

-
- -
-

Turn-by-turn route navigation

- -

- A mapping application can help the user navigate along a route by - providing detailed turn-by-turn directions. The application does this by - registering with the Geolocation Sensor API to receive repeated location updates - of the user's position. These updates are delivered as soon as the - implementing user agent determines that the position of the user has - changed, which allows the application to anticipate any changes of - direction that the user might need to do. - The application can be in the foreground, but likewise can be backgrounded, - for example, when the user turns their device off to save battery - on a long highway route section without side roads. -

-
- -
-

Tracking sports activity

- -

- A web application can track a user's sports activity, for example, - a marathon run or a bicycle race. Therefore, the application does not - need to be on the screen, but would be backgrounded while the user - performs their activity, maybe with their handheld device strapped to their arm. -

-
- -
-

Real estate search

-

- A web application on a handheld device can notify a user of interesting - available properties in a neighborhood they are passing by where the property - fits the user's previously specified search criteria, for example, - 3 bedroom apartments with balcony. -

-
-
- -
-

Background—One-off geolocation fence alert

- -
-

Reminder and to-do applications

-

- Reminder and to-do web applications can use a geofence to remind the - user to do something when they cross it, for example, to buy milk - when they are near the supermarket. -

-
- -
-

Travel applications

-

- Travel applications can show venue specific data like WiFi passwords, - the user's booking confirmation etc. only within geofence boundaries. -

-
- -
-

Ticketing or booking confirmations

-

- Ticketing or booking applications can bring up a ticket notification with a QR - or bar code once the user is near the venue of a concert or sports event - or when they reach their rental car counter or similar. -

-
- -
-

Ride share applications

-

- Users can be informed if their designated driver reaches a pre-defined pickup point. -

-
- -
-

Retail special offers

-

- Given their previous consent, a user with a retailer's web application - installed on their handheld device can be alerted about special offers - or location-based coupons when they are in vicinity of a physical presence of the retailer. - Further, the in-store experience can be enriched, for example, the - retailer can let the user know something they have looked at before - is actually available for pick up nearby. -

-
- -
-
- -
-

Acknowledgments

-

- The use cases mentioned in this document are partly based on previous work in - [GEOLOCATION]. -

-
- -
-

References

-
-
- [GEOLOCATION] -
-
- Geolocation API Specification 2nd Edition, - W3C Recommendation 8 November 2016 (GitHub reference added 31 January 2018). - Andrei Popescu, Editor. World Wide Web Consortium. See https://www.w3.org/TR/geolocation-API/. -
-
-
- - - \ No newline at end of file From 1ad4fb1853ad57aa307a9bc12d53d53a26c8f66d Mon Sep 17 00:00:00 2001 From: Thomas Steiner Date: Mon, 12 Nov 2018 09:56:41 -0800 Subject: [PATCH 5/5] Add Marijn Kruisselbrink as editor --- index.bs | 1 + 1 file changed, 1 insertion(+) diff --git a/index.bs b/index.bs index 1f92f40..fc153a2 100644 --- a/index.bs +++ b/index.bs @@ -7,6 +7,7 @@ TR: https://www.w3.org/TR/geolocation-sensor/ Shortname: geolocation-sensor Editor: Anssi Kostiainen 41974, Intel Corporation, https://intel.com/ Editor: Thomas Steiner 44965, Google Inc., https://google.com/ +Editor: Marijn Kruisselbrink, Google Inc., https://google.com/ Group: dap Abstract: This specification defines the {{GeolocationSensor}} interface for obtaining