10:59:44 <RRSAgent> RRSAgent has joined #wot-arch
10:59:48 <RRSAgent> logging to https://www.w3.org/2023/01/12-wot-arch-irc
11:02:49 <kaz> meeting: WoT Architecture
11:02:57 <kaz> present+ Kaz_Ashimura, Michael_Lagally
11:03:01 <kaz> chair: Lagally
11:05:10 <kaz> present+ Tomoaki_Mizushima
11:06:24 <kaz> present+ Michael_McCool
11:06:52 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_Jan_12th.2C_2023
11:07:03 <McCool> McCool has joined #wot-arch
11:08:16 <kaz> scribenick: kaz
11:08:54 <kaz> topic: Minutes
11:09:06 <kaz> -> https://www.w3.org/2022/12/22-wot-arch-minutes.html Dec-22
11:09:57 <sebastian> sebastian has joined #wot-arch
11:12:45 <kaz> approved
11:13:04 <kaz> topic: Wiki clean-up
11:13:23 <kaz> -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_Jan_12th.2C_2023 Architecture wiki
11:13:31 <kaz> ml: (goes through the Architecture wiki)
11:14:05 <kaz> ... archival of last year's content
11:14:22 <kaz> mm: like the main wiki, we can archive old contents
11:14:44 <kaz> ... would suggest we use the same name convention as the main wiki
11:15:14 <kaz> ... just added a leading slash like "/2021"
11:15:34 <McCool> s/leading/trailing/
11:15:35 <kaz> -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf main wiki
11:16:07 <McCool> s/trailing slash/leading slash before the year/
11:16:31 <kaz> ml: let's go for it
11:16:57 <kaz> ... let's create a GitHub issue for that
11:17:23 <kaz> -> https://github.com/w3c/wot-architecture/issues/889 Issue 889 - Cleanup Wiki pages
11:17:47 <kaz> mm: can handle it since I need to do it for the main call too
11:18:08 <kaz> topic: Publication schedule
11:18:25 <kaz> -> https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md wg-2021-extension-plan.md
11:19:07 <kaz> mm: when to publish the CR drafts?
11:19:18 <kaz> kaz: planning to publish TD and Architecture tomorrow
11:19:45 <kaz> ... regarding Discovery, need to talk with PLH, but if he's OK, we can publish it as well tomorrow
11:20:17 <kaz> mm: what about the Profile WD?
11:20:31 <kaz> kaz: also tomorrow
11:20:47 <kaz> ml: (updates the schedule based on the feedback)
11:20:53 <kaz> present+ Ryuichi_Matsukura
11:21:58 <kaz> (discussion on PR and REC transitions)
11:23:33 <kaz> ml: (add some more updates to the schedule based on the feedback)
11:24:48 <kaz> q+
11:27:08 <kaz> kaz: that implies the REC publication will be the end of June
11:27:20 <McCool> q?
11:27:20 <kaz> ... in that case, we should rather ask W3M for 5-mo extension instead 4
11:27:23 <kaz> ack k
11:27:43 <kaz> ... I'll talk with PLH about Charter extension today anyway
11:27:56 <kaz> ... so will ask him about his opinion about this point
11:27:58 <kaz> mm: yeah
11:28:02 <kaz> ... let's check with PLH
11:29:11 <kaz> i|that im|-> https://github.com/w3c/wot/pull/1048 wot PR 1048 - Update wg-2021-extension-plan.md
11:29:22 <kaz> topic: Testing
11:29:52 <kaz> -> https://w3c.github.io/wot-architecture/testing/report11.html WoT Architecture Implementation Report
11:30:40 <kaz> mm: there are some problems with test tooling
11:30:53 <kaz> ... but that should not impact the WoT Architecture spec
11:31:14 <kaz> subtopic: Dedicated call with implementers + developers
11:31:25 <kaz> ml: should we have a dedicated call with implementers + developers?
11:31:34 <kaz> mm: would be a good idea
11:31:46 <kaz> ... maybe one in English and another in Japanese
11:32:09 <kaz> ... not 100% sure if the current categorization of the assertions is good
11:32:19 <kaz> q+
11:33:08 <kaz> ack k
11:33:10 <kaz> kaz: agree
11:33:25 <kaz> s/current/Ege's/
11:33:57 <kaz> i|agree|-> https://github.com/w3c/wot-architecture/issues/888 Issue 888 - Evaluating At Risk Assertions|
11:34:32 <kaz> ... we can use Ege's analysis as the basis but should validate it and finalize the evaluation
11:34:46 <kaz> q+
11:35:12 <kaz> ack k
11:35:37 <kaz> kaz: let's have some discussion using a dedicated MD file based on Ege's analysis
11:35:54 <kaz> ... so that we can improve the analysis result using PRs later
11:35:59 <kaz> mm: good idea
11:36:19 <kaz> ml: (creates an MD under wot-architecture/testing)
11:37:14 <kaz> -> @@@ at-risk feature evaluation
11:44:52 <kaz> q+
11:47:46 <kaz> (discussion on what we really meant for each assertion)
11:47:47 <kaz> ack k
11:49:16 <kaz> kaz: as already mentioned previously, using TD to express the device capability itself is a kind of abstraction of device interface
11:49:55 <kaz> ... so any WoT implementations should pass 34 and 35
11:50:36 <kaz> mm: that's true but there is an additional requirement for a security later for WoT runtimes
11:51:09 <kaz> kaz: in that case, probably we should clarify our expectation includes two levels, 1. using TD to express device capability and 2. additional abstraction for security purposes
11:52:04 <kaz> q+
11:54:22 <kaz> ack k
11:59:41 <kaz> kaz: to be strict, we should have clarified what part of each assertions to be implemented by whom (including external non-WoT systems)
12:01:16 <kaz> ... that could be explained by a guideline document as already proposed
12:01:40 <kaz> ... and potentially need to update the WoT Architecture spec itself in the future
12:02:15 <kaz> ... but we need clarification on what/how to test each feature from the current WoT Architecture 1.1 spec now
12:02:22 <kaz> ml: yeah
12:02:33 <kaz> ... let's continue the analysis
12:02:36 <kaz> [adjourned]
12:02:44 <kaz> s/[adjourned]//
12:03:05 <kaz> -> https://github.com/w3c/wot-architecture/pull/890 PR 890 - Update At-Risk-Requirements.md
12:03:10 <kaz> rrsagent, make log public
12:03:18 <kaz> rrsagent, draft minutes
12:03:19 <RRSAgent> I have made the request to generate https://www.w3.org/2023/01/12-wot-arch-minutes.html kaz
14:02:31 <Zakim> Zakim has left #wot-arch
15:07:37 <zkis> zkis has joined #wot-arch