13:00:45 RRSAgent has joined #wot-uc 13:00:50 logging to https://www.w3.org/2023/10/26-wot-uc-irc 13:00:50 meeting: WoT Use Cases 13:02:57 present+ Kaz_Ashimura, Michael_McCool, Michael_Koster 13:03:02 chair: McCool 13:03:45 mjk has joined #wot-uc 13:04:23 McCool has joined #wot-uc 13:04:33 present+ Ege_Korkan 13:06:06 present+ Tomoaki_Mizushima 13:06:48 scribenick: mjk 13:07:13 topic: minutes review 13:07:24 agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#October_26th.2C_2023 13:07:33 -> https://www.w3.org/2023/10/19-wot-uc-minutes.html Oct-19 13:08:09 mm: any objections to publishing the minutes? 13:08:19 ... no objections, publish 13:08:24 topic: PRs 13:08:39 subtopic: PR #224 13:10:09 -> https://github.com/w3c/wot-usecases/pull/224 PR 224 - Update README.md 13:10:51 mm: rewording the README 13:11:00 ... any objections to merging? 13:11:07 ... merged 13:11:44 topic: PR #231 - Discovery Requirements 13:11:56 s/topic/subtopic 13:12:19 mm: added category names 13:12:34 i|added|-> https://github.com/w3c/wot-usecases/pull/231 PR 231 - Capture Discovery Requirements| 13:12:40 rrsagent, make log public 13:12:46 rrsagent, draft minutes 13:12:47 I have made the request to generate https://www.w3.org/2023/10/26-wot-uc-minutes.html kaz 13:13:53 luca_barbato has joined #wot-uc 13:14:11 mm: some of the category names are actually use cases 13:14:24 q? 13:14:24 q+ 13:14:47 present+ Luca_Barbato 13:15:30 mm: the education use case needs more context in the name 13:16:33 kaz: adding existing use cases is good, we need more discussion around education use cases 13:17:12 ... for example learning analytics 13:17:39 ack k 13:17:46 rrsagent, draft minutes 13:17:47 I have made the request to generate https://www.w3.org/2023/10/26-wot-uc-minutes.html kaz 13:17:53 ... suggest that we add a note to explain that we need more use cases 13:19:24 mm: split up some use cases that had more than one requirement combined 13:20:31 ... some section numbering is wrong 13:22:11 q+ 13:22:42 ack k 13:22:50 kaz: there should be accessibility use cases 13:23:31 s/use cases/use cases. note that one specific use case could belong to multiple categories./ 13:25:23 ... (online editing) 13:30:10 ack k 13:30:13 rrsagent, draft minutes 13:30:14 I have made the request to generate https://www.w3.org/2023/10/26-wot-uc-minutes.html kaz 13:32:03 mm: consistent format for entries example committed to the document 13:32:11 ... still need to fix some formatting 13:32:12 q+ 13:32:27 ... any objections to merge this once the formatting is fixed? 13:32:46 kaz: happy with this direction, this could become a new template 13:33:05 Ege has joined #wot-uc 13:33:14 mm: yes, the big job is the TD work 13:33:47 ege: this looks good, but not sure how the rest of the pipeline will work 13:34:01 ... what about the title for example system 13:34:20 mm: this is the category, thinking about dropping th ecategories 13:34:37 s/th ec/the c/ 13:35:12 q+ 13:35:36 rrsagent, draft minutes 13:35:37 I have made the request to generate https://www.w3.org/2023/10/26-wot-uc-minutes.html kaz 13:35:55 ege: what do we do if a requirement is not satisfied and we need to create a feature and work items 13:36:09 mm: we will need to link to work items 13:36:36 ... what if a requirement is partially satisfied? What is the progress? 13:36:58 ... what about mandatory vs. optional features? 13:37:15 ege: this is better and should be merged 13:37:46 q? 13:38:30 ack k 13:38:35 kaz: we can start with this and iterate, and improve the categories 13:38:56 q+ 13:39:07 ack mjk 13:39:50 mm: we can merge now and discuss the structure more later 13:40:11 ... we can start a PR for TD and bindings now 13:40:23 s/categories/categories. for example, we could use "General" instead of "System" for 4.3.6.1 13:40:30 rrsagent, draft minutes 13:40:31 I have made the request to generate https://www.w3.org/2023/10/26-wot-uc-minutes.html kaz 13:41:08 ack k 13:41:45 subtopic: PR#233 - Security 13:42:51 mm: started to define categories, work in progress 13:43:07 i|started|-> https://github.com/w3c/wot-usecases/pull/233 PR 233 - Template for Category/Risk org for Security Requiremens| 13:43:15 s/mens/ments/ 13:44:08 mm: subsection for risk 13:44:58 q+ 13:45:12 mm: each risk has a mitigation requirement 13:45:22 ... any opinions or comments? 13:46:01 kaz: the direction is good, I fixed the spelling in the title, also there is a formatting error 13:46:08 ack k 13:47:49 mm: added security to the category names to avoid conflicts with other categories 13:48:22 mm: should the requirement be named after the risk or the mitigation? 13:48:40 ... A risk may have multiple requirements 13:50:16 https://github.com/w3c/wot-usecases/issues/232 13:50:46 subtopic: PR #232 13:51:18 q+ 13:51:27 mm: specific categories for security 13:52:11 ege: the public category seems to be more than one category 13:53:18 q+ 13:53:29 ack e 13:54:29 mm: there might be come common requirements in the public category, for example ddos 13:55:07 ... we can always iterate and adjust 13:56:37 kaz: in the titles, maybe we could add "risk of" to clarify the security context 13:57:14 mm: some requirements could fall into more than one category 13:58:41 kaz: we don't need to add risk of to the titles 13:59:23 kaz: also we should think about using a noun or adjective in the title 13:59:31 mm: adjectives are more descriptive 14:00:35 kaz: for example private is too vague, we should add more description 14:01:17 ... we should think about what kind of titles to use for the categories 14:01:34 mm: will follow up with another meeting, TBA 14:02:08 ... adjourned 14:02:08 rrsagent, draft minutes 14:02:09 I have made the request to generate https://www.w3.org/2023/10/26-wot-uc-minutes.html kaz 15:57:32 Zakim has left #wot-uc