Re: [sdw] TPAC Breakout: Video metadata for moving objects & sensors on the web (#1194)

Many thanks to all those who participated in the online [breakout session on Monday 26 October 2020](https://www.w3.org/2020/10/TPAC/breakout-schedule.html#video-location) and contributed to the discussion. I've collated the feedback with the session goals and [minutes](https://www.w3.org/2020/10/26-video-location-minutes.html).

**Conclusions**

   1. **Proposed attributes for a moving object** 
   A moving object is defined as _an identified object associated with a sequence of timed locations_. The following calculations are sufficiently lightweight and would impose a minimal processing overhead on the web browser.
      1. _Location_ - interpolated from the sequence of timed locations;
      1. _Distance_ - calculated from the cumulative linear change in location over time;
      1. _Heading_ - calculated from the angular change in location over time;
      1. _Speed_ - calculated from the change in distance over time;
      1. _Description_ - description of the moving object, e.g. a front-facing dashcam.
  
   1. **Proposed attributes for a sensor**
   A sensor is defined as _an identified object associated with a sequence of timed observations_. The following attributes are sufficiently small and would impose a minimal storage overhead on the web browser.
      1. _Value_ - interpolated from the sequence of timed observations;
      1. _Description_ - description of the sensor, e.g. heart rate monitor;
      1. _Units_ - units of measurement, e.g. m/s, rpm;
      1. _Type_ - variable type, i.e. string, number, boolean, object, array;
      1. _Range_ - numeric range (optional), e.g. [-90, 90].

   1. **Other topics discussed**
   The following [issues](https://www.w3.org/2020/10/26-video-location-minutes.html) were raised for further discussion:
      1. _Indoor mapping use case_ - associating video with an indoor space, rather than geospatial co-ordinates;
      1. _Location privacy issues_ - privacy & security implications of sharing video-location data online;
      1. _Video metadata search_ - benefits of using out-of-band metadata with online search engines for privacy, security & bandwidth - see [Area Monitoring](https://w3c.github.io/sdw/proposals/geotagging/webvmt/#areamonitoring) use case for more details;
      1. _Browser API integation_ - how video metadata can be integrated with web browsers & HTML DataCue - see [WICG DataCue](https://github.com/WICG/datacue/) activity for more details;
      1. _Weather data use case_ - associating video with weather data - see [Weather Data in Schema](https://github.com/webvmt/community-group/issues/4) issue for more details;
      1. _Multiple moving objects_ - how more than one moving object can be tracked concurrently with WebVMT - see [TV Sports Coverage](https://w3c.github.io/sdw/proposals/geotagging/webvmt/#tvsportscoverage) use case for more details;
      1. _Image stabilisation use case_ - frame timing accuracy required to sync sensor data for image stabilisation.

-- 
GitHub Notification of comment by rjksmith
Please view or discuss this issue at https://github.com/w3c/sdw/issues/1194#issuecomment-718702993 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 29 October 2020 11:51:30 UTC