From 87f31c1ca1c50177902cc4c3e0d01e4d05d99740 Mon Sep 17 00:00:00 2001 From: tomayac Date: Mon, 5 Nov 2018 16:35:36 +0100 Subject: [PATCH] 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