12:00:42 RRSAgent has joined #wot-uc 12:00:42 logging to https://www.w3.org/2022/03/22-wot-uc-irc 12:01:59 Mizushima has joined #wot-uc 12:04:12 meeting: WoT Use Cases 12:04:28 present+ Kaz_Ashimura, Michael_McCool, Tomoaki_Mizushima 12:05:08 present+ Michael_Lagally 12:07:16 scribenick: McCool 12:07:25 mlagally has joined #wot-uc 12:08:11 mm: for requirements, propose we focus in the short term on discovery and profiles 12:08:19 ... since we have to write explainers anyway 12:08:45 ml: I have written up a table (CSV) to get coverage of various requirements 12:09:58 mm: so the columns here are deliverables, right? 12:12:32 mm: so each element of this table is a set of requirements, sorted into buckets 12:15:41 ml: suggest we do a high-level interation first, then drill down into details later once we find gaps. 12:15:52 mm: doing this by columns might be easier 12:17:37 https://github.com/w3c/wot-usecases/blob/main/USE-CASES/coverage.csv 12:18:41 mm: ok, I have added this as an agenda item for Discovery 12:19:10 q+ 12:20:02 kaz: for editor's call, Seb did mention he was generating a coverage note in issue #1350 12:20:18 ... are you planning to update note based on that? 12:20:20 -> https://github.com/w3c/wot-thing-description/issues/1350#issuecomment-1012958553 Sebastian's basic check results 12:21:50 s/are you planning to update note based on that?/My understanding was you wanted Sebastian to update the coverage.csv itself based on this kind of check results, though./ 12:23:55 ml: ok, I see there is a list; but this information needs to be boiled down a bit 12:24:03 mm: what we really want to identify are gaps 12:24:55 mm: maybe we need categories like "ok, partial, and (null)" (e.g. empty means there is a gap) 12:26:38 ml: three-way makes sense, if use "gap" explicitly it is clear is has been filled in 12:32:24 present+ David_Ezell 12:35:27 ml: (goes over use cases in TD comment above) 12:39:57 ml: let's look at the retail use case since David Ezell is here 12:41:05 -> https://www.w3.org/TR/2022/NOTE-wot-usecases-20220307/#retail latest WoT Use Cases and requirement 12:41:38 sebastiankaebisch has joined #wot-uc 12:42:44 mm: in retail demos we were talking about simple automations 12:43:16 de: not so much about configuring individual devices, but about connecting devices in a certain way 12:46:29 mm: also think that "simplicity of use" is an overriding requirement 12:47:32 ryuichi has joined #wot-uc 12:47:35 ... but also reliability, and "just works" 12:49:11 ... also, I think out-of-the-box interop and control are at opposite ends 12:49:35 ... in some use cases, e.g. smart building setup, an engineer may *want* control over all the details 12:49:56 ... in retail, though, I want defaults to take care of the annoying details 12:51:05 ml: for virtual thing, integration of multiple devices -> automation rules 12:51:27 rrsagent, make log public 12:51:31 rrsagent, draft minutes 12:51:31 I have made the request to generate https://www.w3.org/2022/03/22-wot-uc-minutes.html kaz 12:51:58 chair: Lagally 12:52:00 rrsagent, draft minutes 12:52:00 I have made the request to generate https://www.w3.org/2022/03/22-wot-uc-minutes.html kaz 12:52:02 ml: we have found some gaps, can also look at individual use cases that have called out specific gaps 12:52:23 i/for requirements/topic: Use Cases coverage/ 12:56:22 mm: I think time series also shows up 12:56:41 ml: yes, in agriculture 12:57:36 mm: also battery level, units 12:57:42 ml: relative values 12:59:16 mm: eg. depth, and calibration 12:59:27 ml: precision, etc. are also importanbt 13:00:20 sebastiankaebisch has joined #wot-uc 13:00:42 sebastiankaebisch has joined #wot-uc 13:02:37 ml: let's remind people in main call 13:02:39 mm: sure 13:02:44 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf main call agenda 13:05:04 s|https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf|https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#23_March_2022| 13:06:38 [adjourned] 13:06:38 rrsagent, draft minutes 13:06:38 I have made the request to generate https://www.w3.org/2022/03/22-wot-uc-minutes.html kaz 13:34:08 sebastiankaebisch has joined #wot-uc 13:38:09 sebastiankaebisch has joined #wot-uc 14:31:30 sebastiankaebisch has joined #wot-uc 14:31:54 sebastiankaebisch has joined #wot-uc 14:41:41 sebastiankaebisch has joined #wot-uc 14:50:41 Zakim has left #wot-uc 16:13:41 sebastiankaebisch has joined #wot-uc 16:40:22 sebastiankaebisch has joined #wot-uc 16:51:43 sebastiankaebisch has joined #wot-uc 16:52:32 sebastia_ has joined #wot-uc 18:11:26 sebastiankaebisch has joined #wot-uc