12:01:35 RRSAgent has joined #wot 12:01:39 logging to https://www.w3.org/2024/05/22-wot-irc 12:01:50 meeting: WoT-WG/IG 12:02:35 present+ Kaz_Ashimura, Michael_McCool, Luca_Barbato, Mahda_Noura, Michael_Koster, Tim_Panton 12:02:35 dezell has joined #wot 12:02:41 present+ Kunihiko_Toumura 12:02:46 present+ David_Ezell 12:02:58 ktoumura has joined #wot 12:03:15 mjk has joined #wot 12:04:17 mm8 has joined #wot 12:04:27 regrets+ Tomoaki_Mizushima 12:04:32 present+ Ege_Korkan 12:04:56 q+ 12:05:04 mahda has joined #wot 12:05:05 q- 12:05:27 Ege has joined #wot 12:05:31 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#22_May_2024 12:05:44 steely_glint has joined #wot 12:06:05 regrets+ Sebastian_Kaebisch 12:06:50 scribenick: luca_barbato 12:07:12 topic: New members 12:07:29 mm: We have a new member, Tim can you present yourself? 12:07:46 dape has joined #wot 12:08:18 Tim: I participated to the WebRTC group, I'm looking forward to learn and then contribute 12:08:46 mm: Do you have been involved to the local p2p proposals? 12:08:54 Tim: I just started reading it 12:08:57 q+ 12:09:07 q+ 12:10:44 ack k 12:11:08 kaz: We already discussed in the profile call, regarding contributing a UC for the streaming + wot 12:11:28 ack lu 12:11:50 lb: getting more and more interest in multimedia use cases 12:11:55 ... any specific procedure? 12:12:11 mm: as Kaz mentioned we should start with use cases 12:12:51 mm: I guess we first need to look into the UC, and bootstrapping a new task force would require changes in the charter document 12:12:59 s/mm: as Kaz mentioned we should start with use cases// 12:13:06 i/getting/scribenick: kaz/ 12:13:07 proposal: Accept Michael Koster as an Invited Expert for the WoT IG. 12:13:28 mm: Does it need to fill a form? 12:13:31 i/I guess/scribenick: luca_barbato/ 12:13:33 resolution: Accept Michael Koster as an Invited Expert for the WoT IG. 12:13:38 kaz: It can be accepted quickly 12:14:01 s/It can/He has already submitted one, and it can/ 12:14:22 q+ 12:14:26 i/proposal:/topic: Invited Experts/ 12:14:26 mm: The invited expert policy require the expert to be actively involved to producing the standard 12:14:37 q+ 12:14:52 mm: Did you reach out them already Kaz? 12:15:43 gkellogg has joined #wot 12:16:05 Kaz: I will contact two candidates 12:16:30 topic: Minutes 12:16:47 present+ Daniel_Peintner 12:17:08 -> https://www.w3.org/2024/05/15-wot-minutes.html May-15 12:17:14 mm: The general policy is to review them ahead of time, but today we can review it now. 12:17:29 q? 12:17:33 ack e 12:17:34 ack k 12:17:44 12:19:45 mm: Any other comments? 12:19:54 mm: Objections to publish? 12:19:57 12:20:05 topic: Quick Items 12:20:26 mm: We are now officially started, the email got sent 12:21:19 topic: Errata 12:21:37 mm: Ege did you start writing a policy proposal in this regard? 12:21:47 ege: I'll prepare it later 12:22:15 ege: I prepared some PRs for Architecture, TD, 12:22:24 ... and Discovery 12:22:27 https://github.com/w3c/wot-thing-description/pull/2023 https://github.com/w3c/wot-architecture/pull/946 https://github.com/w3c/wot-discovery/pull/547 12:23:16 rrsagent, make log public 12:23:20 rrsagent, draft minutes 12:23:21 I have made the request to generate https://www.w3.org/2024/05/22-wot-minutes.html kaz 12:23:34 mm: When you are ready we'll review all 12:23:39 topic: Notices 12:23:47 mm: Anybody has notices about anything? 12:23:51 topic: Meetups 12:24:15 mm: The CG group has an upcoming meeting 12:24:33 mm: Sadly it overlaps with other meetings so I cannot make to it 12:24:48 ege: We can talk but there always conflicts in the schedule 12:25:25 ege: The meetup we had on Solid and we discovered that one of the luggage control has WoT in production 12:25:36 https://www.youtube.com/watch?v=x6vnqo4j1tA 12:25:43 chair: McCool, Koster 12:26:06 mm: It would be helpful to have more information on adoption 12:26:42 ege: It is sort of tricky to list them since it would be promoting companies, we need agreement within the group 12:26:45 q+ 12:27:19 q+ 12:27:21 ege: The people from the Solid CG asked interesting questions during the meeting 12:27:25 q+ 12:27:53 ege: They also use Discovery and they have bluetooth binding 12:28:17 mm: also Home Assistant has something to wire bt over wifi 12:29:39 ack lu 12:29:50 lu: Marketing-wise we need a public list of adopters to convince more people 12:30:00 mm: Let's discuss it in the Marketing TF 12:30:17 ack ste 12:30:47 Tim: For the WebRTC we did a marketing thing and we got companies to write testimonials 12:31:00 ... and that was done by the W3C. 12:31:16 mm: We did something similar 12:31:39 mm: We need a mechanism to keep track of the adopters, but that's a Marketing TF task 12:32:17 kaz: In addition to Marketing purposes we would also contact the adopters for more UC 12:32:35 q+ 12:32:37 subtopic: WoT JP CG 12:32:44 mm: Any updates? 12:32:55 ack k 12:32:58 kaz: Miz is not available today so no news 12:33:12 s/UC/UC. Also possible joint meeting and breakout during TPAC./ 12:33:30 mm: We should think of more F2F meetings in Asia 12:33:41 topic: Cancellations 12:33:50 q+ 12:34:16 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations_and_Schedule_Updates Cancellations 12:34:19 mm: We have few cancellations and we will have more on July 12:34:56 ack dape 12:35:24 12:35:43 gkellogg has joined #wot 12:36:19 topic: Publication Milestones 12:36:47 mm: No changes over the schedule, we should add intermediate goals 12:37:02 i|No c|-> https://github.com/w3c/wot/blob/main/planning/schedule.md schedule.md| 12:37:06 mm: We should either restart Discover or moving its milestone 12:37:12 q+ 12:37:27 topic: Publications 12:37:39 mm: Anything new regarding the binding template Note 12:37:39 q+ 12:37:44 ack k 12:37:45 ack e 12:37:55 ege: We waited 2 weeks, now it is over 12:38:12 .. only one feedback to fix a figure 12:38:13 https://github.com/w3c/wot-binding-templates/pull/367 12:38:20 .. we have a PR 12:38:32 .. no other issue 12:39:13 mm: We can confirm the publication including the PR or merge the PR and make a resolution 12:39:13 i|Anything|-> https://lists.w3.org/Archives/Member/member-wot-wg/2024May/0001.html Ege's call for review on May 8| 12:39:34 proposal: To confirm TD TF Resolution https://www.w3.org/2024/05/02-wot-td-minutes.html#r01 publish and publish updated Binding Template WG Note. 12:39:50 mm: Any objections? 12:39:59 proposal: To confirm TD TF Resolution https://www.w3.org/2024/05/02-wot-td-minutes.html#r01 publish and publish updated Binding Template WG Note based on the current Editor's draft. 12:40:14 proposal: To confirm TD TF Resolution https://www.w3.org/2024/05/02-wot-td-minutes.html#r01 to publish updated Binding Template WG Note based on the current Editor's draft. 12:40:27 mm: Any objections? 12:40:36 12:40:37 resolution: To confirm TD TF Resolution https://www.w3.org/2024/05/02-wot-td-minutes.html#r01 to publish updated Binding Template WG Note based on the current Editor's draft. 12:41:01 topic: TF Discussion 12:41:04 i|Anything|-> https://www.w3.org/2024/05/15-wot-minutes.html#r01 Basic resolution on May 15| 12:42:18 subtopic: The Security activities can be offloaded to the other TF 12:42:34 s/subtopic:/mm: 12:43:20 mm: Mahda you were interested, but I guess you also have time constraints 12:43:32 s/Mahda you/Mahda, you/ 12:43:55 mahda: We can make a try to tackle the security concerns in the other TF 12:44:10 mm: I'm ok with this plan 12:44:47 q? 12:45:39 mm: Regarding Discovery, we need to understand what we it is left to be done and get feedback from the larger ecosystem. 12:45:50 mm: We should get more input 12:46:04 cris has joined #wot 12:46:25 mm: If pressing needs for discovery I can return as TF lead 12:46:44 q+ 12:46:50 mm: At the very least Discovery should support TD 2.0 so once TD 2.0 is ready we need need to update 12:47:14 kaz: Do we need to concentrate on getting a new TF leader for Discovery? 12:47:31 mm: Yes, Security can be postponed further 12:47:31 ack k 12:48:11 kaz: The most pressing task is surveying other standards' discovery practices? 12:48:16 mm: Yes 12:48:23 present+ Cristiano_Aguzzi 12:48:30 kaz: Do we want to wait another week? 12:48:49 topic: JSON Schema 12:49:26 q+ 12:49:36 mm: Ege wrote our point in the issue 12:49:52 i|Ege|-> https://github.com/w3c/strategy/issues/108#issuecomment-2082109340 Ege's input on strategy issue| 12:49:58 https://github.com/w3c/strategy/issues/108#issuecomment-2082109340 12:50:10 mm: Do we have updates on it? 12:50:15 ege: No 12:50:20 s|https://github.com/w3c/strategy/issues/108#issuecomment-2082109340|| 12:50:36 mm: We may have a possible breakout session at TPAC? 12:50:46 ege: TPAC is too further in time 12:51:13 ege: We do not have much to discuss and it is a W3C-wide issue 12:51:29 mm: I meant making a meeting about schemas in general 12:51:33 q+ 12:52:17 s/ege: No/ege: No. So would Kaz to talk within the Strategy Team about this. 12:52:22 rrsagent, draft minutes 12:52:24 I have made the request to generate https://www.w3.org/2024/05/22-wot-minutes.html kaz 12:52:30 ege: Our issue with JSON Schema is that we rely on it for our Data Schema 12:52:34 present+ Jan_Romann 12:53:07 mm: So there are two issues, one is validation and one is JSON Schema standardization 12:53:09 JKRhb has joined #wot 12:54:15 ege: Schema-validation it an easier issue, our linkml experiment is leading to produce multiple protocols for that 12:54:28 s/it an/is an/ 12:54:31 gkellogg has joined #wot 12:54:47 ack lu 12:55:23 lu: I'm against making normative any validation system 12:56:25 q? 12:56:27 lu: We cannot require implementation to use anything specific to do the validation 12:57:08 kaz: You may want to give me an action item to discuss with the Strategy Team 12:57:22 mm: If you can put it on the agenda would be great. 12:57:38 action: kaz to talk with the Strategy Team about JSON Schema standardization 12:57:50 topic: Update 12:58:14 s/Update/F2F updates/ 12:58:18 -> https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_planning F2F wiki 12:58:20 mm: Sebastian is not available, so we cannot get updates 12:58:47 q+ 12:59:34 mm: We may have additional event/days around the already set days for the F2F Meeting in November 13:00:16 kaz: I'm ok with the basic plan, we can start to think regarding the organization timeline 13:00:52 kaz: What we can do for the June F2F virtual meeting? 13:01:06 mm: We might drop the June event 13:01:12 proposal: drop the plans for the virtual June 2024 F2F. 13:01:21 q+ 13:01:25 s/regarding/about/ 13:01:25 ack k 13:01:29 q+ 13:01:45 cris: Not a big objection, but we might wait for Sebastian 13:01:48 ack cr 13:01:57 lu: +1 13:02:03 ack luca_barbato 13:02:15 mm: More comments? 13:02:52 mm: Please fill the table in the wiki 13:03:32 -> https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_planning#Participants_%28needs_to_be_updated%29 participation table for Nov meeting 13:03:52 [adjourned] 13:03:56 rrsagent, draft minutes 13:03:57 I have made the request to generate https://www.w3.org/2024/05/22-wot-minutes.html kaz 13:13:44 gkellogg has joined #wot 13:47:18 gkellogg has joined #wot 14:01:09 gkellogg has joined #wot 14:04:29 dape has joined #wot 14:06:12 mahda2 has joined #wot 14:21:41 kaz has joined #wot 14:29:08 gkellogg has joined #wot 14:48:07 gkellogg has joined #wot 15:06:07 Zakim has left #wot 15:08:18 gkellogg has joined #wot 15:28:25 gkellogg has joined #wot 15:41:13 gkellogg has joined #wot 15:59:18 gkellogg has joined #wot 16:30:21 gkellogg has joined #wot 16:48:40 gkellogg has joined #wot 17:24:15 gkellogg has joined #wot 17:55:24 gkellogg has joined #wot 18:04:52 gkellogg has joined #wot 20:51:36 gkellogg has joined #wot 21:26:39 gkellogg has joined #wot 21:59:41 gkellogg has joined #wot 22:18:55 gkellogg has joined #wot 22:22:31 gkellogg has joined #wot 22:54:40 gkellogg has joined #wot 23:13:37 gkellogg has joined #wot 23:30:43 gkellogg has joined #wot 23:56:52 gkellogg has joined #wot