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

[wot-poc] minutes - 28 July 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 10 Aug 2020 17:19:33 +0900
Message-ID: <87imdq29re.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/07/28-wot-poc-minutes.html

also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                                WoT PoC

28 Jul 2020

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/PoC_WebConf#28_July_2020

Attendees

   Present
          Kaz_Ashimura, Michael_McCool, Jennifer_Lin,
          Daivid_Ezell, Kunihiko_Toumura

   Regrets
          Tomoaki_Mizushima

   Chair
          McCool

   Scribe
          kaz

Contents

     * [3]Topics
         1. [4]Prev minutes
         2. [5]Geolocation PoC
         3. [6]Use cases
         4. [7]Horizontal/Vertical
         5. [8]AOB?
     * [9]Summary of Action Items
     * [10]Summary of Resolutions
     __________________________________________________________

   <scribe> scribenick: kaz

Prev minutes

   [11]July-7

     [11] https://www.w3.org/2020/07/07-wot-poc-minutes.html

   McCool: (goes through the minutes)
   ... looks fine
   ... approved

   [12]July-14

     [12] https://www.w3.org/2020/07/14-wot-poc-minutes.html

   McCool: demo during the main call?
   ... let's focus on the use case first

   Jennifer: can ask Philip about what can be shown

   McCool: we can wait
   ... minutes themselves are OK

   Jennifer: yeah

   McCool: approve

   [13]July-21

     [13] https://www.w3.org/2020/07/21-wot-poc-minutes.html

   McCool: not exactly a use case but we should think about MQTT
   over WebSocket
   ... we're doing discovery discussions
   ... first draft to be published in September
   ... any issues with the minutes?

   (none)

   McCool: accepted

Geolocation PoC

   McCool: it's not too specific to Singapore
   ... we can collaborate on actual devices/services
   ... GPS module, etc., to be considered
   ... a possible implementation might be having TD on the server
   side and the client as a location sensor just upload the
   geolocation information to that
   ... geolocation stuff is generic and seems to be open to share

   David: there might be turnaround issue
   ... phones may stay on changing

   McCool: could use webhook events, etc.
   ... geolocation use case makes us consider diverse settings
   ... would be useful to go through the use cases
   ... regarding the usage of QR codes, that's related to
   discovery as well

   <McCool> [14]https://www.gibtsnicht.de/loc.html

     [14] https://www.gibtsnicht.de/loc.html

   McCool: wondering about functionalities for retails

   David: geofencing
   ... you can detect certain location
   ... and steady update on your location

   McCool: Jennifer's use case implies issue on installation
   ... temporary installation for certain devices
   ... maybe by scanning QR codes
   ... (crates a new issue to capture the points)
   ... phone s a geolocation device
   ... may want to set it up as a client
   ... that "calls in" data rather than acting as a server
   ... may also provide check-in functionality, i.e., scan a QR
   code or read a bluetooth beacon
   ... this provides access to the phone's geolocation API which
   includes more than just GPS

   Kaz: technically the client and the server could work with each
   other collaboratively like the speech recognition service
   ... for example, pre-processing part could be done on the
   client side
   ... and the integration/complicated search could be done on the
   server side

   <McCool> [15]Issue 37 - Geolocation use case extensions

     [15] https://github.com/w3c/wot-usecases/issues/37

   McCool: might be able to get feedback from EdgeX as well
   ... when would be the event?

   David: August 12

Use cases

   McCool: ok to put the smart city dashboard?

   Jennifer: yes

   McCool: let's generate the description by the use case call on
   Thursday

   <McCool>
   [16]https://github.com/mmccool/wot-usecases/blob/edge-computing
   /USE-CASES/edge-computing.md

     [16] https://github.com/mmccool/wot-usecases/blob/edge-computing/USE-CASES/edge-computing.md

   McCool: let's think about edge computing use case now

   [17]Issue 18

     [17] https://github.com/w3c/wot-usecases/issues/18

   McCool: this (edge computing) should be extended and
   generalized to "public health monitoring" and include variants
   such as fever tracking, social distancing, mask detection, etc.

   [18]McCool's comments to Issue 18

     [18] https://github.com/w3c/wot-usecases/issues/18#issuecomment-665021098

Horizontal/Vertical

   McCool: there are two kinds of use cases
   ... vertical ones like agriculture
   ... and horizontal ones like digital twins
   ... would see what kind of requirements are there for verticals
   within the horizontal use cases
   ... need to go through the use case descriptions
   ... for example, digital twin could be applied to the smart
   city use case

   <McCool> see also autodesk's digital twin technology for
   simulation

   <McCool> traffic, water flow etc.

   [19]autodesk site

     [19] https://www.autodesk.com/

   <jennifer_>
   [20]https://www.autodesk.com.sg/products/infraworks/

     [20] https://www.autodesk.com.sg/products/infraworks/

   Jennifer: popularly used for construction, etc.

AOB?

   McCool: anything for the next call?

   Jennifer: we should make contribution to the use case
   description

   McCool: ok

   Jennifer: we could look at existing geolocation projects

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [21]scribe.perl version ([22]CVS log)
    $Date: 2020/07/29 04:27:31 $

     [21] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [22] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 10 August 2020 08:19:41 UTC

This archive was generated by hypermail 2.4.0 : Monday, 10 August 2020 08:19:41 UTC