11:02:36 RRSAgent has joined #wot-profile 11:02:36 logging to https://www.w3.org/2022/10/19-wot-profile-irc 11:02:40 ryuichi has joined #wot-profile 11:02:41 meeting: WoT Profile 11:03:02 present+ Kaz_Ashimura, Ege_Korkan, Michael_Lagally, Michael_McCool, Sebastian_Kaebisch 11:03:39 Ege has joined #wot-profile 11:04:54 Mizushima has joined #wot-profile 11:05:27 present+ Ryuichi_Matsukura 11:05:40 scribenick: Ege 11:06:07 topic: Working Mode Proposal 11:06:21 ml: ben has objected the initial proposal 11:06:25 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_.28combined_Profile_.2B_Architecture.29_Oct_19th.2C_2022 11:06:36 s/ben /Ben / 11:06:55 present+ Tomoaki_Mizushima 11:06:56 ... I have a sent a proposal yesterday 11:07:40 ... the previous resolution stopped the profile work and Ben proposed to continue asynchronously 11:07:45 s/have a sent/have sent/ 11:07:52 mm: let's have a new resolution, aligning with Ben's proposal 11:08:23 proposal: The main focus of the architecture TF for the next four weeks is to achieve CR status of the architecture spec, so the profile call slots are temporarily used for architecture. To ensure rapid progress of the Profile specification, the Profile work continues asynchronously on github / email, with on-demand discussion in the architecture calls, in case of any blocking issue. 11:08:28 ml: is the proposed text fine? 11:08:37 q+ 11:08:46 -> https://lists.w3.org/Archives/Public/public-wot-wg/2022Oct/0015.html Lagally's response to Ben 11:09:13 q+ 11:09:45 ack e 11:10:04 ml: arch has high precedence, unless a blocking issue is in profile 11:10:27 ek: can we merge PRs or just allowing people to make pull requests and issues 11:10:37 ka: there is a bit of mix up here 11:10:54 ... I am not sure if profile slot would help with arch discussion 11:11:22 ... if you think it would help and accelarate so that we reach the REC in the charter, we should clarify that 11:11:33 ... that was the first issue 11:12:35 ... we should clarify the policy to work asynchronously first 11:12:47 s/clarify that/clarify the updated schedule for that purpose./ 11:12:49 mm: I think we can edit the proposal to say we do not merge PRs 11:13:55 ml: I think we can adapt the call content to the amount of work in hand. Now we have 10 PRs, so we have work to do. 11:14:27 s/we should clarify the policy to work/and then the second issue is about the Profile spec. If we want to continue the spec work for Profile, we should simply continue the discussion using this Profile slot. Or if we really want to go for asynchronous discussion using only GitHub, we should clarify our policy on decision making beforehand./ 11:14:44 s/asynchronously first// 11:15:14 q? 11:15:15 ack k 11:15:18 q+ 11:15:23 proposal: The main focus of the architecture TF for the next four weeks is to achieve CR status of the architecture spec, so the profile call slots are temporarily used for architecture. To ensure rapid progress of the Profile specification, the Profile work continues asynchronously on github / email, with on-demand discussion in the architecture calls, in case of any blocking issue. 11:16:41 ack k 11:16:52 ka: we should fix the schedule and policy before reaching a resolution 11:17:25 s/reaching a resolution/making the resolution/ 11:17:31 mm: we can have resolution by saying "no PRs will be merged" 11:17:39 ml: Let's look at the schedule 11:19:00 q+ 11:19:44 dape has joined #wot-profile 11:20:03 ka: It sounds like we need more work (meetings) in 4 weeks 11:21:44 ml: let's table this discussion, we can look into the profile and architecture this meeting 11:21:53 ml: we need these contributions to be merged 11:21:56 q+ 11:22:56 ka: we can revisit this in the arch call tomorrow 11:23:56 ml: we can have a discussion in the main call and resolution in the arch call 11:24:09 ek: what happens to the previous resolution in this case? cancelled? 11:24:24 ml: I think it is cancelled since he was not in the meeting and there was no consensus 11:24:31 ml: Any other opinion? 11:24:44 s/It sounds like we need more work (meetings) in 4 weeks/Sorry if my words sound severe but this proposed resolution asking for using four additional calls for Architecture sounds like "It aches much, so please give morphine." So I'd like clarification for the feasibility of the updated schedule./ 11:24:53 ack k 11:25:02 ml: Michael and Sebastian, can we update the schedule in the main call? 11:25:11 s/he was not/Ben was not/ 11:25:14 mm: yes we will look into it 11:25:21 topic: Minutes Review 11:26:12 ml: Anything to change in the minutes? 11:26:22 ml: minutes are approved 11:26:27 i|Anything|-> https://www.w3.org/2022/10/12-wot-profile-minutes.html Oct-12| 11:26:34 ml: we can look into the other minutes tomorrow 11:26:38 topic: PRs 11:26:44 subtopic: PR 304 11:27:21 ml: I have put the contributions together into one csv file 11:27:28 ... so we have oracle and krellian 11:27:46 ... so it is something like an implementation report 11:28:12 i|I have put|-> https://github.com/w3c/wot-profile/pull/304 PR 304 - Profile Implementation status after Oct. test+plugfest| 11:28:41 sk: where is the node-wot results? 11:28:56 ml: I did not see any input but there was a discussion about it 11:29:37 dp: I did like ben, it is going into testing 11:31:09 ml: lots of places to input, we should fix it for the next plugfest 11:31:26 present+ Daniel_Peintner 11:31:29 rrsagent, make log public 11:31:33 rrsagent, draft minutes 11:31:33 I have made the request to generate https://www.w3.org/2022/10/19-wot-profile-minutes.html kaz 11:32:05 chair: Lagally 11:32:05 dp: we do not have eventing though 11:32:07 rrsagent, draft minutes 11:32:07 I have made the request to generate https://www.w3.org/2022/10/19-wot-profile-minutes.html kaz 11:33:23 ml: we should merge PR 445 in testing repository 11:34:38 q+ 11:34:59 ack e 11:35:02 ack d 11:35:27 dp: I have seen PRs that change the manual csv so we should be clear 11:35:29 -> https://github.com/w3c/wot-testing/pull/445 wot-testing PR 445 - add initial Profile results for node-wot 11:35:41 s|-> https://github.com/w3c/wot-testing/pull/445 wot-testing PR 445 - add initial Profile results for node-wot|| 11:35:46 sebastian has joined #wot-profile 11:36:03 ack dape 11:36:06 i|I have|-> https://github.com/w3c/wot-testing/pull/445 wot-testing PR 445 - add initial Profile results for node-wot| 11:36:17 ml: yes it is correct, there was a suggestion to remove the event assertions but we are not doing it to see the full picture 11:36:53 i|I have seen|-> https://github.com/w3c/wot-profile/pull/295 PR 295 - Prepare Testfest/Plugfest - informative assertion markup - generate manual.csv| 11:37:06 subtopic: PR 295 11:37:20 ml: we should close this one since it is superseed by others 11:37:48 s/subtopic: PR 295// 11:38:03 i|generate ma|subtopic: PR 295| 11:38:28 subtopic: PR 296 11:39:02 -> https://github.com/w3c/wot-profile/pull/296 PR 296 - full list of assertions, including those for informative SSE and Webhook profiles 11:39:13 (merged) 11:39:29 subtopic: PR 301 11:39:52 -> https://github.com/w3c/wot-profile/pull/301 PR 301 -fixing subprotocol id 11:40:25 ml: let's merge this one 11:40:39 (just editorial fix) 11:40:55 subtopic: PR 303 11:41:04 -> https://github.com/w3c/wot-profile/pull/303 PR 303 - Add Ben Francis as Spec Co-Editor 11:41:15 q+ 11:42:04 q+ 11:42:06 ack e 11:43:18 q+ 11:43:20 ek: We had a discussion on this in the td call and we lacked a policy 11:43:54 q- later 11:43:55 mm: we will talk about this in the main call and have a resolution 11:43:56 ack s 11:44:04 ml: but can we merge it? 11:44:28 mm: we can merge it but it would be better to have a resolution in the main call 11:45:11 sk: we want to use the contributors list from github 11:46:11 ... and also who participates in discussions 11:46:21 ka: we should not use krellian but invited expert 11:46:34 McCool_ has joined #wot-profile 11:47:06 ml: we are all agreeing to merge this PR 11:47:29 ml: congrats to ben 11:47:34 subtopic: PR 305 11:47:52 ml: digest and bearer were not implemented 11:48:15 s/we should not use krellian but invited expert/I've just updated the PR with Ben's ID, but we should use "Invited Expert" as his affiliation. Regarding the policy for Editors, it would be nicer to make an explicit resolution during the main call based on what we've been doing as McCool and Sebastian mentioned./ 11:48:21 q+ 11:48:24 rrsagent, draft minutes 11:48:24 I have made the request to generate https://www.w3.org/2022/10/19-wot-profile-minutes.html kaz 11:48:24 ack k 11:49:05 i|digest|-> https://github.com/w3c/wot-profile/pull/305 PR 305 - Remove unused security schemes| 11:49:13 rrsagent, draft minutes 11:49:13 I have made the request to generate https://www.w3.org/2022/10/19-wot-profile-minutes.html kaz 11:49:27 q+ 11:49:39 ack e 11:49:41 ack m 11:50:41 ek: I think there are still a lot of variation on this 11:50:50 mm: I agree. We can start with a smaller set still 11:51:02 -> https://github.com/w3c/wot-profile/issues/221 Issue 221 - Security Schemes are too loose 11:51:03 ml: we can constrain further 11:51:37 ml: we can merge this one, I think we all agree 11:52:45 topic: Architecture 11:53:02 subtopic: PR 858 11:53:39 -> https://github.com/w3c/wot-architecture/pull/858 wot-architecture PR 858 - Finalize IR and at-risk items 11:53:57 mm: we have agreed to not have links in abstracts 11:55:01 mm: I have run tidying tools on it as well and we see all implementation names 11:55:30 mm: outside of privacy and security assertions, only 2 are at risk 11:57:23 ml: I would like to have more time to review 11:58:45 subtopic: APA Questionnaire 12:00:26 mm: we did this questionnaire already, we should take the results 12:01:51 i|we did this|-> https://github.com/w3c/wot-architecture/issues/796 wot-architecture Issue 796 - Accessibility (APA) review| 12:02:03 mm: did we create an issue on their repo? 12:02:05 ml: let's see 12:02:50 https://github.com/w3c/a11y-request/issues/23 12:03:19 s/this ques/the APA ques/ 12:03:39 s/https/-> https/ 12:04:04 s|23|23 a11y-request Issue 23 - Web of Things (WoT) Architecture 1.1 2022-04-03 > 2022-06-30| 12:04:27 ml: AOB? 12:04:33 ml: adjourned 12:05:45 rrsagent, draft minutes 12:05:45 I have made the request to generate https://www.w3.org/2022/10/19-wot-profile-minutes.html kaz 12:06:52 Mizushima has left #wot-profile 14:03:57 Zakim has left #wot-profile