W3C

– DRAFT –
WoT Architecture

12 May 2022

Attendees

Present
Kaz_Ashimura, Kunihiko_Toumura, Meiyu_Hao, Michael_Lagally, Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
Lagally
Scribe
kaz

Meeting minutes

Welcome Meiyu!

Meiyu: (introduces herself)

Agenda

https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Architecture_May_12th.2C_2022 agenda for today

Lagally: (goes through the agenda)
… anything to be added?

(none)

Minutes

May-5

Lagally: (goes throught the minutes
… anything to be changed?

(none)

approved

Schedule

publication schedule

Lagally: normative feature freeze expected by May 6

Issue 681

Review architecture document consistency

Lagally: wondering if anything to be added to Issue 681?

McCool: not aware of any additional terminology changes
… OK with closing this issue

closed

Kaz: regarding the schedule, do we need to extend the deadline given the original deadline was May 6?

McCool: maybe we can extend it till today

Lagally: ok
… let's see the whole schedule to make sure

Explainer

PR 745 - Explainer Updates

Lagally: McCool, you've implemented all the expected updates. right?

McCool: yes

Lagally: let's merge this then

merged

McCool: can add additional edits, e.g., line 16

Contributions

Lagally: let's start with the one on TLS

PR 747

PR 747 - Additional Security/Privacy Considerations around TLS, access controls for PII

McCool: this is a mistake
… with branch handling

Lagally: let's merge another one first then

PR 746

PR 746 - Update Discoverer, add Registrant Definitions

McCool: explain what a discovery service should be
… directory service is just for directory
… discovery service is the whole mechanism
… one way for discovery is searching for directory
… the Discovery spec describes what discovery is like
… Architecture should be consistent with that

Lagally: in general, if somebody requests some changes, should provide reasonable reasons
… (goes through the changes)
… let's merge this then

merged

PR 747 - revisited

PR - Additional Security/Privacy Considerations around TLS, access controls for PII

McCool: we definitely need TLS for public networks
… summarized the mechanism within TD

10.5 Secure Transport

McCool: should use proxy approach for public network without TLS

Lagally: basically fine with the text

McCool: asking object security as well
… but what query is making?

Lagally: great piece of clarification
… some minor typos, e.g., Unforunately instead of Unfortunately.
… maybe HTML section structure should be also checked again

McCool: (asks Lagally for clarification about the issues)
… maybe missing a close tag?

Lagally: think so

PR 749

PR 749 - Remove abnf validation from rel and op

Lagally: fine with merging this

merged

PR 750

PR 750 - adding orchestration section

Lagally: generated actual text for Orchestration
… (goes through the diff)

Diff - 5.7.2 Orchestration

McCool: OK with the text itself
… but kind of concerned with the definition of "Orchestration"
… already meant as "automation" from my viewpoint

Kaz: +1
… need a clear definition
… from my viewpoint, orchestration should include mashing up multiple devices, applications and entities, and there should be some meta control model as well

McCool: maybe we can add an Editor's note and think about the concrete text later

Lagally: let's one merge this PR itself

McCool: note that we need to modify the Editor's note

merged

PR 751

PR 751 - improving profile description

McCool: "We" as the subject is usually not used
… passive voice to be used here
… like "something is defined"

McCool: ok

merged

PR 747 - revisited

PR 747 - Additional Security/Privacy Considerations around TLS, access controls for PII

McCool: this is addressing PING issues
… mutable IDs to be used for healthcare purposes

Lagally: should define "PII" as well?

McCool: that's right
… previous section 11.1.1 has the definition

diff - 11.1.1 Thing Description Personally Identifiable Information Risk

McCool: (works on the problem to update the PR)

PR 737

PR 737 - Align binding related information

Lagally: normative feature fix was expected by May 6
… but Ege is not here today
… so we need to discuss this next week on May 19

McCool: do we want to delay the CR candidate day ?

Lagally: yes
… (updates the schedule)

McCool: if we make the decision for CR candidate next week on May 19
… we still have two weeks for review

Kaz: what would be the concrete procedure here?
… please note the main call is held on Wednesday
… while this Architecture call is held on Thursday
… maybe we would make a preliminary decision by email?

McCool: CR candidate my thought was we have one more week for decision
… then ask the whole group for 2-week review

Lagally: please add this to the main call agenda for May 18

McCool: ok

PR 747 - revisited

McCool: updated the PR 747 based on the discussion today

PR 747 - Additional Security/Privacy Considerations around TLS, access controls for PII

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).