12:59:41 RRSAgent has joined #wot 12:59:46 logging to https://www.w3.org/2023/12/20-wot-irc 12:59:46 meeting: WoT-WG/IG 13:00:00 present+ Kaz_Ashimura, Michael_McCool, Luca_Barbato 13:01:38 topic: Agenda 13:01:55 present+ Ege_Korkan 13:02:00 present+ Michael_Koster 13:02:04 Ege has joined #wot 13:02:12 rrsagent, make log public 13:02:16 rrsagent, draft minutes 13:02:18 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:04:21 sebastian has joined #wot 13:04:35 mjk has joined #wot 13:04:41 present+ Sebastian_Kaebisch, Tetsushi_Matsuda 13:04:58 matsuda has joined #wot 13:06:27 scribenick: sebastian 13:06:46 topic: Minutes 13:06:49 topic: minutes 13:07:05 -> https://www.w3.org/2023/12/13-wot-minutes.html Dec-13 13:07:05 13:07:14 s/topic: Minutes// 13:07:24 s/topic: m/topic: M/ 13:07:56 q+ 13:08:06 MM: We need to fix to "any change" 13:08:19 ... shoul be versioned 13:08:28 s/shoul/should 13:08:59 Mizushima has joined #wot 13:09:21 Kaz: we need to clearify the Policy when we want to change the minutes 13:09:55 MM: It is wrong recorded in the minutes, so it should be fixed 13:10:23 MM: something else we need to change? 13:10:57 s/"any change"/"any changes" 13:11:18 ktoumura has joined #wot 13:11:28 Kaz: this change should be labeled as maintinance policy 13:11:41 MM: agree 13:12:07 MM: any objections? 13:12:14 no 13:12:19 minutes approved 13:12:30 s/this change should be labeled as maintinance policy/that should be clarified as the maintenance policy for the wot-resources repository./ 13:12:38 rrsagent, draft minutes 13:12:39 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:12:45 topic: Quick Updates 13:13:00 subtopic: End-of-year Agenda Archival 13:13:06 q+ 13:13:16 MM: will archive meeting agendas at the end of the year 13:13:24 subtopic: Nordic Chapter CG 13:13:42 q? 13:13:49 MM: there are around 20 people in the meeting 13:14:10 ... it was like a mini conference 13:14:25 ... missed one hour 13:14:34 s/agendas/agendas on the WoT main wiki/ 13:14:37 ack e 13:14:55 ... they switched to Swedish for doing organization things 13:15:46 q? 13:16:18 Kaz: they had around 10 topics 13:16:44 -> https://www.w3.org/community/smartcity-nordic/2023/12/13/meeting-18-dec-about-local-digital-twins-and-the-metaverse/ 13:16:51 ... we need to clearify the reason between the Nodrdic City and WoT WG 13:17:06 s|metaverse/metaverse Nordic CG's Dec-18 meeting agenda| 13:17:12 topic: Meeting Schedule Changes 13:17:14 s/reason/liaison/ 13:17:20 s/City/CG/ 13:17:27 dape has joined #wot 13:17:43 s/WoT WG/WoT WG. Let's continue discussion with their Chair separately by email./ 13:17:49 13:17:59 q+ 13:18:07 -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Holidays_and_Upcoming_Events 13:18:12 q+ 13:18:15 q- 13:18:16 q+ 13:18:47 EK: we need to change tentative to confirmed for the TD calls 13:18:57 ack e 13:18:59 ack k 13:19:13 Kaz_ security and discovery will start 15th of January? 13:19:21 s/Kaz_/Kaz:/ 13:19:24 s/Kaz_/Kaz: 13:19:33 MM: yes 13:19:34 ;-) 13:19:49 s/security and discovery/scripting, security and discovery/ 13:19:56 s/15th/on the 15th/ 13:20:03 13:20:07 s/January?/January. Right?/ 13:20:20 s/security/Just to make sure, security/ 13:20:21 subtopic: use cases 13:20:26 rrsagent, draft minutes 13:20:27 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:20:48 MM: Seem there was some confusion 13:20:50 present+ Kunihiko_Toumura, Tomoaki_Mizushima 13:21:02 q? 13:21:08 ... intention to the doodle was to find new time slot 13:21:29 ... even there is no new task force lead yet 13:21:38 i/slot/slot in parallel/ 13:21:44 ... hope, that there some volunteers 13:21:46 +q 13:22:03 -> https://doodle.com/meeting/participate/id/e9pR1vPd doodle 13:22:05 https://doodle.com/meeting/participate/id/e9pR1vPd/vote 13:22:08 q+ 13:22:14 q+ 13:22:28 ack d 13:22:48 ack s 13:23:05 s/doodle/doodle for use cases calls/ 13:23:28 DP: an email reminder would be good 13:23:35 MM: there was an email shared 13:23:41 q? 13:24:10 ack k 13:24:37 SK: welcome to apply as a Use Case moderator, should be not that time consuming 13:25:31 Kaz: I'm ok to start perliminary, but priority should be to find a moderater, even it takes longer as expected 13:26:02 topic: Charter 13:26:13 s/Charter/WG planning/ 13:26:25 MM: some topics have to be done 13:26:56 s/, even it takes longer as expected/. maybe we need to hold a doodle again if it takes longer than expected to find the moderator./ 13:26:58 ... e.g., policies, some open PRs, decissions about Twitter 13:27:23 ... we need to find some new TF leads 13:28:22 i/topic:/Kaz: note that the work for moderators might be busier than usual for a while to have initial discussion on the policy, template, workflow, etc., but would become easier in a few months./ 13:28:29 rrsagent, draft minutes 13:28:31 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:28:47 MM: we can think about a PlugFest during the Fiware Summit 13:28:51 q+ 13:29:13 ... it takes place in June, somewhere in Euurope 13:29:23 s/Euurope/Europe 13:30:27 Kaz: there is already another thread about a Fiware liasion. 13:31:45 q+ 13:32:47 dezell2 has joined #wot 13:32:51 present+ David_Ezell 13:32:57 present+ David_Ezell 13:33:09 ack kaz 13:33:10 ack se 13:33:16 present+ Daniel_Peintner 13:33:18 SK: I think its ok to record, so that we have an overview whats is going on 13:33:41 Kaz: @@@ 13:33:45 topic: Resources 13:34:29 s/@@@/We should think about all the related SDOs in addition to FIWARE, so let's say "need to void overlaps with related SDOs meetings, e.g., FIWARE."/ 13:34:33 rrsagent, draft minutes 13:34:35 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:34:41 MM: Jan is looking into the ontology rendering issue 13:34:54 q+ 13:35:00 ... there is also an empty TM html file 13:36:02 EK: we need to updated TM ttl file to make html work 13:36:14 ... Mahda has already provided a PR 13:36:28 s/updated/update/ 13:37:10 ... in the future we should think about versioning for the subsequent changes 13:37:13 chair: McCool, Sebastian, Koster 13:37:48 ... problem we linking a specific version in the TD spec 13:38:04 i/We should think/scribenick: kaz/ 13:38:12 MM: there is the option of an errata to update the link 13:38:19 i/Jan is l/scribenick: sebastian/ 13:38:55 rrsagent, draft minutes 13:38:56 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:39:33 EK: when we update the repository we need to touch the REC all the time, this is annyoing. 13:39:55 q? 13:40:28 MM: first of all we need to adjust the implemenation and have an errata 13:40:34 present+ Cristiano_Aguzzi 13:40:37 q? 13:40:52 present- Kaz:Ashimura 13:40:58 present+ Kaz_Ashimura 13:41:05 ... we can have link to the errata which have the latest links 13:41:40 dezell has joined #wot 13:42:05 ... we can warn the people in the errata document that they should use the updated URLs 13:42:33 EK: I can setup such a document 13:43:20 ack k 13:43:51 Kaz: I'm agree about this procedure. We should clearify the policy for the maintenance. What is related for TD 1.1 and what is relevant for TD 2.0 13:44:53 MM: Let's table this for now. Ege will provide a plicy document and lets dicuss this then 13:45:08 s/dicuss/discuss 13:45:19 q+ 13:45:21 topic: Meetups 13:45:27 s/I'm agree about this procedure. We should clearify the policy for the maintenance./I agree on the discussion, and wanted to suggest again we clarify our policy on how to maintain wot-resources./ 13:45:32 subtopic: WoT CG 13:46:03 s/TD 2.0/TD 2.0. If some of the problems are actual bugs for 1.1 specs, we need to record them within the errata files too./ 13:46:08 q? 13:46:31 ack e 13:46:40 EK: there was a presenation from Grundfos about WoT. Presentation and video are available 13:46:59 q+ 13:47:16 q+ 13:47:22 MM: Grundfos mention an ISO standard that uses WoT ontologies 13:47:24 q- later 13:48:05 ack e 13:48:27 rrsagent, draft minutes 13:48:28 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:49:02 EK: I send an email to get more information and contact person about the ISO standard 13:49:23 Kaz: Could be good candidate for a liasion 13:50:17 s/Could be good candidate for a liasion/after getting clarification based on Ege's message, I'll work with the W3C Liaison Team for the possible new liaison with the ISO group./ 13:50:26 rrsagent, draft minutes 13:50:27 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:50:54 q+ 13:51:08 topic: Liasion 13:51:12 subtopic: OPC UA 13:51:18 rrsagent, draft minutes 13:51:19 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:51:26 q? 13:52:20 q+ 13:52:27 q? 13:52:59 q+ 13:53:57 SK: starting the "OPC UA Binding for Web of Things", internally it is setup the formal procedure within OPCF 13:54:11 ... expect the WG begin of next year 13:54:33 MK: is the same time slot used? 13:54:42 SK: not discussed yet, would make sense 13:55:12 kaz: even though we won't have a joint deliverable, we need to think about how to proceed with our collaboration. From time to time, we (WoT WG) should let them know about our updates on Binding Template registry, etc. 13:55:14 Kaz: how does the colleberate look like? 13:55:21 ack k 13:55:25 ack mc 13:55:28 ack mj 13:55:46 s/kaz: even though we won't have a joint deliverable, we need to think about how to proceed with our collaboration. From time to time, we (WoT WG) should let them know about our updates on Binding Template registry, etc.// 13:55:48 kaz: even though we won't have a joint deliverable, we need to think about how to proceed with our collaboration. From time to time, we (WoT WG) should let them know about our updates on Binding Template registry, etc. 13:56:05 SK: OPCF will act indepenent since there is no joint deliverable 13:56:16 s/kaz: even though we won't have a joint deliverable, we need to think about how to proceed with our collaboration. From time to time, we (WoT WG) should let them know about our updates on Binding Template registry, etc.// 13:56:18 kaz: even though we won't have a joint deliverable, we need to think about how to proceed with our collaboration. From time to time, we (WoT WG) should let them know about our updates on Binding Template registry, etc. 13:56:28 rrsagent, draft minutes 13:56:29 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:57:05 i/even though/scribenick: kaz/ 13:57:09 scribenick: sebastian 13:57:13 rrsagent, draft minutes 13:57:15 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 13:57:24 ack mjk 13:57:53 SK: what I wrote in the charter that we can run together PlugFests 13:58:17 topic: TF reports 13:58:39 https://w3c.social/@wot 13:58:41 q+ 13:59:27 EK: Marketing TF decided to create Mastodon WoT account 13:59:56 https://github.com/w3c/wot-marketing/issues/461 13:59:59 s/account/account and the whole WoT WG also made a resolution for that direction last week/ 14:00:47 ... regarding this there are some PRs 14:01:29 ... we decided to keep the Twitter account and will link it on the WoT webpage 14:01:58 q? 14:02:51 luca_barbato has joined #wot 14:03:21 Kaz: We need to decide which way to go. I'm ok to have both. Ege, you can tell which one would be better in the future. 14:03:23 ack k 14:03:31 s/decide/see/ 14:03:58 EK: in the Marketing TF we decided to keep both. W3C MarComm is also ok with it. 14:04:21 14:05:10 14:05:32 s/for 10min/till 10min past/ 14:05:36 rrsagent, draft minutes 14:05:38 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:06:37 mlagally has joined #wot 14:06:52 zakim, who is on the call? 14:06:52 Present: Kaz_Ashimura, Michael_McCool, Luca_Barbato, Ege_Korkan, Michael_Koster, Sebastian_Kaebisch, Tetsushi_Matsuda, Kunihiko_Toumura, Tomoaki_Mizushima, David_Ezell, 14:06:55 ... Daniel_Peintner, Cristiano_Aguzzi 14:07:08 Can somebody please post the zoom link? 14:08:35 https://us02web.zoom.us/j/87183898009?pwd=UmVHZEpYTGdQbG1VMHVtQmxqUGMxdz09 14:09:06 s|https://us02web.zoom.us/j/87183898009?pwd=UmVHZEpYTGdQbG1VMHVtQmxqUGMxdz09|| 14:09:17 rrsagent, draft minutes 14:09:18 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:10:17 present+ Michael_Lagally 14:12:37 q? 14:12:46 s/Can somebody please post the zoom link?// 14:12:54 rrsagent, draft minutes 14:12:55 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:13:22 scribenick: Ege 14:13:34 q+ 14:13:50 topic: IG Charter Discussion 14:14:07 -> https://github.com/w3c/strategy/issues/440 Strategy issue 14:15:23 i|Strategy|subtopic: Strategy Issue for 3-mo extension| 14:15:36 mk: we need to finalize the scope 14:15:46 i/we need/subtopic: Scope 14:17:24 i/Scope/kaz: As you know, these days we need to create a Strategy repo issue for rechartering procedure, so I've creating one as above. Also asking for a 3-mo extension for the rechartering procedure. Will get approval tomorrow, and will send an advance notice message about that to the AC tomorrow./ 14:17:38 mk: supporting the WG 14:18:12 i|need to fi|-> https://w3c.github.io/wot-charter-drafts/wot-ig-2023-draft.html Draft IG Charter| 14:18:20 rrsagent, draft minutes 14:18:22 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:18:51 ... the changes to the scope is to take out the third point and update the second one 14:18:55 q? 14:19:05 i/supporting/(Koster goes through the bullet points on "Scope Summary")/ 14:19:07 q- 14:19:11 rrsagent, draft minutes 14:19:12 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:19:20 ... we will take out tutorials from the 4th point 14:19:27 i/As you know/scribenick: kaz/ 14:19:33 s/need to fi/scribenick: Ege/ 14:19:37 rrsagent, draft minutes 14:19:38 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:20:04 s/scribenick: Ege/need to fi/ 14:20:10 i/need to fi/scribenick: Ege/ 14:20:12 rrsagent, draft minutes 14:20:13 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:20:24 q+ 14:20:33 ... once we update the scope, we can better explain the relationship between groups 14:21:41 i|supporting the WG|Support the Web of Things Working Group 14:21:42 Organize and run interoperability and testing events, including events for specific vertical industries, to evaluate the current working assumptions in regard to the Web of Things 14:21:42 Reach out and collaborate with interested organizations, industry specific and infrastructure vendors, and communities in support of the Interest Group's mission 14:21:42 Develop supporting materials such as implementation guidelines and tutorials 14:21:43 Explore areas and identify work that is ready for transfer to the W3C Recommendation Track| 14:21:46 rrsagent, draft minutes 14:21:48 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:21:54 mm: the IG owns the website since we cannot transfer to the CG 14:22:14 q+ 14:22:34 q+ 14:22:46 ml: a couple of things. the IG is defining wg documents via use cases 14:23:14 ... also organizing plugfests so that we also show that WG specs are working in real life 14:23:30 ... bring people to the specification work in the WG 14:23:32 rrsagent, draft minutes 14:23:34 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:23:42 ... use cases can help with that 14:24:33 q? 14:24:36 ack ml 14:25:29 q+ 14:25:31 mk: bringing active people is good idea 14:25:51 q? 14:25:51 ml: we should not split requirements from use cases. Otherwise it stays a theoritical activity 14:25:55 mk: it makes sense 14:26:04 mm: yes we are doing that 14:26:28 ack mc 14:27:12 ack e 14:27:53 q+ 14:27:56 ek: just to be clear. The website is an IG resource, marketing TF is also an IG TF. CG cannot own a part of IG resource. We can however link to CG resources etc. 14:28:10 mk: right, that is what I remember as well 14:30:06 kaz: I agree with focusing on the scope 14:30:39 s/focusing on the scope/focusing on the scope, but would suggest we start with the "Scope Summary" as Koster originally mentioned./ 14:30:43 rrsagent, draft minutes 14:30:45 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:30:51 ack k 14:30:53 q+ 14:31:02 mk: Is social media part of website? 14:31:23 https://github.com/w3c/wot-charter-drafts/pull/134 14:31:25 q+ 14:31:54 sk: there is a PR from Ege that shows the relationship between the groups 14:32:11 i/Is social/(Koster adds comments on "Scope Summary" topics based on today's discussion)/ 14:32:14 ack se 14:33:26 mk: This is a nice diagram for discussion 14:33:45 mk: how does outreach work at the moment? 14:33:58 q: 14:34:01 q? 14:34:06 s/q:// 14:34:16 q+ 14:35:54 ack e 14:36:04 -> https://github.com/w3c/wot-charter-drafts/blob/8e0c4da38539f163085bcb7f5b81b9918d7011c1/relationship.md rendered relationship.md 14:38:15 kaz: we can merge this with a draft title. it is a great start 14:39:24 mk: yeah we can do that 14:40:29 s/ it is a great start/ it is a great start, but we still need to extract topics from this and put actual text to the IG Charter./ 14:40:44 ml: nice figures, thanks. 14:40:54 s/we can mer/if everybody is OK, we can mer/ 14:40:57 ml: we should stress the fact that we want to bring new people 14:40:58 rrsagent, draft minutes 14:41:00 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:41:12 q? 14:41:13 ack k 14:41:17 q+ 14:41:19 q+ 14:41:21 ack ml 14:42:01 ... so we should encourage people to contribute 14:43:24 ... writing a use case is already a burden for some 14:43:36 ack k 14:44:34 kaz: let's record Lagally's points on the Issue 122 14:45:12 q+ 14:45:34 mlagally_ has joined #wot 14:45:45 ack e 14:47:30 q+ 14:48:12 ack k 14:48:15 ek: we should not imply that the IG participation is necessary first 14:48:51 ml: we should just get new members, doesn't matter the group 14:49:04 i/we should/kaz: or clarify for what people should join the IG as part of the Scope discussion :)/ 14:49:13 ack ml 14:49:19 rrsagent, draft minutes 14:49:21 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:50:39 s/Issue 122/Issue 122. regarding the roles of related groups, let's discuss them based on the relationship.md separately./ 14:50:44 rrsagent, draft minutes 14:50:45 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:50:51 q? 14:50:55 q+ 14:51:04 ntd, sorry; ttyl (happy holidays!) 14:51:52 you too 14:54:22 merry xmas 14:54:43 subtopic: Plugfest and Testing PR (137) 14:54:53 q? 14:54:53 sk: testing is a wg activity so we make this clear 14:55:42 q? 14:55:47 ack k 14:56:24 mk: As sebastian mentioned, we should focus on interoperability events 14:57:01 q? 14:57:13 mk: Any remarks on the relationship document? 14:57:35 i/Any/kaz: given we just have 5 more minutes for today, we should not change the subtopic now but concentrate on the discussion on the "Scope Summary". Also we should make decision on whether we want to merge PR 134 or not./ 14:58:14 mk: Let's merge the relationship PR 14:58:24 ... so we can continue work on the charter 14:58:29 i/Any rema/subtopic: Relationship among WoT groups/ 14:58:31 ... aob? 14:58:34 rrsagent, draft minutes 14:58:35 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 14:59:08 [adjourned] 14:59:09 rrsagent, draft minutes 14:59:10 I have made the request to generate https://www.w3.org/2023/12/20-wot-minutes.html kaz 16:42:41 Mizushima has left #wot 17:02:08 Zakim has left #wot 17:15:52 bkardell_ has joined #wot