W3C home > Mailing lists > Public > public-wot-ig@w3.org > July 2020

[wot-poc] minutes - 7 July 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Wed, 29 Jul 2020 13:31:18 +0900
Message-ID: <87h7trlz6x.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/07/07-wot-poc-minutes.html

also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                                WoT PoC

07 Jul 2020

Attendees

   Present
          Kaz_Ashimura, Jennifer_Lin, Michael_McCool,
          Kunihiko_Toumura, Tomoaki_Mizushima

   Regrets

   Chair
          McCool

   Scribe
          kaz

Contents

     * [2]Topics
         1. [3]Quick update
         2. [4]Prev minutes
         3. [5]geolocation
     * [6]Summary of Action Items
     * [7]Summary of Resolutions
     __________________________________________________________

   <McCool> todo - robotics followup, use cases for remote
   sensing, water management

Quick update

   <jennifer> SPOTON were featured in this OECD spotlight article:
   [8]https://trends.oecd-opsi.org/trend-reports/innovative-covid-
   19-solutions/

      [8] https://trends.oecd-opsi.org/trend-reports/innovative-covid-19-solutions/

   <jennifer> If you click on the "Download" button and search for
   "SPOTON" in the pdf.

   <jennifer>
   [9]https://trends.oecd-opsi.org/wp-content/uploads/2020/07/OECD
   _2020-Report-Book-v2.pdf (Or here)

      [9] https://trends.oecd-opsi.org/wp-content/uploads/2020/07/OECD_2020-Report-Book-v2.pdf

   <jennifer> SPOTON is GovTech's intended PoC for WoT.

   <jennifer> SPOTON already is in production, but it doesn't
   fully support WoT yet

Prev minutes

   [10]June-9

     [10] https://www.w3.org/2020/06/09-wot-poc-minutes.html

   Jennifer: wondering about the geolocation information

   McCool: put updates on geolocation to the use cases
   ... anyway, ok with the minutes themselves?

   Jennifer: nothing sensitive or anything

   McCool: accepted

geolocation

   <McCool> [11]https://github.com/w3c/wot-architecture/issues/456

     [11] https://github.com/w3c/wot-architecture/issues/456

   McCool: there was general discussion on geolocation
   ... also accuracy of geolocation information
   ... SSN standard defines accuracy, precision and resolution

   [12]SSN

     [12] https://www.w3.org/TR/vocab-ssn/

   McCool: also Basic Geo Vocabulary by Dan Brickley

   [13]Basic Geo Vocabulary

     [13] https://www.w3.org/2003/01/geo/

   McCool: and World Geodetic System

   [14]World Geodetic System - Wikipedia

     [14] https://en.wikipedia.org/wiki/World_Geodetic_System

   <McCool>
   [15]https://www.w3.org/TR/geolocation-API/#coordinates_interfac
   e

     [15] https://www.w3.org/TR/geolocation-API/#coordinates_interface

   McCool: Coordinates interface definition from the Geolocation
   API Spec 2nd Edition
   ... we have an API definition for geolocation here
   ... however, need to talk with the DAS WG guys

   [16]https://w3c.github.io/geolocation-sensor/#geolocationsensor
   -interface Generic Sensor API - Geolocation sensor

     [16] https://w3c.github.io/geolocation-sensor/#geolocationsensor-interface

   [17]ISO119-2:2016 Geographic information

     [17] https://www.iso.org/obp/ui/fr/#iso:std:iso:ts:19159:-2:ed-1:v1:en

   Kaz: some updates about geolocation api (by DASWG) and
   geolocation information accuracy (by ISO) above

   McCool: ok

   <McCool>
   [18]https://w3c.github.io/hr-time/#dom-domhighrestimestamp

     [18] https://w3c.github.io/hr-time/#dom-domhighrestimestamp

   [19]Issue 456

     [19] https://github.com/w3c/wot-architecture/issues/456

   McCool: possible issue on high resolution time stamp

   Kaz: yeah, related issue on who would manage the clock

   McCool: (adds comments to Issue 456)

   [20]comment 1

     [20] https://github.com/w3c/wot-architecture/issues/456#issuecomment-654826943

   [21]comment 2

     [21] https://github.com/w3c/wot-architecture/issues/456#issuecomment-654827710

   [22]comment 3

     [22] https://github.com/w3c/wot-architecture/issues/456#issuecomment-654828354

   [23]comment 4

     [23] https://github.com/w3c/wot-architecture/issues/456#issuecomment-654830604

   McCool: good to have joint discussion with the DASWG during
   TPAC

   Kaz: definitely

   McCool: would like to polish the geolocation use case
   description
   ... will create a separate use case about time and accuracy
   ... note that the goal here is not re-inventing the wheel
   ... geolocation information itself, time, accuracy and SSN
   ... SSN is kind of complicated and need to think about how to
   use it
   ... also how to map the geolocation information from the
   geolocation api with the smart city dashboard

   Jennifer: yeah

   McCool: another use case I'm interested is the mapping
   ... even for static sensor for measurement as well

   Kaz: we need to think about "Web browser as a WoT Servient" for
   that purpose as well

   McCool: yeah
   ... let's discuss mapping during the next meeting

   Jennifer: the eventual goal should include reusing the existing
   map services like Google Maps as well

   McCool: ok, let's defer that to the next meeting
   ... data visualization is another viewpoint
   ... also what the possible limitation with iotschema, etc.

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [24]scribe.perl version ([25]CVS log)
    $Date: 2020/07/07 13:28:20 $

     [24] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [25] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 29 July 2020 04:31:27 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 29 July 2020 04:31:28 UTC