<inserted> scribenick: dezell

Review of minutes

McCool: suggest we continue with lifecycle review
... also requirements.

RESOLUTION: publish Apr-27 minutes

Lifecycle review and input

Elena: haven't seen much traffic, except the diagram that Zoltan sent.
... (shows the diagram)

McCool: Zoltan proposed this latest version with the layered states.
... I think we should examine where the keys are instantiated and managed.
... provider should only update service keys.
... application level updates application keys.
... Should our state diagram include service keys, and potentially rotation (management) for those keys.

Zoltan: I think I got those changes.

McCool: need a dotted line around operational and maintenance states.
... double arrows between operation and maintenance implies a return to the original state, whereas the change should be to the latest state.
... when you go back to operational state, you don't go back to a state with no keys yet.
... in other words, a shift along the arrows doesn't lose the existing state.

Elena: returning to operational from maintenance but retaining keys is a departure from what's intended.

McCool: remove "operational keys - none" from the diagram and it should be good.
... recommend detailed follow up in the architecture call.

Requirements review and Use Case Templates

<inserted> wot-architecture issue 488

McCool: issue #488
... (adjusts topic levels)
... now that we've updated the template, there are a bunch of use cases missing the (now) higher-level sections.
... E.g., look at Smart Cities
... I think we should assign use cases to people and come back together.
... Michael has said it would be good to have one good use case.
... (ruminating) we have privacy issues, images, health status.

(see wot-architecture / USE_CASES / smartcity-health-monitoring)

<inserted> Public Health Monitoring use case

McCool: this is a use case of combining pictures with temperatures to allow personnel to find sick people in a crowd.
... major concern is mistaken identity.
... Use #488 as an example for how to fill out other use cases.
... we'll put use cases in sets, and then assign sets to people.

<McCool> https://github.com/w3c/wot-architecture/issues/492

<McCool> https://github.com/w3c/wot-architecture/tree/master/USE-CASES

Oliver: I'll volunteer for "X-Protocol Internetworking"

McCool: will people go through the issues and volunteer?
... I've worked on "mni" but others should take a look.

<kaz> wot-architecture issue 493

McCool: anybody familiar with nhk?
... David, can we assign you to retail.
... Yes.
... The issues are going to be in architecture.

Clerley: I would like to volunteer

McCool: members should take a look at how they can contribute.

<kaz> ACTION: kaz to check the editor's teams for wot-security and wot-architecture

McCool: Clerley/David volunteered for retail.
... I suggest we merge the security and architecture groups.

Other issues

Oliver: I have tried to issue a PR but have had problems

McCool: it looks like the PR is to your own master, not the remote one (W3C).

Oliver: I'll take a look.

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

McCool: we need to take at this issue #144 while we work out the technical issue.

<scribe> (Kaz has just added the "w3c-group-95969-members" Team, which includes all the WoT WG participants, to the "wot-architecture" repository so that Oliver can be assigned to the related issues.)

<McCool> https://github.com/w3c/wot-architecture/issues/493

<McCool> https://github.com/w3c/wot-architecture/issues/494

McCool: you need to go to the issue and post a comment, then you can take the assignment. comment first, take assignment second.
... retail use case is #494
... next week we'll try to clear as many issues as possible.
... go and volunteer yourselves for the use cases.

adjourned.