search

w3c / geofencing-api

13 stars 9 forks source link

Add use cases to specification #15

Open gmandyam opened 9 years ago

gmandyam commented 9 years ago

See [1]. [1] http://lists.w3.org/Archives/Public/public-geolocation/2015Jun/0003.html

gmandyam commented 8 years ago

Cannot seem to create a pull request, so am including here (respec.js).

A geofence is a virtual fence that circumscribes a geographical area. In its simplest form, a geofence can be described by a centroid and a radius (this defines a 2 dimensional circular geofence). However, more complex geofences are possible (e.g. polygonal boundaries). This document provides sample scenarios and derived requirements for a geofencing feature in the context of the W3C Gelocation API [[!GEOLOCATION-API]]. 

Scenarios
---------

### Alerts when points of interest are in the user's vicinity (derived from [[!GEOLOCATION-API]])

A tour-guide Web application can use the geofencing-enhanced Geolocation 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.

### Asset Tracking

Web technologies are finding a place in mobile devices used for asset or property tracking.  A mobile tag attached to an asset could leverage
a web-based geofencing solution to trigger alerts when it enters or leaves a geofenced area.  For instance, commercial merchandise can be
tracked in a warehouse, or construction equipment can be tracked in a building site.  

### Mobile Marketing

Internet advertising is often measured by click-through rates, i.e. The click-through rate is the number of unique instances where an 
user ineracts with the ad ("clicks" on it)  divided by the total number of ad impressions (the times an advertisement was served).
Physical click-through is possible with geofencing.  In this case, a retailer can determine if an end user has actually entered an establishment after
viewing an ad.

Requirements
------------

### R1:  The Geolocation API must provide a way for the application to set a geofence around a centroid.

### R2:  The Geolocation API must provide a way for the application to perform a one-shot query as to whether the device is inside or outside of a geofence defined around a centroid.

### R3:  The Geolocation API must provide a way for the application to register to receive notifications when the device breaches a geofence, including information as to whether the device is entering or leaving the geofenced area.

mkruisselbrink commented 8 years ago

I hope it's not me converting the spec from respec to bikeshed that made creating the pull request a problem?

But either way, I'd be happy to manually merge this, although I'm not sure where exactly this text would best fit within the spec? Is the idea that these would be new sections at the end of the spec similar to those in the geolocation api spec?

gmandyam commented 8 years ago

Yes - adding a new section at the end of the spec would work.