11:02:23 RRSAgent has joined #wot-uc 11:02:27 logging to https://www.w3.org/2024/07/10-wot-uc-irc 11:03:33 meeting: WoT Use Cases 11:03:51 Ege has joined #wot-uc 11:03:55 present+ Kaz_Ashimura, Tomoaki_Mizushima, Ege_Korkan, Michael_McCool, Luca_Barbato 11:04:12 McCool has joined #wot-uc 11:04:38 scribenick: kaz 11:04:51 agenda: https://github.com/w3c/wot-usecases/blob/main/TODO/20240710.md 11:04:52 q+ 11:05:18 q- 11:05:23 topic: Agenda 11:05:31 miz: (goes through the agenda) 11:05:50 i|goes|-> https://github.com/w3c/wot-usecases/blob/main/TODO/20240710.md agenda for today| 11:06:26 kaz: we should talk about your proposal on WoT-JP CG's reusing the use case template for their events 11:06:28 miz: ok 11:06:41 ... any other topics for today? 11:06:45 q+ 11:06:58 ack e 11:07:22 ek: is the test run proposal also on the agenda? 11:07:28 miz: yes 11:07:49 topic: Logistics 11:08:10 miz: no plans for cancellations atthe moment 11:08:10 q+ 11:08:18 ... but need to think about summer vaation 11:09:02 ... myself planning to take summer vacation from aug-22 till aug-31 11:09:18 ... so would cancel the call on Aug 28 11:09:25 ack m 11:09:38 mm: will discuss vacation during the main call too 11:09:51 topic: Meeting Plan 11:10:20 miz: would fix the use case issue template today 11:10:22 [[ 11:10:32 July-10: Refactoring and Fix Github Issue template using YAML 11:10:33 July-17: Fix Github Issue template using YAML 11:10:33 July-24 and July-31: Initial discussion on Requirements Template 11:10:33 Aug-7 and Aug-14: Fix basic Functional Requirements Template 11:10:33 Aug-21 and Sep-4: Fix basic Technical Requirements Template 11:10:34 ]] 11:10:37 q+ 11:10:47 ack m 11:11:03 mm: one thing thinking recently is refactoring 11:11:11 +1 to mccool 11:12:06 ... perhaps we don't need to think about the detail on functional vs technical requirements 11:12:09 q+ 11:13:00 kaz: probably we don't have to think about that kind of future topics now 11:13:10 ... but should concentrate on the topics for today now 11:13:18 q+ 11:13:48 ... so probably you should handle the long-term schedule separately in addition to the agenda topics for "today" 11:13:52 miz: ok 11:13:53 q- 11:13:58 topic: Minutes 11:14:12 q+ 11:14:18 q- 11:14:30 -> https://www.w3.org/2024/06/26-wot-uc-minutes.html#t05 June-26 11:15:03 s/#t05// 11:15:15 miz: (goes through the minutes) 11:15:41 q+ 11:16:03 ack k 11:16:32 kaz: the TF resolution on the UC Editors has been approved by the whole group too during the main call last week 11:16:50 ... so you can update the UC TF wiki and the UCR Note draft accordingly 11:16:54 miz: ok 11:17:10 ... any objections for the minutes? 11:17:12 (none) 11:17:17 minutes approved 11:17:46 topic: WoT-JP CG's reusing the UC template 11:18:03 miz: sent out a message to the whole group 11:18:27 i|sent|-> https://lists.w3.org/Archives/Member/member-wot-ig/2024Jul/0000.html [wot-uc] About the use of our Use Case Template in WoT-JP CG 11:18:45 miz: should think about the procedure 11:18:46 [[ 11:18:56 The WoT-JP CG would like to copy the WoT Use Case template to their repository. 11:18:56 Then they would like to describe their use cases in Japanese using the template. 11:18:56 And bring the use cases back to the WoT Use Cases TF after translating the use cases in Engish. 11:18:56 The original Japanese use cases should be archived in the wot-usecases repository. 11:18:57 ]] 11:19:13 miz: would agree with the above procedure 11:19:25 q? 11:19:28 q+ 11:19:50 q+ 11:19:52 kaz: firstly, this is discussion for TF-level resolution. right? 11:20:33 ... then we need to think about how to deal with #4 above 11:20:38 ack k 11:21:09 mm: my point was possible concern about the mis-translation of the original JP content into English 11:21:20 ... should have an archive of the original JP version 11:21:31 q? 11:21:35 q+ 11:22:02 ek: agree with the overall proposal 11:22:20 ... but would suggest we start that after testing the usage of the template ourselves 11:22:27 ack e 11:22:46 kaz: so there are two questions 11:22:59 ... 1. when to start this (e.g., after testing it ourselves) 11:23:10 ... 2. how/where to manage the resources 11:24:02 miz: question #1 above (when to start) can be discussed as part of the "Refactoring" topic later 11:24:15 q+ 11:24:27 mm: what's the date? 11:25:40 ack k 11:25:50 kaz: I'm OK with discussing the detail later 11:26:02 ... but we should make basic agreement quickly now 11:26:30 ... e.g., I'm OK with starting the procedure after testing the usage of the template ourselves within the WoT IG 11:26:47 ... and we need to think about how/where to manage the JP resources anyway 11:26:50 +1 let's do a trial run asap 11:27:05 q+ 11:27:11 miz: the WoT-JP CG event is expected on July 26 11:27:30 ek: let's do a trial run for the UC template right away 11:27:43 ... we already have existing example use cases 11:28:25 ... the question is rather how to extract requirements later 11:28:47 q? 11:28:48 selected use cases are tracked at https://github.com/w3c/wot-thing-description/issues?q=is%3Aopen+is%3Aissue+label%3A%22Selected+for+Use+Case%22+label%3A%22Has+Use+Case+Potential%22 11:28:49 ack e 11:29:03 ... we can even try on today 11:29:05 q+ 11:30:06 mm: fine by me 11:30:29 kaz: we already have some more expected agenda items including finalization of the template itself 11:30:35 ... so we should handle them first 11:31:00 ... and you can ask people to submit example use cases based on the finalized template as an action item later 11:31:03 miz: ok 11:31:31 q+ 11:32:07 JKRhb has joined #wot-uc 11:32:27 q+ 11:33:58 ... then the proposed procedure above? 11:34:25 kaz: we still need to clarify #4 above (where/how to manage the JP version use case resources) 11:35:03 ... for example, the WoT JP CG can copy the UC template and the issue mechanism from the wot-usecases repo to their repo 11:35:08 suggest changing point 4 to read: "The original Japanese use cases should be archived so they are available for future reference." 11:35:16 ... and everything will be automatically archived on their repo 11:35:18 mm: right 11:35:33 ... we can add modification/clarification about that for #4 above 11:35:44 s/suggest changing point 4 to read: "The original Japanese use cases should be archived so they are available for future reference."// 11:35:45 suggest changing point 4 to read: "The original Japanese use cases should be archived so they are available for future reference." 11:35:50 i/suggest/[[/ 11:35:51 ]] 11:36:09 rrsagent, make log public 11:36:13 rrsagent, draft minutes 11:36:14 I have made the request to generate https://www.w3.org/2024/07/10-wot-uc-minutes.html kaz 11:37:45 proposal: suggest changing point 4 to read:"The original Japanese use cases should be archived so they are available for future reference." 11:38:03 proposal: suggest changing point 4 to read: "The original Japanese use cases should be archived so they are available for future reference." 11:38:32 s/proposal: suggest changing point 4 to read:"The original Japanese use cases should be archived so they are available for future reference."// 11:38:44 resolution: suggest changing point 4 to read: "The original Japanese use cases should be archived so they are available for future reference." 11:39:01 i/resolu/(no objections)/ 11:39:04 rrsagent, draft minutes 11:39:06 I have made the request to generate https://www.w3.org/2024/07/10-wot-uc-minutes.html kaz 11:39:32 topic: Fix the YAML-based Use Case template 11:39:57 subtopic: typos 11:40:30 -> https://github.com/w3c/wot-usecases/issues/288 issue 288 - [UC Template] Typos 11:40:31 q+ 11:40:50 ack k 11:40:59 kaz: have you fixed the typos 11:41:03 s/typos/typos?/ 11:41:07 miz: yes 11:41:20 (closed) 11:41:37 ack m 11:41:46 subtopic: Stakeholders 11:42:11 -> https://github.com/w3c/wot-usecases/pull/291 PR 291 - Use a checklist for the stakeholders 11:42:49 miz: Luca made modification to use checkboxes 11:43:28 ... ok to merge that? 11:43:42 mm: sure 11:44:22 (no objections) 11:44:26 merged 11:45:13 subtopic: Submitters 11:45:32 -> https://github.com/w3c/wot-usecases/issues/286 Issue 286 - [UC Template] "Submitter" should indicate Real Name(s) 11:45:47 miz: we don't need to discuss this at the moment 11:46:05 q+ 11:46:36 mm: eventually need some way to find a real name when we publish the UCR Note 11:47:06 please see an example https://github.com/hspaay 11:47:09 ek: need to have not only GitHub names but real names too 11:47:29 s|please see an example https://github.com/hspaay|| 11:48:10 ... would like to suggest we have real names and email addresses 11:48:34 lb: to contact the proposers, we need to have email addresses too 11:48:55 miz: it's not good to describe email address on the public GitHub 11:48:56 q+ 11:48:56 q? 11:48:58 q+ 11:48:59 q+ 11:48:59 ack e 11:49:10 to be specific I did not say that this information has to be in the github issue 11:49:12 ack m 11:49:14 q+ Ege 11:49:18 q+ McCol 11:49:25 q- McCol 11:50:18 mm: there could be possible privacy issue to put the email address on GitHub 11:51:20 kaz: had discussion with the Security contact from the W3C Team 11:51:32 ... basically, getting email address itself is fine if needed 11:52:00 ... and we can think about how to manage the information separately, e.g., asking them to send the information separately to the team-wot list 11:52:09 ... and we can add a note about that to the UC template 11:52:12 q? 11:52:14 ack k 11:52:37 lb: the simplest way is we don't require email address 11:52:38 q+ 11:53:06 ... when we need to contact the person, we need an email address at that time 11:53:50 ... another option is our declaring that we reserve the right to close the UC issue when we can't get enough clarification 11:54:23 present+ Jan_Romann 11:55:02 ... would stay away from dealing with privacy 11:55:12 rrsagent, draft minutes 11:55:13 I have made the request to generate https://www.w3.org/2024/07/10-wot-uc-minutes.html kaz 11:55:19 q? 11:55:38 ek: can agree with Luca 11:56:06 ... if we can close the UC proposal issue when we can't get enough clarification, that's fine 11:56:29 ack eg 11:57:23 ... on the other hand, if we keep the contact information, that should be handled carefully 11:57:34 mm: email address is technically not stable and changeable 11:58:05 ... but if the email information can be kept in a secret manner, that's fine 11:58:25 ... anyway, would have real names on the UC proposals 11:58:40 +1 to collecting the name 11:58:44 q+ 11:59:14 ... we should have a policy to delete UC proposals if we can't get enough clarification 11:59:21 rrsagent, draft minutes 11:59:23 I have made the request to generate https://www.w3.org/2024/07/10-wot-uc-minutes.html kaz 11:59:30 q? 11:59:30 q+ 11:59:30 ack mm 11:59:30 ack m 12:00:00 s/get enough clarification/contact the submitters/ 12:00:13 q? 12:00:26 please add to the minutes: I feel we should have a policy that allows us to remove a use case if we can't contact the submitters in the future 12:00:46 (ntd) 12:01:19 kaz: unfortunately, we're getting out of time 12:02:12 ... but would suggest we record the important point that we should have a policy that allows us to remove a use case if we can't get enough clarification or can't contact them 12:02:21 ... let's continue the discussion next time 12:02:23 [adjourned] 12:02:28 rrsagent, draft minutes 12:02:30 I have made the request to generate https://www.w3.org/2024/07/10-wot-uc-minutes.html kaz 12:06:34 mahda has joined #wot-uc 12:09:05 dape has joined #wot-uc 12:42:12 Ege3 has joined #wot-uc 13:57:32 Ege has joined #wot-uc 14:04:38 Zakim has left #wot-uc 14:06:40 mahda has joined #wot-uc