14:01:08 RRSAgent has joined #wot-discovery 14:01:08 logging to https://www.w3.org/2022/07/18-wot-discovery-irc 14:01:35 Mizushima has joined #wot-discovery 14:01:48 glomb has joined #wot-discovery 14:02:32 meeting: WoT Discovery 14:03:12 ktoumura has joined #wot-discovery 14:03:15 present+ Kaz_Ashimura, Michael_McCool, Andrea_Cimmino, Christian_Glomb, Farshid_Tavakolizadeh, Kunihiko_Toumura, Tomoaki_Mizushima 14:04:41 q+ 14:05:55 ack k 14:06:41 FarshidT has joined #wot-discovery 14:06:43 scribenick: glomb 14:10:45 Minutes from last meeting - slight corrections, approved 14:10:52 i/Minutes/topic: Minutes/ 14:11:05 i|Minutes|-> https://www.w3.org/2022/07/11-wot-discovery-minutes.html July-11| 14:11:31 https://github.com/w3c/wot-discovery/pull/376 14:11:58 New assertion included - merged 14:12:01 i|376|topic: PR 376| 14:12:06 s/https/-> https/ 14:12:46 s/376/376 PR 376 - Add missing tdd-things-update-contenttype to manual.csv/ 14:14:29 topic: Testing 14:14:37 -> https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online 2022-July Testfest 14:14:51 Links in wot-testing/events/2022.07.Online corrected appropriately 14:17:30 Testing next week - check schedule & participation - Discovery call will be cancelled - logistics in https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online/README.md 14:19:37 manual.csv and test tool should be up-to-date, however assertions related to event filtering might fail 14:19:56 Event Filtering assertion should be fixed 14:20:22 -> https://w3c.github.io/wot-discovery/publication/3-wd/Overview.html#exploration-directory-api-notification 3-wd draft - 7.3.2.2 Events API 14:21:11 farshid: What if Event type is missing? - need clarifications 14:22:09 mmc asks farshid to open an issue / PR 14:22:44 Farshid will reword following assertion to make it clearer that it is conditional: "The server MUST support event filtering based on the event type given by the client upon subscription." 14:23:56 mmc - Implementations should be updated and both manual as well as auto assertion tests should be run 14:25:05 acimmino_ has joined #wot-discovery 14:25:36 https://github.com/w3c/wot-testing/blob/main/events/2022.07.Online/README.md 14:25:39 mmc - Currently ahead of schedule wrt. CR transition, no severe feedback gotten yet (especially wrt. security) 14:28:07 farshid - Will create new implementation report directory and update https://github.com/w3c/wot-testing/pull/362 14:30:37 Use links whenever possible (manual.csv and template.csv) 14:31:11 Publication preparation 14:32:41 -> https://www.w3.org/pubrules/ Pubrules checker 14:34:26 mmc: which Patent Policy to be used? 14:34:26 kaz - Should switch to new Patent Policy after approval 14:34:59 s/Should/For today, we should use the old one, and should/ 14:35:29 s/after approval/after getting the W3M approval for the new (extended) WG Charter./ 14:36:11 mmc - farshid should fix affiliation / hyperlink related to it 14:39:41 Links to "Hydra" are reported broken by the checker, even though they are not 14:40:41 kaz - Not considered an issue ... 14:41:27 i/Not considered an issue .../In that case, maybe that's caused by some additional tooling mechanism, so please don't worry./ 14:41:54 Tag review feedback 14:42:47 https://github.com/w3ctag/design-reviews/issues/736 14:43:23 Testable statements for Security and Privacy needed 14:44:18 s/Tag review feedback/topic: TAG Review feedback/ 14:44:26 s/https/-> https/ 14:44:41 mmc - E.g. "Denial of Service" - should be more precise 14:45:19 s|736|736 TAG Issue 736 - Web of Things (WoT) Architecture 1.1| 14:47:10 follow assertion might be considered a statement of policy: "If Things cannot be individually secured with transport security and authentication and authorization, a separate network SHOULD be set up, i.e. with an alternative SSID, and used only for IoT devices. " 14:49:38 mmc - Could have a separate section about "mitigation" or "downgrade to informative statements" 14:52:54 mmc - ... and mark them as proposals 14:54:58 mmc - However, security guys askes to make normative statements 14:55:18 mmc - But cannot make it an assertion if not test-able 15:01:03 i/Could have/kaz: ideally, we should describe within each feature description what is the expected behavior of each implementation of the WoT Discovery specification's feature based on the requirements, e.g., the mitigation description./ 15:12:55 i/ideally/scribenick: kaz/ 15:13:11 i/Could have/scribenick: glomb/ 15:13:14 [adjourned] 15:13:19 rrsagent, make log public 15:13:23 rrsagent, draft minutes 15:13:23 I have made the request to generate https://www.w3.org/2022/07/18-wot-discovery-minutes.html kaz 15:14:28 chair: McCool 15:14:29 rrsagent, draft minutes 15:14:29 I have made the request to generate https://www.w3.org/2022/07/18-wot-discovery-minutes.html kaz 15:14:56 i/which Pa/scribenick: kaz/ 15:15:03 i/For today/scribenick: glomb/ 15:15:14 s/ - /: / 15:15:18 rrsagent, draft minutes 15:15:18 I have made the request to generate https://www.w3.org/2022/07/18-wot-discovery-minutes.html kaz 15:15:41 i/In that case/kaz: In that case/ 15:15:46 i/In that/scribenick: kaz/ 15:16:10 rrsagent, draft minutes 15:16:10 I have made the request to generate https://www.w3.org/2022/07/18-wot-discovery-minutes.html kaz 16:51:49 kaz has joined #wot-discovery 18:31:14 Zakim has left #wot-discovery 23:34:27 kaz has joined #wot-discovery