Meeting minutes
Minutes
Lagally: (goes through the minutes)
… owners of issues marked as "publication-2.0" should work on their assigned issues
Issues marked as "publication-2.0"
Lagally: any objections for the minutes?
(none; approved)
PRs
PR 152
PR 152 - Please merge the description of ECHONET Consortium
Lagally: (reviews the PR)
Lagally: looks good
… but need to fix the style since it's included in "Editor's Note"
Kaz: let's simply remove [[class="ednote"]]
Lagally: let's merge the PR itself
… and fix the style later
(merged)
Conexxus use case priority
Jack: can explain
… (shows "Conexxus IoT User Stories Priorities")
… [Top Device User Stories]
… (priority with 7 topics)
… priority list here
… 1. allStopButtoncustomer experience, security, safety, ...
… 2. doorSensor
… 3. freezer, kitchenRefrigerater
David: sense temperature
Jack: refrigeration and food safety
… 4. restroom device
… 5. lighting, canopyLightingControl
… EV charging, etc., as well
… both for customer experience and security
… self service from customer's viewpoint
… 6. fountainDrinkIceMachine
… 7. camera
… accessibility too
David: a couple of things here
… if we look at doorSensor and freezer
… would like to see abstraction by WoT
… you could see how low/high the temperature
… Coca Cola company working on smart vending machine
… same things for fountainDrinkIceMachine
… where WoT can play key roles
… camera for multi-views
… two doorSensors monitored by a camera, for example
… very much play&play
… would like to use camera for handle the affordance for doorSensors
Jack: [Device comparison]
… Devices vs topics (IoT Primary, IoT Secondar, Supply Chain, Operations, ecurity, Food Safety, Experience)
… camera conceptually used
… nice summary of focus
David: IoT interface for camera is a secondary interface
… primary role is making images
… AI systems work for product identification
… you know what Sony video camera does
… camera in our phones also does something like that
… value of abstraction
… handing our camera stream as a blackbox
Jack: store flow traffic
… using the camera for store design
… product placing
… we tried to take the data and share the power
… once the Thing is available
David: is this what you want?
Lagally: definitely
… a couple of questions
Kaz: the point here is orchestration
… of multiple devices
… would be great if you could generate concrete description about the combination of devices
… e.g., allStopButton, doorSensor and freezer plus camera
David: (shows one of the Use Case descriptions)
Lagally: horizontal vs vertical
… it seems camera is used for horizontal purposes
… we can add a sub section for retail use cases within the Use Cases document
… primary devices can be included in the Vertical use cases part
Jack: distinction for supply chains
Lagally: camera can be used for Smart Cities use cases as well
David: cameras take pictures
… is an IoT-backend device
… and you can have vertical devices with it
… we've generated these user stories
… do we need to generate any more additional documents?
Lagally: we can identify requirements/gaps based on the existing use case descriptions
… e.g., two gaps so far
… orchestration, etc.
… also handling video streams
Sebastian: one example of taking pictures from camera
… streaming video is related to event handling
… initialize the video stream, etc.
Lagally: subprotocol to handle it?
Sebastian: yeah
… what kind of technology is used for your camera
… any specific protocol or data format there?
… thought McCool was using a camera for plugfests
Lagally: yeah, discussion with McCool would make sense
… a horizontal use case would be nice
… let's look into the horizontal use case
https://
Kaz: or maybe we could think about how to apply video camera to the other existing vertical use cases like "All Stop Button"
David: interesting to have stop button capability by detecting the gesture from the video camera
Jack: possibly microwave sensor, etc., as well
Lagally: (shows the minutes from Nov-2 meeting)
Lagally: we have another category for multimodal interface
David: let me check the terminology of "orchestration"
Lagally: multiple simple devices combined for some capability
… we don't have clear definition yet, though
David: if you have a door sensor and a temperature sensor
… you have two separate devices for a common use case?
Lagally: yes
David: we should look at aggregation of the two different kind of devices
Lagally: yes
… let's see the aggregation scenario
Sebastian: consume different TDs attached to multiple devices at once
… Ege was working on system description
… maybe Ege can talk about that
David: interesting
Lagally: ok
… meanwhile please work on your assigned issues
… thanks a lot for your updates, David and Jack
Kaz: we can look into the existing use cases like multimodal integration and also ECHONET use case which include aggregation of multiple devices
Industry 4.0 use case
Lagally: we'll continue the discussion next week
Sebastian: Kaz, would be nice if you could put your comment you mentioned during the previous call as an Issue for the use case
Kaz: will do
[adjourned]