Geolocation use case extensions

[mmccool]

• Phone as a geolocation device

  • May want to set it up as a client that "calls in" data rather than acting as a server - "Thing as a client"
  • This provides access to the phone's geolocation API which includes more than just GPS
  • For Smart City POC, probably based on Android
  • May also provide check-in functionality, i.e. scan a QR code or read a bluetooth beacon, then combine that code with geolocation and register it with a service

• Check-in

  • Installation of portable devices (eg SPOTON)
  • Delivery confirmation; fuel delivery, package delivery
  • Geofencing; delivery unlocking, actions only permitted in certain locations

• Non-Smart-City use cases w/ additional requirements

  • Agriculture - relative depth
  • Logistics/transportation - dynamic location information (not just "portable")

[mmccool]

Note that geolocation is currently mentioned in a Smart City use case (see https://github.com/w3c/wot-usecases/blob/master/USE-CASES/processed/smartcity-geolocation.md, although this has now been merged into the main document) but relates to other verticals as well, eg logistics, transportation, agriculture, etc. and some of these have additional requirements (e.g. relative depth for agriculture, room connectivity for smart building, etc).

[mmccool]

I have labelled this with security-privacy because location information is especially privacy sensitive, although really we need to look at ALL the use cases, and in other cases I just labelled issues that are about security or privacy directly.