- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 01 Mar 2021 15:21:57 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at: https://www.w3.org/2021/02/08-wot-sec-minutes.html also as text below. Thanks a lot for taking the minutes, Oliver! Kazuyuki --- [1]W3C [1] https://www.w3.org/ WoT Security 08 February 2021 [2]IRC log. [2] https://www.w3.org/2021/02/08-wot-sec-irc Attendees Present Cristiano_Aguzzi, Elena_Reshetova, Kaz_Ashimura, Michael_McCool, Oliver_Pfaff, Tomoaki_Mizushima Regrets - Chair McCool Scribe Oliver Contents 1. [3]Prev minutes 2. [4]Agenda bashing 3. [5]Quick updates 4. [6]Issues and PRs 5. [7]Accessibility Meeting minutes Prev minutes <kaz> [8]Feb-1 [8] https://www.w3.org/2021/02/01-wot-sec-minutes.html Minutes: review of the minutes WoT-Security call 2021-02-01 - no objections raised, are considered published Agenda bashing <cris> [9]https://github.com/w3c/wot-scripting-api/pull/289 [9] https://github.com/w3c/wot-scripting-api/pull/289 Quick updates Quick updates: none Issues and PRs Issues and PRs: starting now First about [10]https://github.com/w3c/wot-scripting-api/pull/ 289 handling of "Security" section in partial TD needs consideration [10] https://github.com/w3c/wot-scripting-api/pull/289 A delta approach is suggested: Security section from parent TD is inherited when partial TD does not contain a Security section. A partial TD may override Security in parent TD by having an own Security section As follow-up a new issue shall be created that considers Security scheme selection Other follow-up: Management API requirements and Management of security items (keys, shared secrets...) also to be addressed inn to-be-created issues <kaz> [11]algorithm at 5.2.1 Use an ExposedThingInit - Preview of wot-scripting-api PR 289 [11] https://pr-preview.s3.amazonaws.com/relu91/wot-scripting-api/pull/289.html#use-an-exposedthinginit <McCool> [12]https://github.com/w3c/wot-discovery/issues/99 [12] https://github.com/w3c/wot-discovery/issues/99 <cris> [13]https://github.com/w3c/wot-scripting-api/issues/287 [13] https://github.com/w3c/wot-scripting-api/issues/287 New issue "Add formal validation process" filed in WoT-Discovery repo: [14]https://github.com/w3c/wot-discovery/ issues/1043 [14] https://github.com/w3c/wot-discovery/issues/1043 <McCool> [15]https://github.com/w3c/wot-thing-description/ issues/1043 [15] https://github.com/w3c/wot-thing-description/issues/1043 <McCool> raised a TD issue linking to this and the issue in scripting Discussion of [16]https://github.com/w3c/wot-thing-description/ pull/1032 more clarification needed, could be done by extending example [16] https://github.com/w3c/wot-thing-description/pull/1032 WoT-Discovery team should indicate the directions in which they'd expect to have more examples [17]https://github.com/w3c/wot-thing-description/pull/1042 needs update with respect to response behavior [17] https://github.com/w3c/wot-thing-description/pull/1042 Accessibility <kaz> [18]wot issue 953 - Plan a meeting with APA [18] https://github.com/w3c/wot/issues/953 [19]https://github.com/w3c/wot-security/issues/166 added note on "progressive disclosure" principle [19] https://github.com/w3c/wot-security/issues/166 <McCool> [20]https://github.com/w3c/wot-security/issues/166 [20] https://github.com/w3c/wot-security/issues/166 Meeting closed <kaz> [adjourned] Minutes manually created (not a transcript), formatted by [21]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC). [21] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 1 March 2021 06:22:03 UTC