13:01:01 RRSAgent has joined #wot 13:01:05 logging to https://www.w3.org/2024/03/06-wot-irc 13:01:06 luca_barbato has joined #wot 13:01:44 present+ Mahda_Noura 13:02:11 McCool_ has joined #wot 13:02:21 meeting: WoT-WG/IG 13:03:07 present+ Kaz_Ashimura, Michael_McCool, Ege_Korkan, Kunihiko_Toumura, Luca_Barbato, Michael_Koster,Tomoaki_Mizushima 13:03:32 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#6_March_2024 13:06:01 present+ Sebastian_Kaebisch 13:06:43 dezell has joined #wot 13:06:45 q+ 13:06:55 present+ David_Ezell 13:07:00 sebastian has joined #wot 13:07:02 topic: Guests, IEs 13:07:19 q? 13:07:58 gkellogg has joined #wot 13:08:19 scribe+ 13:08:34 MM: any new members or guests? 13:08:36 no 13:08:38 mm: no guests here but one possible IE application being discussed 13:08:42 topic: minutes 13:09:01 MM: reviewed them in yesterday's chair's call 13:09:13 i|rev|-> https://www.w3.org/2024/02/28-wot-minutes.html Feb-28| 13:09:13 any objections? 13:09:14 no 13:09:26 s/MM: any new members or guests?// 13:09:28 minutes approved 13:09:43 topic: Quick items 13:09:55 i/revie/scribenick: sebastian/ 13:10:00 rrsagent, make log public 13:10:07 rrsagent, draft minutes 13:10:09 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:10:16 q+ 13:10:16 MM: be awaere of the daylight saving changes 13:10:38 ... starts in US next week 13:11:00 [ the call starts one hour earlier in Europe and Japan ] 13:11:06 subtopic: IG charter 13:11:08 q+ 13:11:12 Ege_ has joined #wot 13:11:24 MM: wide review is ongoing 13:11:38 mjk has joined #wot 13:11:55 .. there are some comments 13:11:59 i|wide|-> https://github.com/w3c/strategy/issues/440 strategy issue 440 for the IG Charter| 13:12:07 scribe+ 13:12:12 kaz: will handle them 13:12:14 Kaz: there are missing tags 13:12:19 scribe- 13:12:23 ... will look into the bugs 13:12:33 s/kaz: will handle them// 13:12:45 i/there are/scribenick: sebastian/ 13:12:46 subtopic: W3C Breakout Day 13:12:50 rrsagent, draft minutes 13:12:51 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:13:14 matsuda has joined #wot 13:13:32 -> https://github.com/w3c/wot/issues/1178 Issue to gather ideas 13:13:33 MM: there are two calls, one is about schemata 13:13:51 .. another one is about registries 13:14:14 i|there are|-> https://github.com/w3c/breakouts-day-2024/issues/15 breakout issue 15 - Schemata Discussion - Follow up from TPAC23 13:14:42 i|there are|-> https://github.com/w3c/breakouts-day-2024/issues/18 breakout issue 18 - Registries for W3C Specifications| 13:14:48 rrsagent, draft minutes 13:14:49 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:15:27 13:15:32 q+ 13:16:10 EK: do you have people you want me to contact? 13:16:34 MM: would be good to know who is already invited? 13:17:19 ... would be good people from JSON Schema 13:17:40 and SHACL 13:17:44 q? 13:17:53 ... for the registry, DID would be good 13:19:07 q+ 13:19:19 ack k 13:19:33 Kaz: some more exoerts from other groups should be invited such as DID 13:19:46 s/exoerts/experts 13:19:48 ack 13:19:53 rrsagent, draft minutes 13:19:54 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:20:19 chair: McCool, Koster, Sebastian 13:20:31 q+ 13:20:42 DK: I chaired XML Schema Working Group, many people are now retired 13:21:16 present+ Tetsushi_Matsuda 13:21:23 q? 13:21:25 ack d 13:21:43 ... we should invite Piere Antoine (?) 13:22:28 subtopic: Profile 13:23:35 s/Piere Antoine (?)/the Team Contact of the DID WG/ 13:23:47 i/subtopic/kaz: that's Pierre-Antoine :)/ 13:24:01 MM: Profile starts next week 13:24:07 q+ 13:24:11 ack m 13:24:33 ack e 13:25:20 ... 12. March-13 UTC, however, this conflicts with the w3c breakout day 13:25:23 i/that's P/scribenick: kaz/ 13:25:34 i/Profile start/scribenick: sebastian/ 13:25:40 MM: ok, lets postpone profile call for one week 13:25:41 rrsagent, draft minutes 13:25:42 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:26:03 MM: is this ok for you, Luca? 13:26:22 LB: is ok for me 13:26:48 ... I will have a prepearation meeting with Michael Lagally this week 13:27:14 -> https://www.w3.org/events/meetings/97f4d945-dba3-4461-be33-f2cc110af348/20240319T080000/ WoT Profile Calendar 13:27:15 s/prepearation/preparation 13:27:30 topic: Meetups 13:27:58 subtopic: WoT CG 13:28:09 s/lets/let's/ 13:28:11 rrsagent, draft minutes 13:28:13 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:28:31 EK: next meeting is planned March 14 13:28:56 ... there is a presentation about Matter from Deutsche Telekom 13:29:03 q? 13:29:10 subtopic: WoT JP CG 13:29:24 q+ 13:29:25 MM: next meeting in 2 days 13:29:31 gkellogg has joined #wot 13:29:48 subtopic: Nordic Smart Cities and WoT CG 13:29:53 +1 13:30:00 MM: no news 13:30:04 s/meeting/meeting on WoT Security/ 13:30:08 .. next meeting March 18 13:30:19 s/+1// 13:30:46 Kaz: should move this to Liaisons section 13:30:53 MM: yes 13:31:17 subtopic: Other 13:31:46 EK: WoT presentation at the HiveMQ Community Event on March 26 13:32:00 topic: Meeting Schedule Changes 13:32:34 13:32:34 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Holidays_and_Upcoming_Events Holidays and Cancellations 13:33:03 MM: any holidays to be aweare of? 13:33:48 q+ 13:33:56 q? 13:34:06 ack k 13:34:17 q+ 13:34:36 Mar 12: 13:34:36 Defer start of Profile call to Mar 19. 13:34:36 Mar 20: 13:34:36 Use Case call is cancelled. 13:34:37 MM: is it ok cancel main call on March 20? 13:34:39 no 13:34:47 s/20/20 also/ 13:34:56 s/no/no objections 13:35:28 q? 13:35:48 sk: also we should think about Hannover Fair 13:36:01 ... because that's a very big industry show 13:36:23 i/also/scribenick: kaz/ 13:36:31 scribenick: mahda-noura 13:37:28 Topic: F2F Planning 13:38:49 sebastian: Web of Things event planned from Siemens standardization, and to show how WoT is used in products and industry ompared to the event in 2019 13:38:50 i|F2F|-> https://www.hannovermesse.de/en/hannover-messe-2024/ Hannover Fair 2024| 13:39:07 s/ompared/compared/ 13:39:16 ...he liked to plan this event in June, do we want to have beside this special event a plugfest? 13:39:27 q+ 13:39:54 dezell2 has joined #wot 13:39:57 ...in the chairs called last week we discussed about this, and wondered how many people will be able to travel to such an event considering the limited budget and travel restrictions of companies 13:40:09 s/he liked/my boss would like/ 13:40:22 ...we should think about this question and ask your company if its possible to travel 13:40:28 s/called last/call last/ 13:40:31 ...the event will take place in Berlin 13:40:40 q 13:40:53 mm: do we want to do an email survey? 13:41:13 sebastian: we could maybe setup a wiki page where people could mention their availability 13:41:24 mm: lets try to make a draft ready 13:41:33 s/lets/let's/ 13:41:45 ...I think we need to do a concrete proposal 13:42:09 ...I will be able to attend with high probability 13:42:37 ...There is some work I am involved with Microsoft regarding AI, we could have a AI theme too 13:42:57 sebastian: lets make a draft in the chairs call 13:43:08 mm: see who could do demos and talks 13:43:08 sorry, I have to leave the meeting 13:43:46 kaz: probably I agree we should clarify logistic and create a dedicated wiki page, for that purpose we need to clarify the estimated date and content and additional discussion 13:44:06 mm: we will create a wiki page and clarify those things and try to get all stakeholders to agree to the plan 13:44:18 Topic: Resources 13:44:20 s/probably // 13:44:29 mm: Is there any updates? 13:44:33 s/for that purpose/for that purpose, probably/ 13:44:46 rrsagent, draft minutes 13:44:47 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:44:54 ack k 13:45:04 q+ 13:45:07 ack s 13:45:21 q- 13:45:21 mm: my hope is that there will be eventually a policy regarding semantic versioning, the discovery is proceeding under a assumption on version policy 13:45:32 mm: is the TD TF taking a lead on this? 13:45:44 q+ 13:45:47 mjk: yes, we are expected to report in the next TD call 13:45:54 q? 13:46:38 mm: we updated our rendering in the discovery, the blue boxes are because of the domain and range not present, we recently transferred a issue under the TD directory for security ontology 13:46:44 mm: I suggest we fix that first 13:47:06 ege: we should have a good proposal in the next TD call 13:47:14 i|we updated|-> https://w3c.github.io/wot-discovery/context/discovery-ontology.html Web of Things (WoT) Discovery Ontology (Editor's Draft)| 13:47:22 ...the semantic versioning is only one small aspect of the versioning topic 13:47:32 q+ 13:47:35 ack e 13:47:55 https://github.com/w3c/wot-thing-description/pull/1969 13:47:59 ...today in the TD call, we will discuss what are the requirements for versioning 13:48:17 s/https/-> https/ 13:48:32 s/1969/1969 wot-thing-description PR 1969 - WIP: Concrete Versioning Proposal| 13:48:40 s/sal|/sal/ 13:48:46 rrsagent, draft minutes 13:48:47 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:48:54 mm: As part of our rendering of the ontology, we have a template, we also have a changelog, and the final resource will output the release 13:49:05 q 13:49:14 ...we need to do some work to align with the TD script 13:49:39 gkellogg has joined #wot 13:49:42 ege: we need to seperate the versioning from the toolchain for now, the versioning is about the outputs 13:49:56 mm: my intention is that the output needs to be consistent 13:50:51 kaz:Michael Mccool and the discovery guys have been working on a proposal, we should make a consolidation. We should also include David as an expert 13:51:07 kaz: would you be available for todays TD call or next week main call? 13:51:34 mm: lets wait until the work in progress policy is done, and in two weeks from now we plan and put on the agenda 13:52:05 s/todays TD call or next week main call?/today's TD call, tomorrow's TD call or main call next week?/ 13:52:09 mm: maybe 21st March to have a joint call 13:52:14 rrsagent, draft minutes 13:52:15 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:52:38 q? 13:53:25 mm: A note added on the agenda 13:53:31 s/joint call/joint discussion during the TD call/ 13:53:32 ack k 13:53:48 [ that is Mar 21 at 9am EDT ] 13:54:20 mm: does anyone else who wants to report on the TF reports 13:54:55 ege: we have an issue in finding a timesolt in the marketting call, once we consider the chairs and kaz it gets tricky 13:55:23 mm: proposal could be once a month you guys join the chairs call 13:55:28 i/we have/subtopic: Marketing TF/ 13:55:39 i/does any/topic: TF Reports/ 13:55:47 mm: lets dicuss this in the chair meeting next time 13:55:50 q+ 13:56:02 s/lets/let's/ 13:56:15 kaz: we probably need to do a doodle 13:56:35 mm: in the doodle add half an hour after the new chairs call as one of the options 13:56:38 action: kaz to create a doodle to find a possible slot for Marketing (first call of the month) 13:56:46 ack k 13:56:46 ege: I think it would fit well in the chairs call 13:57:28 mm: would be helpful to setup a doodle 13:57:35 q+ 13:57:36 ...any other reports? 13:57:58 ack e 13:58:06 q+ 13:58:27 ege: not only from the TD, but would affect others. The project management proposal is more concrete. We looked with Michael Koster and Kaz, I would send the rendered version and pull request 13:58:37 Rendered Version: https://github.com/w3c/wot-thing-description/blob/ege-project-management/proposals/project-management/project-management.md 13:58:38 mm: is it a policy? 13:58:44 ege: it is a process 13:58:49 PR: https://github.com/w3c/wot-thing-description/pull/1977 13:58:59 kaz: I would suggest to finalize the draft today in the TD call 13:59:16 s/call/call first, and then send it to the whole group/ 13:59:18 mm: maybe we can finalize the versioning and project management together in the main TD call 13:59:20 q? 13:59:22 ack k 13:59:26 rrsagent, draft minutes 13:59:27 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 13:59:36 subtopic: Architecture 14:00:10 q+ 14:00:34 mm: We will defer it until the profiles get going 14:00:54 ack k 14:00:57 kaz: we can discuss how to handle the architecture in the main call 14:01:15 mm: we should focus on giving profiles speed until we find someone to work on the architecture 14:02:23 gkellogg has joined #wot 14:03:19 s/we can discuss how to handle the architecture in the main call/We'll restart the Profile TF in two weeks, and the TF probably will discuss what to be done by the Profile TF and the Profile document, then bring the feedback to the main call. We can discuss how to handle the Architecture during the main call at that time./ 14:03:36 s/we should/right. we should/ 14:03:48 [ break till 10 mins past ] 14:03:50 topic: Policies 14:03:55 rrsagent, draft minutes 14:03:57 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 14:04:10 mm: let's go for 30m only since some people have to leave early 14:04:16 mk: ok 14:04:27 mjk has joined #wot 14:04:39 s/[ break till 10 mins past ]// 14:05:24 -> https://github.com/w3c/wot/labels/Policy Policy Issues and PRs 14:06:11 subtopic: Assertion IDs 14:06:12 https://github.com/w3c/wot/pull/1181 14:06:19 mk: PR #1181 14:06:32 s|https://github.com/w3c/wot/pull/1181|-> https://github.com/w3c/wot/pull/1181 PR 1181 - Assertion id policy proposal| 14:06:43 i/let's go for/scribenick: McCool_/ 14:06:47 rrsagent, draft minutes 14:06:48 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 14:07:07 ege: lots of variations in ids, not consistent 14:07:29 i|lots|-> https://github.com/w3c/wot/blob/cc1a8fee23fe3ca43e3f453d51647fa855acd027/proposals/policies/assertion-id.md rendered assertion-id.md| 14:07:32 rrsagent, draft minutes 14:07:33 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 14:07:39 ... for TD spec, agreed to always start with td or tm 14:07:59 q+ 14:08:22 ege: also, if there are subsections, best to include those 14:08:41 q+ 14:08:53 q? 14:10:17 mm: also, please don't use section *numbers* - they change! 14:10:30 ack m 14:10:40 ... also, don't do sub-sub-sections, just two levels is enough 14:11:02 ege: include doc prefix so can recognize if taken out of context 14:11:23 mm: agree; within a doc, redundant, but helpful if taken out of context 14:11:51 ... so agree with prefixes; also ok with both td and tm 14:12:01 +1 to kaz 14:12:43 kaz: could define a template, eg. PP-SS-DESC 14:12:46 q? 14:13:05 ... would also be good to define each prefix 14:13:15 mm: I think the prefixes are clear from context 14:13:40 ack k 14:13:56 kaz: editors and group participants can tell, but would be good to have a description 14:14:11 mm: where would the description go? 14:14:34 ... the implementation report? The readme? 14:14:48 q+ 14:15:37 q? 14:15:40 q+ 14:15:43 mjk: would make sense to make a little formal spec, maybe in the policy 14:15:52 q+ 14:15:56 ack mjk 14:16:36 ege: can add a bit to the current PR 14:16:49 mm: I think the current PR is moving in the right direction, however 14:17:33 kaz: for assertionid.md itself, would explain what's wrong with each incorrect example, how it should be fixed 14:17:57 ... but policy should also state that assertion id formats and prefixes should be defined in IRs 14:18:23 s/IRs/Implementation Reports/ 14:18:56 subtopic: Chair Decision Process 14:19:14 -> https://github.com/w3c/wot/pull/1128 PR 1128 - [Policy] Move chair-decision-process.md from "proposals" to "policies" 14:19:34 mm: I made the suggested changes, removed "voting" 14:19:45 -> https://github.com/w3c/wot/blob/62050f79d1cca5032b80e9b50c7fd707650f77de/policies/README.md rendered proposal 14:20:08 ... still have a 2/3 quorum 14:21:26 s|-> https://github.com/w3c/wot/blob/62050f79d1cca5032b80e9b50c7fd707650f77de/policies/README.md|https://github.com/w3c/wot/blob/62050f79d1cca5032b80e9b50c7fd707650f77de/policies/chair-decision-process.md| 14:21:40 s/https/-> https/ 14:21:44 mm: but should remove the "no more than a day earlier" 14:21:45 rrsagent, draft minutes 14:21:47 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 14:21:57 q+ 14:22:01 mjk: ok (removes clause) 14:22:04 ack m 14:22:43 kaz: quorum is still there 14:23:45 mm: yes; note that 1 chair can't make unilateral decisions 14:23:50 mjk: but two can 14:24:49 q? 14:25:10 kaz: opinion is that we should stick to consensus and just wait until we get all three 14:25:13 ack k 14:27:34 mm: suggest we add a line of the form "However, if possible, when a chair cannot attend..." 14:28:00 ... the "if possible" is to cover the case when we do have to make an immediate decision 14:28:54 kaz: what about team contacts input? 14:29:14 mjk: true, we haven't a problem 14:29:21 s/contacts/contact's/ 14:29:45 I need to go. See you in the TD call soon :) 14:30:06 q+ 14:30:20 s/I need to go. See you in the TD call soon :)// 14:30:21 q- 14:30:36 mm: suggest we don't merge this PR for now - can discuss further in chairs' call 14:30:49 mjk: out of time, adjourn 14:31:06 rrsagent, draft minutes 14:31:07 I have made the request to generate https://www.w3.org/2024/03/06-wot-minutes.html kaz 15:15:47 gkellogg has joined #wot 15:40:19 gkellogg has joined #wot 15:49:05 JKRhb has joined #wot 16:01:57 gkellogg has joined #wot 16:02:27 bigbluehat has joined #wot 16:16:34 gkellogg has joined #wot 16:18:19 JKRhb has joined #wot 16:39:49 Zakim has left #wot 16:43:26 JKRhb has joined #wot 18:25:07 gkellogg has joined #wot 19:09:31 gkellogg has joined #wot 19:22:09 gkellogg has joined #wot