McCool: goes through PRs
... and updates the agenda for today

Quick updates

McCool: might be going to get additional review for security by Siemens

PRs

PR 128

McCool: simpler one above

PR 127

Elena: better logic flow here
... didn't change any terminology
... note I've removed the section on "sec-pract-things-directory"
... because that section is empty

McCool: don't see any major issues here
... we can accept both PR 127 and PR 128

(no objections)

McCool: merges PR 127 and PR 128

Issues

Elena: name change

McCool: will add a new issue

Issue 129

McCool: another new issue is merging testing document into the main security guideline

Issue 130

Elena: how to deal with the links?

McCool: can do PRs for edits
... wot-security testing doc should be merged into the wot-security
... timeline wise, we're getting shorter
... really tomorrow will get an updated draft for the implementation document
... final documents by next Monday
... discuss at the security call next Monday
... (then goes through TD issues)

TD issues

McCool: creates an issue for TD as well

TD Issue 760

McCool: update the references to "Security and Privacy Guidelines"
... and then goes to the Scripting API issues

Scripting API issues

Scripting API Issue 172

McCool: update the references to "Security and Privacy Guidelines"
... and then Architecture repo

Architecture Issue 323

McCool: there is already an issue above
... and related PR

PR 355

McCool: goes through the changes

Changes

McCool: my inclination is merging this
... (puts a comment on the PR)

Elena: any links to the wot-security-testing document?

McCool: goes through the wot-architecture document
... no reference here

Elena: should change the main wot-security document as well

McCool: quickly skimmed and seems ok

Terminology issues and updates

Elena: is "consumer" the correct term?

McCool: right now "consumer" is a client
... but some possibility of a bit different setting

Elena: wondering about "consumer" and "WoT consumer"

McCool: personally think "WoT consumer" is OK
... but "client" is definitely wrong
... we should list terms we use/borrow from the WoT Architecture document

Elena: the next term is
... "WoT system"
... which should we use, "WoT system" or "WoT network"?

McCool: "WoT system" should be better
... and we should define that as a term within the WoT Architecture document
... btw, "Server" or "Client" is defined
... though we define "Servient"

Elena: ok
... what about "WoT device"?

McCool: we should have "WoT device"
... we should add definition to "Device" in the WoT context as well
... technically "Thing" is abstraction
... an object available to WoT servients
... representation of an entity

Elena: ok, I'll double check
... next
... what about "Gateway"?
... in general "Intermediary" would be a safer word
... should not use "Proxy" as a generic term for "Intermediary"

<McCool> https://www.w3.org/TR/wot-architecture/images/architecture/intermediary.png

Elena: next
... "Instance"

McCool: we have the diagram here
... (shows Figure 27)

Figure 27

McCool: "Behavior Implementation" might be a better word
... some confusion on execution context here
... would not use "Thing Instance"
... maybe "Execution environment" or "Behavior implementation"
... "Thing instance" is not reasonable
... we should change it
... try to find time for review
... e.g., on Thursday
... hopefully not huge changes

Elena: right

McCool: merges Architecture issue 323

Architecture 323

Security section of the Architecture document

Elena: it's confusing

Security section

McCool: would be a pretty big edit
... should check with the security experts again

<inserted> er: will check

Kaz: thanks

Feedback review

McCool: let's create a GitHub issue for each review feedback
... to be moved to TD, Architecture, etc.

Elena: ok

[adjourned]