WoT Security

Prev minutes

<kaz> Feb-1

Minutes: review of the minutes WoT-Security call 2021-02-01 - no objections raised, are considered published

Agenda bashing

<cris> https://github.com/w3c/wot-scripting-api/pull/289

Quick updates

Quick updates: none

Issues and PRs

Issues and PRs: starting now

First about https://github.com/w3c/wot-scripting-api/pull/289 handling of "Security" section in partial TD needs consideration

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> algorithm at 5.2.1 Use an ExposedThingInit - Preview of wot-scripting-api PR 289

<McCool> https://github.com/w3c/wot-discovery/issues/99

<cris> https://github.com/w3c/wot-scripting-api/issues/287

New issue "Add formal validation process" filed in WoT-Discovery repo: https://github.com/w3c/wot-discovery/issues/1043

<McCool> https://github.com/w3c/wot-thing-description/issues/1043

<McCool> raised a TD issue linking to this and the issue in scripting

Discussion of https://github.com/w3c/wot-thing-description/pull/1032 more clarification needed, could be done by extending example

WoT-Discovery team should indicate the directions in which they'd expect to have more examples

https://github.com/w3c/wot-thing-description/pull/1042 needs update with respect to response behavior

Accessibility

<kaz> wot issue 953 - Plan a meeting with APA

https://github.com/w3c/wot-security/issues/166 added note on "progressive disclosure" principle

<McCool> https://github.com/w3c/wot-security/issues/166

Meeting closed

<kaz> [adjourned]