12:25:49 RRSAgent has joined #wot-uc 12:25:49 logging to https://www.w3.org/2021/05/04-wot-uc-irc 12:26:08 meeting: WoT Use Cases - publication status check 12:26:33 kaz has changed the topic to: WoT Use Cases 12:27:13 topic: Status check 12:27:15 mlagally__ has joined #wot-uc 12:27:41 present+ Kaz_Ashimura, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima 12:28:15 Agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf 12:29:30 topic: Recent updates 12:29:43 s/updates/editorial updates/ 12:30:29 subtopic: PR 126 12:30:40 -> https://github.com/w3c/wot-usecases/pull/126 PR 126 - Editorial fixes for issue 119 12:30:47 ml: just fixed typos 12:31:07 subtopic: PR 128 12:31:17 -> https://github.com/w3c/wot-usecases/pull/128 PR 128 - list contributors and respective companies in acknowledgement section 12:31:42 ml: updates for the acknowledgement section 12:32:28 mm: maybe should have the list in alphabetical order? 12:32:36 ml: yes, it's already so 12:33:36 q+ 12:34:52 ack 12:35:18 kaz: as confirmed the other day, we should not include non-Member companies' names for each Use Case entry 12:35:29 -> https://w3c.github.io/wot-usecases/index.html#smart-building-things 2.3.3 Automated Smart Building Management 12:36:08 mm: or rather we can simply remove all the companies' names from each Use Case description to be consistent 12:36:10 ml: right 12:36:59 mm: we can list multiple authors concatenated with ", " (=A, B, C) 12:38:10 rrsagent, make log public 12:38:16 rrsagent, draft minutes 12:38:16 I have made the request to generate https://www.w3.org/2021/05/04-wot-uc-minutes.html kaz 12:39:09 subtopic: PR 129 12:39:27 -> https://github.com/w3c/wot-usecases/pull/129 PR 129 - cleanup references 12:39:40 ml: updated the reference section 12:39:42 mm: ok 12:40:05 subtopic: Issue 117 12:40:13 s/Issue/PR/ 12:40:27 -> https://github.com/w3c/wot-usecases/pull/117 PR 117 - WIP: Add liaisons 12:40:47 ml: let's leave it out at the moment 12:40:49 mm: ok 12:41:09 topic: Issues 12:41:12 -> https://github.com/w3c/wot-usecases/issues 12:41:21 s/issues/issues remaining issues/ 12:41:44 subtopic: Issue 84 12:41:55 -> https://github.com/w3c/wot-usecases/issues/84 Issue 84 - Security and requirements questionnaire 12:42:00 mm: we did look into it 12:42:17 ... may have cross-TF issues 12:42:46 ml: asking for a table indicating which concrete implementations (eg OAuth2) satisfy which requirements (eg "scopes"). 12:42:51 mm: yes 12:42:56 ... we talked about this 12:43:17 ... most to be included in the Security Best Practice document 12:43:30 ... and Use Case document should have more generic description 12:43:45 ... and possibly link to the Best Practices document 12:44:36 ... would be nice to have detailed description at one place 12:45:00 ... question 4 here is more related to Web questionnaire 12:45:29 ... probably should look at the long list on security 12:46:29 kaz: McCool, could you please respond to this issue 84? 12:46:50 mm: (adds comments) 12:47:07 ... adding a cross-reference 12:48:04 ml: think we need to extend the Use Case template with some more detailed security questions 12:48:07 mm: yeah 12:48:37 s|security|security and privacy| 12:49:19 ... just added a cross-referencing with wot-security issue 168 12:49:42 -> https://github.com/w3c/wot-security/issues/168 wot-security issue 168 - Add "Security and Privacy Considerations" to all use cases (or requirements) 12:50:58 ml: (also updates the wot-usecases issue 84) 12:51:20 ... McCool will discuss this in the Security TF and come back with a list of candidate questions 12:51:30 mm: ok 12:51:58 ... 3 sub steps 12:52:21 ... starting with brainstorming 12:52:31 ... look at the CR questions we got 12:53:49 subtopic: Issue 70 12:54:11 -> https://github.com/w3c/wot-usecases/issues/70 Issue 70 - Fix reference section 12:54:40 ml: PR 129 already available 12:54:42 (closed) 12:55:00 subtopic: Issue 45 12:55:30 -> https://github.com/w3c/wot-usecases/issues/45 Issue 45 - Review EdgeX Architecture 12:55:58 mm: what would be the use case description for this proposal? 12:56:25 s/mm:/ml:/ 12:56:35 mm: maybe we need some more generic use case description 12:56:55 q+ 12:57:26 ... also a hub-based architecture proposal for the Architecture document 12:57:51 ... we could think about adding a section for hub-based architecture 13:00:11 kaz: from our viewpoint, hub-based structure is one the possible connection patters, and we already have a section about that which could include hub-based structure as well 13:00:19 ... also we @@@ 13:00:22 topic: AOB 13:00:50 ml: will update the shortname to "wot-usecases" 13:01:16 kaz: as I mentioned, we've got transition approval, so let' move forward :) 13:01:19 [adjourned] 13:02:12 s/@@@/should have some concrete use case scenario for EdgeX architecture if we want to have a use description for it within the Use Cases document./ 13:02:18 rrsagent, make log public 13:02:24 rrsagent, draft minutes 13:02:24 I have made the request to generate https://www.w3.org/2021/05/04-wot-uc-minutes.html kaz 13:02:36 chair: Lagally 13:02:37 rrsagent, draft minutes 13:02:37 I have made the request to generate https://www.w3.org/2021/05/04-wot-uc-minutes.html kaz 13:03:12 s/topic: Status check// 13:03:12 rrsagent, draft minutes 13:03:13 I have made the request to generate https://www.w3.org/2021/05/04-wot-uc-minutes.html kaz 15:01:43 Zakim has left #wot-uc