11:03:28 <RRSAgent> RRSAgent has joined #wot-uc
11:03:32 <RRSAgent> logging to https://www.w3.org/2024/07/31-wot-uc-irc
11:03:35 <kaz> meeting: WoT Use Cases
11:04:04 <kaz> present+ Kaz_Ashimura, Tomoaki_Mizushima, Ege_Korkan, Luca_Barbato
11:06:23 <Ege> Ege has joined #wot-uc
11:06:58 <Ege> topic: Agenda Review
11:07:10 <Ege> tm: we have 6 topics today
11:07:25 <kaz> q?
11:07:28 <Ege> tm: any other topics?
11:07:32 <Ege> ek: looks good to me
11:07:41 <kaz> q+
11:07:51 <Ege> tm: also please make sure to use q+ and speaking slowly
11:08:03 <kaz> q-
11:08:09 <Ege> topic: Logistics
11:08:21 <Ege> tm: the meetings on august 21 and 28 will be cancelled
11:08:27 <Ege> q+
11:08:44 <kaz> q+
11:09:13 <kaz> ack e
11:09:30 <Ege6> Ege6 has joined #wot-uc
11:09:49 <Ege6> ek: I cannot be there for september 4th as well
11:10:35 <kaz> q-
11:11:13 <Ege> Ege has joined #wot-uc
11:12:19 <Ege> I keep losing internet connection for 10 seconds...
11:13:12 <kaz> s/I keep losing internet connection for 10 seconds...//
11:13:31 <kaz> q-
11:14:25 <kaz> scribe+
11:14:32 <kaz> topic: Meeting plan
11:14:52 <kaz> tm: would like to fix GH issue template for use case using YAML
11:14:59 <kaz> ... then internal trial
11:15:04 <kaz> ... then refactoring
11:15:21 <kaz> q+
11:15:33 <kaz> q-
11:15:36 <kaz> topic: Minutes
11:16:00 <kaz> -> https://www.w3.org/2024/07/17-wot-uc-minutes.html July-17
11:16:37 <kaz> q+
11:17:02 <kaz> q-
11:17:34 <kaz> tm: any objections?
11:17:44 <kaz> (none)
11:17:47 <kaz> approved
11:17:58 <kaz> topic: Fix the YAML-based Use Case template
11:18:07 <kaz> q+
11:18:18 <kaz> q-
11:20:29 <Ege> Ege has joined #wot-uc
11:20:58 <Ege> test?
11:21:17 <kaz> s/test?//
11:21:22 <kaz> subtopic: PR 298
11:21:37 <kaz> scribenick: Ege
11:21:57 <Ege> tm: this PR changes the order of items
11:22:09 <kaz> i|this PR|-> https://github.com/w3c/wot-usecases/pull/298 PR 298 - Change the order of items of WoT-UseCases-Template.yml|
11:22:14 <kaz> rrsagent, make log public
11:22:18 <kaz> rrsagent, draft minutes
11:22:19 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/31-wot-uc-minutes.html kaz
11:22:26 <kaz> q+
11:22:30 <Ege> tm: Do you know Ted?
11:22:59 <Ege> kaz: He is active in DID work and is a W3C member
11:23:28 <Ege> kaz: we should talk about his contributions in general in the main call
11:23:58 <kaz> s|DID|DID/VC|
11:24:58 <Ege> tm: any comments or questions?
11:25:04 <kaz> q+
11:25:27 <kaz> ack k
11:26:09 <Ege> tm: Is it ok to merge?
11:26:13 <Ege> kaz: the changes are fine
11:26:28 <Ege> ... it would be nicer to explain the PR a bit more
11:26:59 <kaz> -> https://github.com/w3c/wot-usecases/blob/57faf912b0910ba87f7ae946d13adbbfb94e04af/.github/ISSUE_TEMPLATE/WoT-UseCases-Template.yml preview md
11:27:00 <Ege> ek: let's merge :)
11:27:55 <kaz> s/it would be/but it would be/
11:29:03 <Ege> topic: Real names and E-mail addresses
11:29:04 <kaz> merged
11:29:08 <kaz> s/merged//
11:29:18 <kaz> i/Real/merged/
11:29:22 <kaz> rrsagent, draft minutes
11:29:24 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/31-wot-uc-minutes.html kaz
11:29:36 <kaz> s/topic:/subtopic:/
11:29:54 <Ege> tm: we decided that ownership and being able to contact is important. If we cannot, we should be able to delete the use case
11:30:11 <Ege> ... anonymous submissions are not allowed
11:30:14 <Ege> q+
11:30:28 <kaz> scribe+
11:30:34 <kaz> ek: agree with this direction
11:30:44 <kaz> ... but need to be careful about the expression
11:30:52 <kaz> q+
11:30:55 <kaz> ack e
11:31:07 <Ege> ek: I agree with this. We can collect name and email address in another way if we need it
11:31:13 <Ege> tm: we should be able to contact submitters
11:31:20 <Ege> q+
11:31:20 <kaz> s/... but need to be careful about the expression//
11:31:22 <kaz> s/ek: agree with this direction/
11:31:33 <Ege> tm: I would like to use github account first
11:33:17 <kaz> ack k
11:33:30 <Ege> kaz: Please clarify what you want to talk about first
11:34:08 <Ege> tm: Email and name should be decided
11:34:19 <Ege> kaz: Could you remove the policy mention from the agenda?
11:35:27 <Ege> kaz: (explains the issue in the markdown)
11:39:43 <luca_barbato> q+
11:42:21 <kaz> ack eg
11:42:26 <Ege> https://github.com/egekorkan
11:42:58 <Ege> ek: Could you clarify what you mean by contacting someone through github?
11:43:12 <kaz> [[
11:43:13 <Ege> tm: we can contact through github. No need to collect email address
11:43:21 <kaz> s/[[//
11:43:22 <kaz> [[
11:43:24 <kaz> if we can't contact submitters in the future (somehow - may or may not be email) then we reserve the right to delete a use case.
11:43:27 <kaz> We should have clear "authorship" for uses cases.
11:43:29 <kaz> We should don't allow anonymous use cases.
11:43:31 <kaz> ]]
11:43:38 <kaz> [@@@ Kaz will move Mizushima-san's points later ]
11:43:51 <kaz> q+
11:44:53 <kaz> ack lu
11:46:04 <Ege> ek: My question was not answered
11:46:12 <Ege> lb: we can open an issue or discussion and tag them
11:46:21 <Ege> ... That should be enough for our use case
11:46:47 <Ege> ... They relinquish the right once they submit. UCs are just an input for standardization work
11:48:07 <Ege> ... if a UC is not useful, we can delete and move on to the next one
11:48:21 <kaz> q?
11:48:26 <kaz> q+ Ege
11:48:28 <kaz> q- later
11:48:54 <kaz> ack e
11:49:04 <Ege> ek: my question is answered by Luca. We should note it down, e.g. tagging GitHub handle in an issue
11:51:22 <kaz> ack k
11:51:50 <kaz> scribe+
11:51:54 <Ege> kaz: Partly answers Ege's question
11:52:03 <kaz> s/scribe+//
11:52:05 <kaz> scribe+
11:52:24 <kaz> kaz: but that is rather "how to solve the problem"
11:52:58 <kaz> ... and we should start with "what kind of information we need when we collect use cases" first
11:53:15 <kaz> ... then can think about how to get that information next
11:54:30 <Ege> ... we should clarify our need first
11:55:01 <kaz> i/we should/scribenick: Ege/
11:55:38 <kaz> scribenick: kaz
11:55:53 <kaz> kaz: we need clear input for each item from the UC tempalte
11:56:05 <kaz> ... and if some of the items are unclear, we need further clarification
11:56:24 <kaz> ... and so we need some method to contact the submitter to get further clarification
11:56:40 <kaz> ... we should start with that kind of need
11:56:42 <luca_barbato> q+
11:56:48 <Ege> tm: we should discuss account to discuss those issues
11:57:02 <kaz> i/we should discuss/scribenick: Ege/
11:57:15 <Ege> tm: I think there is enough in the issue template
11:57:29 <kaz> q?
11:57:39 <kaz> q+
11:58:14 <kaz> s/kind of need/kind of need, then we can talk about how to get the information as Luca proposed./
11:58:41 <kaz> q?
11:58:59 <Ege> lb: just by using the issue, we can ask all the information we need. Until we have it all, we can keep the issue open and not contribute to git
11:59:02 <kaz> ack lu
11:59:30 <kaz> ack k
11:59:41 <Ege> kaz: we should create a draft policy page
12:00:24 <kaz> s/page/page, and ask people to give ideas to that page/
12:00:32 <Ege> adjourned
12:00:40 <kaz> rrsagent, draft minutes
12:00:41 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/31-wot-uc-minutes.html kaz
12:02:55 <kaz> agenda: https://github.com/w3c/wot-usecases/blob/main/TODO/20240731.md
12:02:56 <kaz> rrsagent, draft minutes
12:02:58 <RRSAgent> I have made the request to generate https://www.w3.org/2024/07/31-wot-uc-minutes.html kaz
12:04:20 <dape> dape has joined #wot-uc
12:04:42 <mahda> mahda has joined #wot-uc
13:27:58 <EgeKorkan> EgeKorkan has joined #wot-uc
14:04:57 <Zakim> Zakim has left #wot-uc