12:00:12 RRSAgent has joined #wot-profile 12:00:12 logging to https://www.w3.org/2022/11/16-wot-profile-irc 12:00:20 meeting: WoT Architecture/Profile 12:00:52 present+ Kaz_Ashimura 12:00:56 regrets+ McCool 12:01:02 present+ Michael_Lagally 12:02:38 present+ Ege_Korkan 12:03:33 Mizushima has joined #wot-profile 12:04:00 q+ 12:04:13 present+ Sebastian_Kaebisch 12:04:32 Ege has joined #wot-profile 12:04:40 sebastian has joined #wot-profile 12:05:07 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_.28Profile.29_Nov_16th.2C_2022 12:06:05 present+ Tomoaki_Mizushima 12:06:06 ML: 12:06:29 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf 12:06:52 i/shows/topic: Agenda/ 12:07:13 s/WebConf/WebConv#Architecture_.28Profile.29_Nov_16th.2C_2022/ 12:07:33 12:07:53 topic: Minutes 12:08:14 subtopic: Minutes 09 Nov 2022 12:08:25 -> https://www.w3.org/2022/11/09-wot-profile-minutes.html 12:08:45 q+ 12:09:36 ack k 12:09:48 Kaz: we review the minutes twice 12:10:04 s/html/html Nov-9/ 12:10:17 ML: any objections? 12:10:18 s/we/It seems we/ 12:10:21 no 12:10:38 subtopic: Minutes 10 Nov 2022 12:10:48 -> https://www.w3.org/2022/11/10-wot-arch-minutes.html 12:10:58 ML: any objections? 12:11:00 no 12:11:04 s/any/ML: some people can join only on Wed or Thu, so quickly skim both the minutes from Wed and Thu./ 12:11:19 s/html/html Nov-10/ 12:11:38 topic: Architecture 12:11:43 subtopic: Implementation report + CR status 12:12:27 s/Implementation report + CR status/PR 878/ 12:12:36 ML: Sebastian provided an PR about the CR exit statement 12:12:59 i|Seb|-> https://github.com/w3c/wot-architecture/pull/878 PR 878 - Provide CR exit statment in sotd section| 12:13:14 s/an/a 12:13:58 ML: How long is the CR review phase? 12:14:53 q+ 12:15:55 -> https://www.w3.org/2021/Process-20211102/#transition-cr W3C Process Document says "CR period at least 28 days" but it can be longer 12:16:12 SK: not 100% sure, I think min 1 month upto 2month 12:17:33 Kaz: the review phase is at least 28 days 12:18:54 Kaz: usually transition request should be done by the spec editor. Co-chairs and myself can help 12:19:12 ML: lets discuss this in the main call 12:21:01 12:21:21 s/lets/let's/ 12:21:29 Kaz: we should use this call to talk about the Arch topics 12:21:58 12:22:12 Kaz: suggest to discuss the testing result in the testing call 12:23:03 ML: I always wondering why we have different numbers of test results. 12:23:17 q+ 12:23:21 ack k 12:24:13 [ We've confirmed that Michael Lagally will work on the CR Transition Request for WoT Architecture and the Status Section (SoTD) for the exit criteria (the Chairs and the Team Contact will help) ] 12:24:35 subtopic: Implementation status 12:24:46 s/ML: I always wondering why we have different numbers of test results.// 12:24:48 ML: I always wondering why we have different numbers of test results. 12:25:23 -> https://w3c.github.io/wot-architecture/testing/report11.html draft Implementation Results 12:25:27 q? 12:25:27 ML: many security-based asserations missing 12:25:29 ack e 12:25:33 q+ 12:26:19 Ege: Does maybe Oracle support those features? 12:26:42 ML: Currently have poc for the Profile Spec. 12:28:22 Kaz: I do also not understand why this features are not implemented yet. 12:28:29 q+ 12:28:33 ack k 12:29:27 s/I do also not understand why this features are not implemented yet./I suspect report submitters don't really understand what the assertions really mean/ 12:29:45 Ege: maybe an explaination can be that there are different csv which have to be provided. Developer maybe are not aware of it. 12:29:58 s/mean/mean given "The WoT Runtime SHOULD NOT directly expose native device interfaces to the script developers." is not implemented./ 12:30:17 ack k 12:30:20 ack e 12:30:48 s/not implemented./not implemented. We need to ask all the submitters about their intentions again./ 12:30:53 ML: there are 10 implementations in the test folder, but the report has more 12:31:18 Ege: the report shows all WoT implementations that are invovled in the testing 12:31:31 s/explaination/explanation/ 12:32:41 ML: we should invite people to provide contributions 12:32:46 Ege: agree 12:32:53 q+ 12:33:35 ... it would be great to see your implementation also here 12:34:18 q+ 12:34:25 Kaz: we should check the current situation in the testing repo and should clearify what is missing. 12:34:28 present+ Ryuichi_Matsukura 12:34:32 ack k 12:35:22 ML: its hard to understand what should to do for testing 12:35:59 Ege: actually, there are READMEs and thosw works well in the past. 12:36:09 s/thosw/those 12:36:20 s/missing/missing first. after that, if some of the assertions which should have been covered already is not covered yet, we should explain what we really meant by each assertion to all the implementers and ask them to submit their results again./ 12:36:45 s/its/right. it's/ 12:36:54 s/should to do/should be done/ 12:37:08 12:37:14 s/thosw works/they worked/ 12:37:22 q? 12:37:24 ack e 12:37:42 rrsagent, make log public 12:37:45 rrsagent, draft minutes 12:37:45 I have made the request to generate https://www.w3.org/2022/11/16-wot-profile-minutes.html kaz 12:38:40 q+ 12:41:17 Kaz: The procedure is already defined by the process document. We should mention that we would like to have tow or more implementaion. 12:41:44 s/tow/two 12:44:18 ... if we want to use the arch 1.0 version result we should check the status there. 12:44:56 ML: I have a problem to reuse from the past also from members that are not members anymore 12:45:58 Kaz: we should be clear which features are new in Arch 1.1 and should be explained in the IR 12:46:31 q+ 12:47:17 ML: we do not test that we are backwards compatible 12:47:45 q+ 12:48:41 Kaz: it is ok when we define our own policy 12:48:47 ack k 12:48:49 ack e 12:50:00 Ege: I just agree what Kaz said 12:51:14 s/it is ok when we define our own policy/If we really want, we can define a policy to require WoT Architecture 1.1 implementations which cover all the features including both 1.0 compatible features and 1.1-specific features./ 12:51:20 q+ 12:52:19 SK: in my understanding, in the CR phase the IR needs not to be finalized 12:54:03 s/specific features./specific features. However, we can expect 1.0-compatible features are implementable based on the results of the WoT Architecture 1.0 Implementation Report./ 12:58:35 kaz: Anyway, given some of the simple/clear assertions like "abstraction of device interfaces" are not covered yet, we need to look into the test results themselves 12:59:27 ack s 13:03:46 Kaz: IR results is needed for the PR 13:04:22 ML: is the current version enough for the CR transition? 13:04:38 ack k 13:04:52 s/IR results is/IR results are/ 13:04:54 Kaz: I'm ok. the question is to check the results 13:05:17 I have some connection problems... 13:05:26 I cannot hear anything anymore 13:05:28 s/for the PR/for the PR transition, so we can continue the detailed check in parallel./ 13:05:59 ML: Unfortunately, we're out of time 13:06:41 ML: I'm going to merge this PR 13:06:50 s/ML: Unfortunately, we're out of time// 13:06:56 [adjourned] 13:07:02 rrsagent, make log public 13:07:05 SK: we will use the main call to talk about Profile PRs 13:07:08 adjourn 13:07:08 rrsagent, draft minutes 13:07:09 I have made the request to generate https://www.w3.org/2022/11/16-wot-profile-minutes.html kaz 13:07:20 s/[adjourned]// 13:07:21 rrsagent, draft minutes 13:07:21 I have made the request to generate https://www.w3.org/2022/11/16-wot-profile-minutes.html kaz 13:10:23 chair: Lagally 13:10:24 rrsagent, draft minutes 13:10:25 I have made the request to generate https://www.w3.org/2022/11/16-wot-profile-minutes.html kaz 14:46:22 kaz has joined #wot-profile 14:58:09 Mizushima has left #wot-profile 15:34:28 Zakim has left #wot-profile