28 Jul 2020



Kaz_Ashimura, Michael_McCool, Jennifer_Lin, Daivid_Ezell, Kunihiko_Toumura


<scribe> scribenick: kaz

Prev minutes


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


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


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?


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> 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> Issue 37 - Geolocation use case extensions

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> https://github.com/mmccool/wot-usecases/blob/edge-computing/USE-CASES/edge-computing.md

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

Issue 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.

McCool's comments to Issue 18


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.

autodesk site

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

Jennifer: popularly used for construction, etc.


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


Summary of Action Items

Summary of Resolutions

[End of minutes]

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