11:59:44 <RRSAgent> RRSAgent has joined #wot
11:59:48 <RRSAgent> logging to https://www.w3.org/2024/06/26-wot-irc
11:59:49 <kaz> meeting: WoT-WG/IG
11:59:57 <kaz> present+ Kaz_Ashimura, Luca_Barbato
12:00:24 <McCool> McCool has joined #wot
12:01:21 <mjk> mjk has joined #wot
12:01:37 <Tomo> Tomo has joined #wot
12:01:47 <dezell> dezell has joined #wot
12:01:57 <dezell> present+ David_Ezell
12:02:51 <kaz> present+ Michael_McCool, Ege_Korkan, Sebastian_Kaebisch
12:03:10 <kaz> present+ Mahda_Noura, Michael_Koster, Tomoaki_Mizushima
12:03:16 <kaz> rrsagent, make log public
12:03:22 <kaz> rrsagent, draft minutes
12:03:24 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
12:03:49 <kaz> chair: McCool
12:04:11 <mahda> mahda has joined #wot
12:04:16 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#26_June_2024
12:04:46 <mahda> present+ Mahda_Noura
12:06:01 <kaz> scribenick: mahda
12:06:07 <sebastian> sebastian has joined #wot
12:06:16 <kaz> topic: Guests
12:06:26 <mahda> Topic: Guests, New Members
12:06:32 <kaz> s/topic: Guests//
12:06:38 <mahda> mm: any news on the new members Kaz?
12:06:40 <mahda> kaz: no
12:06:49 <mahda> topic: Minutes
12:06:51 <kaz> s/members/IE applicants, /
12:07:01 <mahda> mm: any objection to the minutes of June 19th?
12:07:06 <mahda> (none)
12:07:09 <kaz> i|19th|-> https://www.w3.org/2024/06/19-wot-minutes.html June 19|
12:07:16 <mahda> topic: Quick Items
12:07:24 <kaz> subtopic: Smart Cities IG
12:07:27 <kaz> q+
12:07:34 <mahda> mm: deadline for AC Review is July 3, what is the status?
12:07:45 <mahda> kaz: We got 22 supports already
12:08:20 <mahda> subtopic: Editors
12:08:21 <kaz> i|deadline|-> https://www.w3.org/2002/09/wbs/33280/smartcities2024/ AC review ongoing till July 3 (Member-only)|
12:09:09 <McCool> proposal: Confirm Luca Barbato and Ege Korkan as new Editors for the Use Case and Requirements document.
12:09:17 <kaz> s/Editors/Editors for UC Note/
12:09:39 <McCool> resolution: Confirm Luca Barbato and Ege Korkan as new Editors for the Use Case and Requirements document.
12:09:54 <kaz> q+
12:11:21 <McCool> proposal: Change status of Michael Lagally and Ryuichi Matsukura to Previous Editors for the Use Case and Requirements document.
12:11:22 <kaz> i|proposal:|-> https://www.w3.org/2024/06/26-wot-uc-minutes.html#t02 June-26 Use Case TF discussion|
12:11:38 <kaz> q-
12:11:51 <McCool> resolution: Change status of Michael Lagally and Ryuichi Matsukura to Previous Editors for the Use Case and Requirements document.
12:12:50 <kaz> q?
12:13:00 <gkellogg> gkellogg has joined #wot
12:13:02 <mahda> topic: Notices
12:13:12 <mahda> mm: any announcements?
12:13:17 <mahda> (none)
12:13:26 <mahda> topic: Meetups
12:13:45 <mahda> mm: anything planned for Japaneese meetups?
12:14:00 <kaz> s/Japanese meetups/Japanese CG/
12:14:25 <kaz> q+
12:14:27 <mahda> mizushima: We have planned a use case meetup, but the details are not ready yet
12:14:43 <mahda> topic: Liaisons
12:15:33 <mahda> Kaz: I am working with 30 teams, on the NGSI-LD with the FIWARE guys we continued the discussions, my name will be put there
12:15:54 <mahda> mm: NGSI-LD is not the official name
12:16:35 <mahda> sebastian: are the meetings taking place every week on Friday, or are they bi-weekly
12:16:47 <mahda> kaz: bi-weekly
12:17:19 <mahda> mm: I think the problem is that the meeting invitation that is provided is not bi-weekly and needs to be changed
12:18:29 <mahda> kaz: In any case once there becomes a collaboration between WoT and NGSI-LD, we can manage the time
12:19:07 <mahda> topic: Errata
12:19:20 <mahda> mm: the Errata policy is now in effect
12:19:22 <Ege> q+
12:19:25 <kaz> ack k
12:19:55 <mahda> ege: I will do now the PR
12:20:14 <kaz> i|the Errata po|-> https://github.com/w3c/wot/blob/main/policies/errata-management.md errata-management.md|
12:20:21 <kaz> rrsagent, make log public
12:20:24 <kaz> rrsagent, draft minutes
12:20:26 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
12:20:43 <mahda> topic: Meeting Schedules
12:20:46 <kaz> present+ Kunihiko_Toumura
12:21:30 <mahda> mm: We will have a chairs call on July 1st, and we will have a Wednesday call next week eventhough it's a holiday in the US, and July 15th is cancelled
12:21:43 <kaz> i|We will|-> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates Cancellations|
12:21:46 <kaz> rrsagent, draft minutes
12:21:48 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
12:22:13 <dezell> dezell has joined #wot
12:22:27 <mahda> mm: We should also add TPAC week to the cancellations
12:22:29 <kaz> s/Japaneese meetups/Japanese CG/
12:22:30 <kaz> rrsagent, draft minutes
12:22:32 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
12:23:41 <mahda> mm: We should check the schedule also, we are behind in the use cases and requirements due to missing 5 meetings. Other than that, discovery is schedules for mid-December however we are not active there
12:24:06 <mahda> mm: we need to make sure we are on schedule for the whole process and discuss that, maybe could be an agenda for TPAC
12:24:42 <mahda> topic: F2F Planning
12:25:10 <mahda> mm: We did add the F2F event in the schedule
12:25:29 <kaz> i|We did|-> https://github.com/w3c/wot/blob/main/planning/schedule.md schedule.md|
12:26:10 <kaz> i|We should check|-> https://github.com/w3c/wot/blob/main/planning/schedule.md schedule.md|
12:26:12 <kaz> rrsagent, draft minutes
12:26:13 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
12:26:21 <mahda> sebastian: updates on the F2F event, the Wiki page has now been updated, the location, public transportation information
12:28:40 <mahda> sebastian: we wanted to initially get some discounts on the hotels that are in the area, however this is costly for Siemens, so please check the hotels yourself and decide
12:28:55 <dezell> dezell has joined #wot
12:29:14 <kaz> q+
12:29:20 <Ege> ack
12:29:20 <mahda> ... there is also a link to the public transportation in Munich
12:29:23 <Ege> q?
12:29:25 <Ege> ack e
12:30:04 <kaz> -> https://www.w3.org/WoT/IG/wiki/Wiki_for_WoT_Week_2024_planning Wiki for WoT Week on Nov 25-29
12:30:35 <mahda> sebastian: we need to decide whether we want a full day or a half day on the last day
12:31:46 <mahda> Ege: if you are staying longer, you could also use the Deutschland Ticket for getting around
12:31:56 <Ege> q+
12:32:26 <mahda> mm: I think we should focus on the TPAC agenda, and any overflow we can cover in the WoT F2F meeting
12:32:45 <kaz> -> https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_planning
12:33:30 <kaz> s/planning/planning Wiki for TPAC/
12:33:45 <gkellogg> gkellogg has joined #wot
12:33:48 <kaz> ack k
12:34:16 <kaz> kaz: would be better to have the links for the TPAC 2024 wiki and WoT Week wiki on the schedule.md too
12:34:22 <kaz> i/would/scribenick: kaz/
12:34:26 <kaz> scribenick: mahda
12:34:35 <kaz> rrsagent, draft minutes
12:34:37 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
12:35:14 <mahda> mm: Please do add your suggested topics to the WiKi for TPAC organization
12:35:24 <mahda> topic: Document Refractoring
12:36:37 <mahda> mm: We had a discussion in the use cases TF, and were wondering where the requirements actually go, should the architecture be a REC document or not.
12:37:03 <kaz> [[
12:37:04 <kaz> Where do requirements go?
12:37:04 <kaz> What is the role/status of Architecture?
12:37:04 <kaz> How can we better organize Profiles?
12:37:04 <kaz> Do we have to wait until UC&R is a Note before implementing features?
12:37:05 <kaz> ]]
12:37:33 <mjk> q?
12:37:33 <Ege> q+
12:37:39 <kaz> q+
12:37:46 <mahda> ... my opinion would be that, architecture should be the main entry point and understanding WoT, they should get a summary and motivation of WoT, could be an informative document, published as Note.
12:38:31 <McCool> q+
12:39:07 <mahda> ege: I am aligned, I think there should not be overlap between documents, and keep architecture as an informative note, should be an explainer for all. It should be a timeless document and not require too much changes, because we cannot generally change our design decisions, should not be too long
12:39:56 <sebastian> sebastian has joined #wot
12:39:56 <mahda> kaz: I suggest we record all the main points from the use cases
12:40:04 <kaz> ack e
12:40:06 <kaz> ack k
12:40:15 <mahda> mm: we should volunteer to make a PR, and everyone can make comments
12:40:26 <mahda> mm: any volunteers?
12:40:27 <sebastian> <sorry, I had Internet blackout at home>
12:40:35 <mahda> mm: I could do it
12:40:56 <kaz> q+
12:41:12 <mahda> mm: the PR should capture the proposal and ask people for comments. In a month or two we need a resolution
12:41:31 <Ege> +1 on PR :)
12:41:41 <mahda> kaz: As a starting point you could create a template based on the four questions, and other put their points
12:42:08 <Ege> +1 for concrete proposal
12:42:17 <Ege> q+
12:42:21 <Ege> ack m
12:42:34 <kaz> ack k
12:42:56 <kaz> s/and other/and everybody including you can/
12:44:16 <kaz> -> https://www.w3.org/2024/06/26-wot-uc-minutes.html#t05 June-26 UC call discussion
12:44:20 <mahda> mm: we were discussing the UC&R, do we have to wait until we publish it officially? I think it would cause delays, if we merge a user case and requirement we have a consensus and should work on it.
12:44:47 <mahda> mm: I think when we publish a note, that is sort of an external thing, and it's more for external consumption
12:44:55 <kaz> q+
12:44:57 <Tomo> q+
12:45:01 <mahda> mm: any comments on this?
12:45:03 <Ege> ack e
12:45:05 <Ege> q+
12:45:20 <mahda> mm: merging PR in the UC documents as a sort of consensus
12:45:49 <McCool> proposal: Use merging of a PR into the UC&R document that there is consensus on a requirement.
12:45:53 <kaz> ack k
12:46:08 <mahda> kaz: would be easier to handle the discussion if we wait, but we need to look at the charter schedules. But if we work at the same time, we need to take care
12:46:20 <mahda> mm: We probably want to discuss the requirements one by one...
12:46:34 <mahda> kaz: I am not objecting, but we need to clarify the procedure
12:47:38 <mahda> mm: when we merge the PR that should be the record of concensus, but we need to have a process, it could be as simple as sumarizng the requirements and ask people for comments, and ask people for 1/2 weeks to comments. I think that should be faster then waiting for the Note to be published
12:48:19 <kaz> s|1/2|one or two|
12:48:32 <kaz> s/then waiting/than waiting/
12:48:37 <McCool> proposal: Use merging of a PR into the UC&R document that there is consensus on a requirement.  PRs for requirements should be tagged as "Requirement" in the usecases repo and notification of new requirement PRs made in the main call, with a 2-week period for review.
12:48:39 <kaz> q?
12:48:57 <sebastian> sebastian has joined #wot
12:49:25 <kaz> q+
12:50:36 <mahda> mizu: I think we have not started correct use case yet, but I would like to collect use case immediately. a consensus for technical requirements or functional requirements.
12:51:00 <kaz> s/not started correct/not started to collect/
12:51:49 <kaz> s/a consensus for technical requirements or functional requirements/btw, which do you mean by a consensus for technical requirements or functional requirements?/
12:51:53 <kaz> ack to
12:51:55 <mahda> mm: we need to document our existing requirements
12:52:30 <kaz> ack e
12:52:31 <mahda> ege: I do not want to wait for a Note, and in case a use case and a requirement is not ready, we can mark it as draft
12:52:33 <gkellogg> gkellogg has joined #wot
12:52:59 <kaz> q?
12:53:10 <mahda> mm: I think what you are saying is that we consider the editors draft as the functional requirement document
12:53:58 <mahda> mm: we have to clarify the template, this is something that I could leave off the details, but I want to get a consensus on the overall mechanism
12:55:14 <mahda> kaz: I am basically overall with the direction, but given the progress of the use case this proposal is okay for the internal group, but we cannot make the work public to the whole world yet, otherwise we will get too many backlog proposals from the world.
12:55:26 <Ege> q+
12:56:17 <McCool> proposal: Use merging of a PR into the UC&R document as the indication that there is consensus on a requirement.  PRs for requirements should be tagged as "Requirement" in the usecases repo and notification of new requirement PRs made in the main call, with a 2-week period for review.  Requirements that have not yet been published in a Note should
12:56:17 <McCool> be marked with "Draft."
12:56:34 <mahda> ege: I think we should not over engineering it
12:57:08 <McCool> proposal: Use merging of a PR into the UC&R document as the indication that there is consensus on a requirement.
12:58:07 <mahda> kaz: we have not clarified how to start the requirements discussion in the UC&R TF
12:58:45 <mahda> mm: when we merge a PR in the editors version, we can use that as a record that we have accepted that requirement by the group.
12:59:00 <McCool> proposal: Use merging of a PR into the editor's version of the UC&R document as the indication that there is consensus on a requirement.
12:59:22 <Ege> +1 to the proposal
13:00:51 <mahda> kaz: the final decision should be taking by the whole working group, but taking important decision in the main call is odd, since we already have the UC&R call.
13:01:13 <kaz> s/whole working group/whole WG and IG/
13:01:13 <Tomo> +1 for kaz
13:01:30 <kaz> s/should be taking/should made/
13:02:09 <kaz> s/taking important/making important/
13:02:29 <kaz> i/in the main call/in the main call directly without having no discussion within the UC TF/
13:02:49 <Ege> q+
13:02:51 <kaz> q+
13:02:53 <kaz> ack k
13:02:55 <kaz> q+
13:03:42 <kaz> scribenick: kaz
13:03:49 <kaz> mm: let's revisit this topic next time
13:03:53 <kaz> topic: Policies
13:04:05 <kaz> ek: need to clarify what "Editors" mean
13:04:20 <kaz> mm: let's clarify our policy
13:04:23 <kaz> q?
13:04:40 <kaz> ack e
13:04:55 <kaz> ack k
13:04:58 <kaz> topic: Profile
13:05:22 <mahda> I need to leave, thanks all
13:05:50 <kaz> kaz: McCool was proposing there should be some discussion Profile during the TD call
13:06:00 <kaz> mm: Ege mentioned TD call is already full
13:06:06 <kaz> ... but can have some discussion there
13:06:13 <kaz> [adjourned]
13:06:15 <kaz> rrsagent, draft minutes
13:06:16 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/26-wot-minutes.html kaz
13:14:20 <gkellogg> gkellogg has joined #wot
13:31:36 <gkellogg> gkellogg has joined #wot
13:49:04 <gkellogg> gkellogg has joined #wot
14:07:46 <mahda> mahda has joined #wot
14:34:43 <gkellogg> gkellogg has joined #wot
14:42:37 <TallTed> TallTed has joined #wot
14:59:03 <gkellogg> gkellogg has joined #wot
15:05:35 <bigbluehat> bigbluehat has joined #wot
15:16:23 <gkellogg> gkellogg has joined #wot
15:25:49 <gkellogg> gkellogg has joined #wot
15:27:11 <Zakim> Zakim has left #wot
15:48:57 <gkellogg> gkellogg has joined #wot
15:49:07 <gkellogg> gkellogg has joined #wot
17:46:48 <gkellogg> gkellogg has joined #wot
17:58:29 <gkellogg> gkellogg has joined #wot
18:16:08 <gkellogg> gkellogg has joined #wot
18:34:27 <gkellogg> gkellogg has joined #wot
18:52:52 <gkellogg> gkellogg has joined #wot
19:13:45 <gkellogg> gkellogg has joined #wot
19:32:06 <gkellogg> gkellogg has joined #wot
20:06:45 <gkellogg> gkellogg has joined #wot
20:37:11 <gkellogg> gkellogg has joined #wot
21:04:46 <gkellogg> gkellogg has joined #wot
21:08:41 <gkellogg> gkellogg has joined #wot
21:40:39 <gkellogg> gkellogg has joined #wot
21:52:45 <gkellogg> gkellogg has joined #wot
22:25:23 <gkellogg> gkellogg has joined #wot
22:33:34 <gkellogg> gkellogg has joined #wot
22:50:24 <gkellogg> gkellogg has joined #wot
23:13:06 <gkellogg> gkellogg has joined #wot
23:33:10 <gkellogg> gkellogg has joined #wot
23:52:56 <gkellogg> gkellogg has joined #wot