– DRAFT –
WoT Architecture

minutes

<kaz> Aug-4

Lagally: review minutes of 4 aug

McCool: wonder if using tag-needs-resolution label is a good idea, hard to remove, but ok

Lagally: can we publish the minutes? Any objections?

Publication

PR 823

<kaz> PR 823 - WIP: Add change log from FPWD 1.1 to 2-WD

Lagally: some minor issues, but I think we should just merge it

McCool: ok

Kaz: now that we have the change log, shall I publish the updated draft?

Lagally: yes, let's

tag-needs-resolution issues

issue 818

<kaz> Issue 818 - Consider whether this makes more sense as a Note [TAG feedback]

Lagally: should arch be a note?

Lagally: mozilla previously asked this, now raising

McCool: bottom line is we need a place for global assertions, like security

McCool: but charter does not set security as a normative document

McCool: related to other issues that are "extra"; if we remove unessential assertions, then restructuring later will be easier

Kaz: agree

McCool: before we can change from normative to informative, need to identify essential assertions first

issue 816

<kaz> Issue 816 - Review for redundant normative statements [TAG feedback]

McCool: regarding redundant assertions, I think we fixed the one they called out already
… but there may be others

McCool: suggest updating comment to say that we are open to discussing this further

Kaz: also suggest we reach out to TAG and request a meeting

issue 814

<kaz> Issue 814 - Compatibility in the ecosystem [TAG feedback]

Lagally: compatibility story - added some comments

McCool: need to explain what protocols work, gateways, etc.

issue 811

<kaz> Issue 811 - Improve security section to address TAG feedback

McCool: add comment that we plan to update the Guidelines document this fall, but because it is informative essential assertions need to be in a normative document. We can update the reference so it is informative

issue 809

<kaz> Issue 809 - Fix normative references / convert to informative, where applicable

Lagally: informative/normative refs again, should be relatively easy to fix

implementation report

McCool: updated, but more work to do

WIP security assertion issue

Lagally: issue 824

McCool: Issue 824 - WIP: Adjust policy-like security and privacy assertions what we have to deal with, but I still need to implement a PR

<kaz> [adjourned]