12:51:40 <RRSAgent> RRSAgent has joined #wot-uc
12:51:40 <RRSAgent> logging to https://www.w3.org/2021/11/16-wot-uc-irc
12:57:54 <kaz> meeting: WoT Use Cases
12:58:01 <kaz> present+ Kaz_Ashimura
12:58:08 <kaz> chair: Lagally
13:01:30 <dezell> dezell has joined #wot-uc
13:01:38 <kaz> present+ Tetsushi_Matsuda
13:02:09 <kaz> present+ Jack_Dickinson
13:02:17 <dezell> present+ David_Ezell
13:02:22 <Mizushima> Mizushima has joined #wot-uc
13:02:45 <kaz> present+ Michael_Lagally
13:02:52 <kaz> present+ Tomoaki_Mizushima
13:05:16 <mlagally_> mlagally_ has joined #wot-uc
13:08:07 <matsuda> matsuda has joined #wot-uc
13:08:16 <kaz> scribenick: kaz
13:08:18 <kaz> topic: Minutes
13:08:26 <kaz> -> https://www.w3.org/2021/11/09-wot-uc-minutes.html Nov-9
13:08:43 <kaz> ml: (goes through the minutes)
13:09:34 <kaz> ... owners of issues marked as "publication-2.0" should work on their assigned issues
13:10:15 <kaz> -> https://github.com/w3c/wot-usecases/issues?q=is%3Aissue+is%3Aopen+label%3Apublication-2.0 Issues marked as "publication-2.0"
13:10:29 <kaz> ml: any objections for the minutes?
13:10:33 <kaz> (none; approved)
13:10:47 <kaz> topic: PRs
13:11:06 <kaz> subtopic: PR 152
13:11:15 <kaz> -> https://github.com/w3c/wot-usecases/pull/152 PR 152 - Please merge the description of ECHONET Consortium
13:11:23 <kaz> ml: (reviews the PR)
13:12:15 <kaz> -> https://pr-preview.s3.amazonaws.com/matsu200722/wot-usecases/pull/152.html#echonet preview
13:12:20 <kaz> ml: looks good
13:12:44 <kaz> ... but need to fix the style since it's included in "Editor's Note"
13:14:35 <kaz> kaz: let's simply remove [[class="ednote"]]
13:14:46 <kaz> ml: let's merge the PR itself
13:14:54 <kaz> ... and fix the style later
13:14:58 <kaz> (merged)
13:15:23 <kaz> subtopic: Conexxus use case priority
13:15:30 <kaz> jd: can explain
13:16:10 <kaz> ... (shows "Conexxus IoT User Stories Priorities")
13:16:22 <kaz> ... [Top Device User Stories]
13:16:39 <kaz> ... (priority with 7 topics)
13:16:48 <kaz> ... priority list here
13:17:15 <kaz> ... customer experience, security, safety, ...
13:17:35 <kaz> s/... /... 1. allStopButton/
13:17:39 <kaz> ... 2. doorSensor
13:17:52 <kaz> ... 3. freezer, kitchenRefrigerater
13:17:58 <kaz> de: sense temperature
13:18:20 <kaz> jd: refrigeration and food safety
13:18:41 <kaz> ... 4. restroom device
13:18:52 <kaz> ... 5. lighting, canopyLightingControl
13:19:06 <kaz> ... EV charging, etc., as well
13:19:21 <kaz> ... both for customer experience and security
13:19:35 <kaz> ... self service from customer's viewpoint
13:19:56 <kaz> ... 6. fountainDrinkIceMachine
13:20:05 <kaz> ... 7. camera
13:20:12 <kaz> ... accessibility too
13:20:28 <kaz> de: a couple of things here
13:20:41 <kaz> if we look at doorSensor and freezer
13:20:48 <kaz> s/if/... if/
13:21:12 <kaz> ... would like to see abstraction by WoT
13:21:50 <kaz> ... you could see how low/high the temperature
13:22:39 <kaz> ... Coca Cola company working on smart vending machine
13:23:09 <kaz> ... same things for fountainDrinkIceMachine
13:23:19 <kaz> ... where WoT can play key roles
13:23:33 <ryuichi> ryuichi has joined #wot-uc
13:23:35 <kaz> ... camera for multi-views
13:23:58 <kaz> ... two doorSensors monitored by a camera, for example
13:24:11 <kaz> q+
13:24:24 <kaz> ... very much play&play
13:24:51 <kaz> ... would like to use camera for handle the affordance for doorSensors
13:25:01 <kaz> jd: [Device comparison]
13:25:41 <kaz> ... Devices vs topics (IoT Primary, IoT Secondar, Supply Chain, Operations, ecurity, Food Safety, Experience)
13:26:23 <kaz> ... camera conceptually used
13:26:34 <kaz> ... nice summary of focus
13:26:35 <kaz> q?
13:27:18 <kaz> de: IoT interface for camera is a secondary interface
13:27:47 <kaz> ... primary role is making images
13:28:05 <kaz> ... AI systems work for product identification
13:28:27 <kaz> present+ Ryuichi_Matsukura
13:28:46 <kaz> ... you know what Sony video camera does
13:29:01 <kaz> ... camera in our phones also does something like that
13:29:11 <kaz> ... value of abstraction
13:29:26 <kaz> ... handing our camera stream as a blackbox
13:29:44 <kaz> jd: store flow traffic
13:29:54 <kaz> ... using the camera for store desing
13:30:04 <kaz> ... product placing
13:30:38 <kaz> ... we tried to take the data and share the power
13:30:55 <kaz> ... once the Thing is available
13:31:50 <kaz> de: is this what you want?
13:31:54 <kaz> ml: definitely
13:31:59 <kaz> ... a couple of questions
13:32:00 <kaz> q?
13:33:08 <kaz> ack k
13:33:27 <kaz> kaz: the point here is orchestration
13:33:31 <kaz> ... of multiple devices
13:33:49 <kaz> ... would be great if you could generate concrete description about the combination of devices
13:34:26 <kaz> ... e.g., allStopButton, doorSensor and freezer plus camera
13:34:44 <kaz> de: (shows Use Case description)
13:35:12 <kaz> s/Use/one of the Use/
13:35:17 <kaz> s/n)/ns)/
13:35:39 <kaz> ml: horizontal vs vertical
13:35:50 <kaz> ... it seems camera is used for horizontal purposes
13:36:30 <kaz> ... we can add a sub section for retail use cases within the Use Cases document
13:37:24 <kaz> ... primary devices can be included in the Vertical use cases part
13:38:02 <kaz> jd: distinction for supply chains
13:38:18 <kaz> ml: camera can be used for Smart Cities use cases as well
13:40:59 <kaz> de: cameras take pictures
13:41:37 <kaz> ... is an IoT-backend device
13:41:56 <kaz> ... and you can have vertical devices with it
13:42:47 <kaz> ... we've generated these user stories
13:42:50 <kaz> q+
13:43:14 <kaz> ... do we need to generate any more additional documents?
13:43:32 <kaz> ml: we can identify requirements/gaps based on the existing use case descriptions
13:43:41 <kaz> ... e.g., two gaps so far
13:43:50 <kaz> ... orchestration, etc.
13:44:01 <kaz> ... also handling video streams
13:44:21 <kaz> present+ Sebastian_Kaebisch
13:44:52 <kaz> sk: one example of taking pictures from camera
13:45:11 <kaz> ... streaming video is related to event handling
13:45:21 <kaz> ... initialize the video stream, etc.
13:45:39 <kaz> ml: subprotocol to handle it?
13:45:42 <kaz> sk: yeah
13:46:06 <kaz> ... what kind of technology is used for your camera
13:46:19 <kaz> ... any specific protocol or data format there?
13:46:49 <kaz> ... thought McCool was using a camera for plugfests
13:46:58 <kaz> q?
13:47:16 <kaz> ml: yeah, discussion with McCool would make sense
13:47:25 <kaz> ... a horizontal use case would be nice
13:47:45 <kaz> ... let's look into the horizontal use case
13:47:47 <kaz> q?
13:48:02 <kaz> https://github.com/w3c/wot-usecases/blob/main/USE-CASES/retail/Retail-indoor-camera.md
13:50:35 <kaz> kaz: or maybe we could think about how to apply video camera to the other existing vertical use cases like "All Stop Button"
13:50:42 <kaz> de: interesting
13:51:20 <kaz> jd: possibly microwave sensor, etc., as well
13:52:08 <kaz> s/interesting/interesting to have stop button capability by detecting the gesture from the video camera/
13:52:25 <kaz> ml: (shows the minutes from Nov-2 meeting)
13:52:53 <kaz> -> https://www.w3.org/2021/11/02-wot-uc-minutes.html Nov-2
13:53:17 <kaz> ml: we have another category for multimodal interface
13:53:51 <kaz> de: let me check the terminology of "orchestration"
13:54:26 <kaz> ml: multiple simple devices combined for some capability
13:54:56 <kaz> ... we don't have clear definition yet, though
13:55:06 <kaz> q+
13:55:22 <kaz> de: if you have a door sensor and temperature sensor
13:55:31 <kaz> s/temp/a temp/
13:55:59 <kaz> ... you have two separate devices for a common use case?
13:56:02 <kaz> ml: yes
13:57:08 <kaz> de: we should look at aggregation of the two different kind of devices
13:57:11 <kaz> ml: yes
13:57:22 <kaz> ... let's see the aggregation scenario
13:58:00 <kaz> sk: consume different TDs attached to multiple devices at once
13:58:10 <kaz> q+
13:58:23 <kaz> ... Ege was working on system description
13:59:11 <kaz> ... maybe Ege can talk about that
13:59:27 <kaz> de: interesting
13:59:37 <kaz> ml: ok
13:59:47 <kaz> ... meanwhile please work on your assigned issues
13:59:57 <kaz> ... thanks a lot for your updates, David and Jack
14:02:01 <kaz> kaz: we can look into the existing use cases like multimodal integration and also ECHONET use case which include aggregation of multiple devices
14:02:02 <kaz> ack k
14:02:04 <mlagally_> q?
14:03:12 <kaz> [adjourned]
14:03:17 <kaz> rrsagent, make log public
14:03:23 <kaz> rrsagent, draft minutes
14:03:23 <RRSAgent> I have made the request to generate https://www.w3.org/2021/11/16-wot-uc-minutes.html kaz
14:08:19 <kaz> s/[adjourned]//
14:08:32 <kaz> topic: Industry 4.0 use case
14:08:41 <kaz> ml: we'll continue the discussion next week
14:09:26 <kaz> sk: Kaz, would be nice if you could put your comment you mentioned during the previous call as an Issue for the use case
14:09:29 <kaz> kaz: will do
14:09:32 <kaz> [adjourned]
14:09:36 <kaz> rrsagent, draft minutes
14:09:36 <RRSAgent> I have made the request to generate https://www.w3.org/2021/11/16-wot-uc-minutes.html kaz
14:24:36 <Joshue108> Joshue108 has joined #wot-uc
16:21:44 <Zakim> Zakim has left #wot-uc