12:02:06 RRSAgent has joined #wot 12:02:11 logging to https://www.w3.org/2023/05/17-wot-irc 12:02:28 meeting: WoT-WG/IG 12:02:47 MIzushima has joined #wot 12:02:58 present+ Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura, Luca_Barbato, Michael_Kostr, Sebastian_Kaebisch, Tomoaki_Mizushima 12:03:57 agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#17_May_2023 12:04:55 scribenick: sebastian 12:05:32 MM: there was a IE request 12:05:55 ... in the chairs call decided not to accept 12:06:35 MM: we have not guest today 12:06:48 s/not/no 12:06:53 topic: minutes 12:07:15 -> https://www.w3.org/2023/04/26-wot-minutes.html 12:07:41 s/minutes/review minutes from Apr-26 12:08:38 s/html/html Apr-26/ 12:08:41 MM: any updates or objections? 12:08:49 no, minutes approved 12:09:01 topic: Quick updates 12:09:03 i/there was/topic: Guests and IEs/ 12:09:11 subtopic: Cancellations 12:09:15 present+ Ege_Korkan 12:09:39 MM: next week is ambiguous 12:10:09 ryuichi has joined #wot 12:10:12 Kaz: he best possibility we might want to mention two weeks advance 12:10:24 s/he/the 12:10:39 MM: we need to make decission about Profile 12:11:04 present+ Daniel_Peintner, Ryuichi_Matsukura 12:11:12 ... Ben would be main contributor 12:11:52 MM: proposal suspend Profile work until the end of the Charter and then restart the new Charter. 12:11:59 s/the best possibility we might want to mention two weeks advance/We should put concrete date for each meeting. Note that sometimes we want to cancel meetings within two weeks./ 12:12:20 MM: any objections? 12:12:24 no 12:12:57 s/We need to make/We should put a specific deadline here, also/ 12:13:13 dape has joined #wot 12:13:13 subtopic: AC meeting debrief 12:14:35 Kaz: there was some discussion about internal W3C topics 12:14:37 ... if you are member there are minutes available 12:14:54 s/W3C topics/W3C topics, e.g., Legal Entity updates./ 12:15:07 s/member/a Member/ 12:15:13 topic: WG Charter review status 12:15:27 cris_ has joined #wot 12:15:51 -> https://github.com/w3c/strategy/issues/375 Strategy pipeline issue 375 12:16:02 MM: there was a comment about the rechartering 12:16:09 s/issue 375/issue 375 for WoT WG Rechartering/ 12:16:18 q+ 12:16:48 ... the comment is from APA 12:17:31 12:17:35 ack k 12:18:15 MM: I think, it is not a blocker on the Charter 12:18:35 ... expect a decission next week 12:18:51 present+ Cristiano_Aguzzi 12:18:59 q+ 12:19:31 ack k 12:19:42 s/decission/decision/ 12:19:55 Kaz: I created a wiki page for the Chair's role definition 12:20:10 ... only accessable for the chair candidates 12:20:21 s/wiki page/GitHub repo/ 12:20:35 topic: TPAC 2023 planning 12:20:54 -> https://www.w3.org/2002/09/wbs/1/GroupsTPAC2023/ TPAC 2023 questionnaire (Member-only) 12:21:09 MM: there was a questionnaire to provide the number of attendees and the planed joint meetings 12:21:43 12:23:04 ... currently we plan in persons 10 people 12:24:21 ... we need joint meetings between two groups 12:24:55 Kaz: there should be also extra chairs 12:26:18 s/two groups/two goups which requires corresponding room space 12:27:29 s/extra chairs/extra chairs for observers/ 12:28:17 MM: the WoT meetings are planned for Thursday and Friday, right? 12:28:19 Kaz: yes 12:29:12 MM: I thought there are 2x2h meetings each day 12:30:02 Kaz: depends on the agenda 12:31:23 s/agenda/agenda. For example, if we rather prefer holding our own vF2F meeting separately before or after the TPAC week, just having discussion in afternoon is ok./ 12:32:47 resolution: WoT WG/IG will have the joint F2F meeting during TPAC on Thursday/Friday only in the afternoon. 12:32:48 proposal: For TPAC 2023 qs response, change to two sessions each day, afternoon slots on Thursday and Friday. 12:32:54 s/resolution: WoT WG/IG will have the joint F2F meeting during TPAC on Thursday/Friday only in the afternoon.// 12:33:36 +1 12:33:40 resolution: For TPAC 2023 qs response, change to two sessions each day, afternoon slots on Thursday and Friday. 12:33:44 rrsagent, make log public 12:33:49 rrsagent, draft minutes 12:33:50 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 12:34:06 topic: Planning 12:34:11 chair: McCool/Sebastian 12:34:28 MM: we have to look at our schedule. 12:34:48 q+ 12:34:52 s|IG will have the joint F2F meeting during TPAC on Thursday/Friday only in the afternoon.//IG will have the joint F2F meeting during TPAC on Thursday/Friday only in the afternoon.|| 12:34:55 rrsagent, draft minutes 12:34:56 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 12:35:06 dezell has joined #wot 12:35:08 12:35:11 -> https://github.com/w3c/wot/pull/1089/files 12:35:15 present+ David_Ezell 12:35:56 MM: to be realistic, new charter will start in July 12:36:17 MM: is it ok to merge this PR? 12:36:18 i|we have to look|-> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md Schedule| 12:36:21 q? 12:36:23 ack e 12:36:29 rrsagent, draft minutes 12:36:30 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 12:36:47 no objections 12:37:17 Ege: the binding template publications date is outdated 12:37:33 s/no objections/ 12:38:14 q+ 12:38:28 Ege: there was already a call for resolution in March 13th 12:40:18 MM: lets ask for resolution agian here 12:40:39 proposal: After the merge of the two editorial PRs, the Binding Templates core document can be published: https://github.com/w3c/wot-binding-templates/pull/288 and https://github.com/w3c/wot-binding-templates/pull/286 12:41:04 -> https://www.w3.org/2023/03/29-wot-td-minutes.html March-29 TD minutes 12:41:25 s/resolution again here/call for resolution 12:42:26 Ege: there was also an email sent out 12:42:33 MM: any objections? 12:42:35 no 12:42:54 -> https://lists.w3.org/Archives/Member/member-wot-wg/2023Apr/0005.html Call for Review for Binding 12:43:29 resolution: After the merge of the two editorial PRs, the Binding Templates core document can be published: https://github.com/w3c/wot-binding-templates/pull/288 and https://github.com/w3c/wot-binding-templates/pull/286 12:43:42 +1 12:44:56 Ege: individual bindings are not part of the publications 12:44:56 -> https://github.com/w3c/wot-binding-templates/pull/288 PR 288 - Make XML Binding "planned" 12:45:20 -> https://github.com/w3c/wot-binding-templates/pull/286 PR 286 - Fix Editorial issues and examples 12:46:10 s/no/kaz: I'm OK with this resolution itself given those belated PRs are completely editorial, but we should confirm they're completely editorial./ 12:46:15 rrsagent, draft minutes 12:46:16 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 12:46:37 s|resolution: After the merge of the two editorial PRs, the Binding Templates core document can be published: https://github.com/w3c/wot-binding-templates/pull/288 and https://github.com/w3c/wot-binding-templates/pull/286|| 12:46:41 s/+1// 12:46:53 12:47:25 Kaz: please place a resolution again 12:47:53 MM: any objections about the PRs? 12:47:56 resolution: After the merge of the two editorial PRs, the Binding Templates core document can be published: https://github.com/w3c/wot-binding-templates/pull/288 and https://github.com/w3c/wot-binding-templates/pull/286 12:47:57 no 12:48:13 s/no/ 12:48:18 https://github.com/w3c/wot/pull/1089 changes dates, including start of next charter 12:48:24 i/After/(no objections)/ 12:48:29 rrsagent, draft minutes 12:48:30 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 12:48:36 proposal: Change the proposed start date of the next charter to July 1, 2023 12:48:46 +1 12:49:02 resolution: Change the proposed start date of the next charter to July 1, 2023 12:49:56 Kaz: the start / end date does not be edit in the charter. W3M will provide the dates 12:50:17 topic: Testfest 12:50:40 MM: Today we completed testing 12:50:58 12:51:36 -> https://github.com/w3c/wot-testing/tree/main/events/2023.03.Online 12:51:54 MM: Arch and TD in a very good shape 12:52:07 s|the start / end date does not be edit in the charter. W3M will provide the dates|We don't need to update the start/end dates every time, because the draft Charter says [[date of the "Call for Participation", when the charter is approved]].| 12:52:11 rrsagent, draft minutes 12:52:13 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 12:52:19 ... Discovery is a bit worse shape 12:53:03 ... however, we manage to the cought up the most things 12:54:52 12:55:06 [[ 12:55:08 Architecture 12:55:08 See the WoT Architecture 1.1 Developer Meeting Presentation for explanations of each at-risk assertion and current status. The number before each assertion is the number of implementations still needed to resolve them. 12:55:08 List of assertions to resolve (low priority): 12:55:09 (1) arch-security-consideration-hal-refuse-unsafe 12:55:09 Additional assertions which however have problems and we will retire without attempting to test: 12:55:10 (1) arch-security-consideration-use-psk 12:55:12 (2) arch-security-consideration-dtls-1-3 12:55:14 Thing Description 12:55:16 See WoT Thing Description 1.1 Developer Meeting Presentation for explanations of each at-risk assertion and current status. 12:55:19 List of assertions to resolve. 12:55:21 High Priority 12:55:23 All high-priority assertions have been resolved. See w3c/wot-thing-description#1813 12:55:25 Medium Priority 12:55:29 (1) privacy-immutable-id-as-property Intel to do 12:55:31 Lower Priority 12:55:33 Less-used features, guidelines 12:55:35 (2) td-security-oauth2-device-flow 12:55:37 (2) security-context-secure-fetch 12:55:39 Discovery 12:55:41 See WoT Discovery Developer Meeting Presentation for explanations of each at-risk assertion and current status. 12:55:44 The number before each assertion is the number of implementations still needed to resolve them. 12:55:46 High Priority 12:55:48 List of higher-priority assertions with at least one implementation: 12:55:50 (1) tdd-registrationinfo-expiry-config - Intel 12:55:50 MM: High and medium have 4 assertions left 12:55:52 These are in support of internationalization, and were added based on wide review, so should be a relatively high priority. 12:55:55 (2) tdd-http-alternate-language - Intel 12:55:59 (1) tdd-validation-response-lang - Intel 12:56:01 Medium Priority 12:56:02 proposal: Conclude testing and proceed with preparation of the PR draft for Architecture 1.1. 12:56:03 This is needed because if diff is ignored, result will be different than expected. However, it should be very easy to implement (if an implementation does not support diff, it just has to say so). Note that diff itself IS satisfied by other implementations already, so this is for those that do NOT implement it! 12:56:07 (2) tdd-notification-data-diff-unsupported - Intel, Logilab 12:56:09 Lower Priority 12:56:11 These have one implementation but are in security considerations and can be converted into "guidelines", so are a lower priority. 12:56:14 (1) sec-tdd-query-watchdog 12:56:16 (1) sec-tdd-intro-no-multicast 12:56:18 These have two but are also in security/privacy considerations and can be converted into "guidelines", so are also lower priority: 12:56:21 (2) sec-tdd-throttle-queries 12:56:23 (2) sec-tdd-limit-query-complexity 12:56:25 (2) sec-tdd-intro-limit-response-size 12:56:29 (2) sec-tdd-intro-throttling 12:56:31 (1) sec-self-proxy - Intel? 12:56:33 (2) priv-loc-disable-public-directories 12:56:35 (2) priv-loc-anonymous-tds - Intel? 12:56:37 (2) priv-loc-gen-ids - Intel? 12:56:39 (2) priv-loc-explicit-strip 12:56:41 (2) priv-query-anon 12:56:43 This is for security bootstrapping with OAuth, would be useful for onboarding: 12:56:45 (2) exploration-secboot-oauth2-flows 12:56:47 ]] 12:56:49 @@@ the style to be fixed later 12:56:55 proposal: Conclude testing and proceed with preparation of the PR draft for Architecture 1.1. 12:57:32 MM: any objections? 12:57:44 s|proposal: Conclude testing and proceed with preparation of the PR draft for Architecture 1.1.|| 12:57:45 no 12:57:47 resolution: Conclude testing and proceed with preparation of the PR draft for Architecture 1.1. 12:58:03 MM: same for TD: 12:58:19 q? 12:58:21 ack k 12:58:23 proposal: Conclude testing and proceed with preparation of the PR draft for TD 1.1. 12:58:25 q+ Ege 12:58:39 q+ 12:58:40 ack e 12:58:55 Ege: What happens if somebody actually submits a test input? 12:59:52 MM: if you have results until tomorrow, we could probably squeeze it in 13:00:01 proposal: Conclude testing and proceed with preparation of the PR draft for TD 1.1. 13:00:08 MM: any objections? 13:00:17 no 13:00:26 resolution: Conclude testing and proceed with preparation of the PR draft for TD 1.1 13:01:47 proposal: Conclude testing and proceed with preparation of the PR draft for Discovery 13:01:54 i/proposal:/kaz: Given (1) the original deadline was 2 weeks ago and (2) we're making resolution for Proposed Rec transition now, we should finalize the implementation report now. We still can accept implementation reports themselves any time./ 13:02:07 q+ 13:02:21 resolution: Conclude testing and proceed with preparation of the PR draft for Discovery 13:02:51 ack k 13:03:52 proposal: Each TF will be responsible for how to resolve remaining at-risk assertions, then there will be a one-week review of the final PR drafts. 13:04:17 resolution: Each TF will be responsible for how to resolve remaining at-risk assertions, then there will be a one-week review of the final PR drafts. 13:04:46 i/Each/kaz: fine with the resolutions to move ahead, but we should record how to proceed with the drafts for PR publication, e.g., removing features, making some of them informative, changing "MUST" to "must"./ 13:04:54 topic: next charter 13:04:55 rrsagent, draft minutes 13:04:57 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 13:05:35 i/Each/MM: OK. Let's record another resolution for that purpose./ 13:05:35 MM: we need to plan a meeting to organize next charter (schedule, planed deliverables, etc) 13:05:50 ... Kaz will provide a doodle 13:06:00 [adjourned] 13:06:01 adjourn 13:06:06 s/[adjourned]// 13:06:13 rrsagent, draft minutes 13:06:14 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 13:06:23 I have to go, see you in TD call 13:06:48 (Test call starts in 24 mins for quick updates) 13:06:51 rrsagent, draft minutes 13:06:52 I have made the request to generate https://www.w3.org/2023/05/17-wot-minutes.html kaz 13:33:00 MIzushima has left #wot 15:04:49 Zakim has left #wot