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

[gv-collab] minutes - 24 March 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 27 Apr 2020 13:04:50 +0900
Message-ID: <87lfmhvajh.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/03/24-govtech-minutes.html

also as text below.

Thanks a lot for taking the minutes, Michael McCool!

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                             Govtech Collab

24 Mar 2020

Attendees

   Present
          Kaz_Ashimura, Daniel_Peintner, Jennifer_Lin,
          Michael_Lagally, Michael_McCool, Ege_Korkan,
          Kunihiko_Toumura, Sebastian_Kaebisch

   Regrets

   Chair
          McCool

   Scribe
          kaz, McCool

Contents

     * [2]Topics
         1. [3]Agenda for today
     * [4]Summary of Action Items
     * [5]Summary of Resolutions
     __________________________________________________________

Agenda for today

   <inserted> scribenick: kaz

   McCool: use cases like fleet management

   Jennifer: answering questions on node-wot

   <inserted> scribenick: McCool

   McCool: and public health monitoring use case

   <mlagally> Lagally: onboarding requirements

   McCool: edgex proof-of-concept

   Ege: node-wot issues and requirements

   <inserted> scribenick: kaz

   Jennifer: note that Philip Tran from Govtech would like to
   support various security approaches

   <inserted> scribenick: McCool

   Kaz: let's also think about how to use this call
   ... could clarify Govtech's needs here but should consider we
   discuss the detail of the extracted use cases, requirements,
   questions, etc., during the other WoT calls. For example, use
   case discussion could be done during the Architecture call, td
   topics in td call...

   McCool: maybe best to use this call for node-wot, deal with use
   cases in arch call

   Lagally: use this call for sync between govtech's needs and wot
   groups
   ... management of issues and use cases

   McCool: node-wot concerns a lot of people, not just govtech, so
   it should probably be more open

   Lagally: easy onboard of lots of devices; security requirements
   ... what kind of architecture did you have in mind; onboarding
   to what? do you have a diagram, etc?
   ... something that you could share?

   Jennifer: we have an agency with a lot of buildings around
   singapore
   ... they want to buy a lot of thermal sensors, look for people
   with fevers
   ... each sensor needs an id, a location, number of detections,
   etc
   ... and need to send images if there is a detection, as well as
   a notification
   ... but needs to be managed well since used with a map, and
   used to make health decisions
   ... identify hot spots, let people know where to stay away
   from; but also particular stores, etc.
   ... looking at wanting to purchase a solution rather than build
   it, because need it NOW
   ... also need to do filtering based on location

   <Zakim> dape, you wanted to leaning away means using still WoT
   standard

   Daniel: do understand why Philip is leaning away from node-wot
   ... feedback on both standard and implementation is beneficial
   ... so even if you do not use it for this, we still want to
   capture the feedback

   Jennifer: using node-wot as a prototyping tool right now

   McCool: is there another project with a longer horizon we
   should be looking at?

   Jennifer: right now the health monitoring issue is high
   priority, so...

   Lagally: you mentioned buildings with sensors; what are they
   measuring

   Jennifer: right now, thermal sensors at entrances
   ... if a fever is detected (temp above a threshold) will
   trigger an alert
   ... id of thermal sensor, number of faces with fever -> action
   to send email or sms
   ... aggregate that data
   ... management wants to be able to look at a map or at a
   building
   ... there are both agencies (govt) and companies
   ... ex: before it got shut down on friday, mosques wanted some
   sensors...

   scribenick: kaz

   McCool: (creates another use case MD file to capture the use
   case)

   Kaz: it depends on the need of the service, e.g., just want to
   pick up people with fever or AI-based analysis on the cloud
   side
   ... btw, I believe we definitely need timecode as part of the
   data, so it should be added :)

   <Ege> [6]https://github.com/eclipse/thingweb.node-wot

      [6] https://github.com/eclipse/thingweb.node-wot

   Ege: happy to join node-wot related calls but the discussions
   should go to the node-wot repo above as well

   McCool: let's see a good slot for the possible node-wot call
   ... let's discuss that during the main call

   <kaz> +1

   Jennifer any specific requests for the future agenda?

   McCool: would like to continue to talk about use cases

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [7]scribe.perl version 1.154 ([8]CVS log)
    $Date: 2020/04/27 03:59:03 $

      [7] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
      [8] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 27 April 2020 04:04:38 UTC

This archive was generated by hypermail 2.4.0 : Monday, 27 April 2020 04:04:39 UTC