Meeting minutes
Agenda
<ML presents the agenda>
We should check the issue about the Profile normative section in Arch11 spec. Should be informative. I provided a PR to solve this issue
Minutes
WoT Arch
https://
<mlagally> decision: revisit in next charter period (issue 815)
<mlagally> anecdotal
Lagally: any objections?
McCool: looks good
approved
WoT Profile
https://
<mlagally> there was no consensus - we agreed to cancel the previous resolution
McCool: is ok
<mlagally> (ran out of time) - AOB
<kaz> (Architecture part is approved)
Lagally: we will keep the minutes open, will be approved in the next Profile call
Issues to close
Issue 841 Link
<mlagally> https://
<mlagally> /github.com/w3c/wot-architecture/issues/841/Issue 814 - Compatibility in the ecosystem [TAG feedback]
Lagally: will close
<mlagally> -> /github.com/w3c/wot-architecture/issues/814 -> close/
Issue 814
<kaz> rrsagent make log public
<kaz> rrsagent draft minutes
<kaz> Issue 814 - Compatibility in the ecosystem [TAG feedback]
Lagally: close this issue
Issue 587
<mlagally> https://
https://
Lagally: close issue
<mlagally> https://
Issue 561
Issue 561 - Lifecycle simplification
<kaz> Issue 841 - Update Security Link
Lagally: will close
Issue 558
Issue 558 - Cross reference FPWD drafts of Discovery, TD, ...
Lagally: will be not closed. Defered to next Arch version
Issue 555
<mlagally> Issue 555 - system lifecycle with registration
<mlagally> deferred to 2.0
Issue 548
<mlagally> Issue 548 - Align language: use case vs. application domains
Lagally: close this issue
Issue 412
Issue 412 - Property affordances claimed to always readable
<ML shows the text in Arch section 6.5.1>
Lagally: Issue is addressed, we can close this issue
Issues with label "close next week"
Issue 553
<mlagally> https://
McCool: Prefer to defer it to next charter
… relates to registration
<mlagally> Issue 553 - Information lifecycle
Lagally: ok, defer it
Issue 538
Issue 538 - Lifecycle section needs to take peer to peer discovery into account
Lagally: lets also defer it
Issue 536
Issue 536 - Relationship to Project Connected Home over IP
McCool: CHIP is now called Matter
Sebastian: I'm wondering why achitecture should address this. Maybe more relevant for use case discussion.
Kaz: Ok with moving to Use Case doc. New smart home standards should be also mention in the new charter.
<ML adds "use case" and "charter discussion" labels to the issue>
issue will be not closed
<mlagally> https://
Issue 530
Issue 530 - Incorporate Discovery terminology into terminology section
Lagally: Issue seems to be solved
… going to close
Issue 524
Issue 524 - Sequence diagram for TD lookup in a directory service
Lagally: Will keep it open
Issue 417
Issue 417 - [question] Is the servient a hypervisor or single application vm?
Lagally: Question was answeard in the issue
… going to close this issue
<mlagally> proposal: Architecture TF agrees to close issues that are marked as "question" after they had been sufficiently "answered"
RESOLUTION: Architecture TF agrees to close issues that are marked as "question" after they had been sufficiently "answered"
Issue 374
Issue 374 - Where did w3c-wot-td-context.jsonld and w3c-wot-common-context.jsonld go?
Lagally: close
Issue 365
Lagally: close it
Issue 364
Issue 364 - How does one connect "directly to the cloud"?
Lagally: close it
Issue 48
Lagally: also close it
Issues to close or defer
Issue 508
<kaz> Issue 508 - Create a terminology definition for "system user data"
Sebastian: Oliver is not active anymore. We should involve Jiye
Lagally: let keep it open
Issue 455
Issue 455 - Cross check terminology of stakeholders with DID
Lagally: close it
Issue 430
Issue 430 - Give basic definition of "End-to-End Security"
Lagally: close it
Issue 429
Issue 429 - More clearly define "Thing Authentication"
McCool: keep it open
Issue 208
Issue 208 - Need deployment example for Cloud Server with Client devices
Lagally: keep it open and defer it
Issues to resolve by PR transition
Issue 859
Issue 859 - Prepare PR publication
Lagally: It seems that APA did not review yet
McCool: I will check
PR
PR 862
PR 862 - Switch Profile to non-normative section
<kaz> related Issue 850 - Contradiction with the WoT Profile spec on protocol bindings
<there is too less time for detail disussion>
<kaz> (to be discussed during the Profile call next Wednesday)
Lagally: let's continue in Profile call
<kaz> [adjourned]