<kaz> scribenick: ktoumura
<kaz> Agenda for today
<kaz> May-7
Lagally: some typo
<kaz> [typos fixed]
<kaz> minutes approved
Lagally: (introducing use case
slides)
... We are working use cases and life cycle. Still other work
items remain.
... Workflow for architecture process.
Kaz: "architecture process" should be "discussion process".
Lagally: (updated)
... Currently there are 20 use cases.
... Use case categories: Retail, Audio/Video ...
... from use case, we'll prepare a shortlist to make sure the use cases address real market needs, etc.
... ... then, prioritize them.
Ege: I support this process.
Lagally: I'll present this slides in next few meeting.
Kaz: I suggest that we put a
document together including all the proposed use cases, then
after prioritize them.
... I can generate a W3C WBS questionnaire for the voting purpose
Ryuichi: I want to insert "system configuration" between "shortlist" and "New Building block" .
Kaz: "system configuration" may
already included in "Requirement"
... and "Use case" part.
Ryuichi: to understand "building
block", we have to show some "system
... configuration"
Kaz: how about remove "new
building block", and just discuss them in "Gaps"?
... we should clarify output of each process.
Lagally: (categorizing processes to two phase)
<kaz> strategy funnel
Kaz: W3c teams also have similar
process, strategy funnel.
... need not to follow the strategy funnel.
... Gaps, New BB, Sys Conf are part of "Requirements" as its
features
(issue #496)
Ege: Educational use cases.
<kaz> Issue 496
Ege: We put the some device in
the lab, and it can be seen by IP cameras.
... Target users are university student, and plugfest
participant..
... motivation of this use case is device sharing.
... (introducing devices, data)
Kaz: You can make a title more specific. "Sharing devices" etc.
Lagally: It is not restricted to
education.
... let's continue discussion in afternoon session.
... We have 8 PRs, and we'll review in todays call.
Ryuichi: I added some use case in Issue. I'll convert it to a PR.
<kaz> [adjourned]
<kaz> scribenick: zkis
<kaz> May-7
<inserted> minutes approved
Lagally: the Use Cases call was useful, we got inputs
Lagally presents the Use Case TF presentation
Lagally: Use Case call will start
regularly
... a Use Case document will be produced
... the Architecture TF takes use cases, identifies
requirements and feeds them to the other task forces, like TD,
Scripting, Security, etc
McCool: regarding the work items we should identify which use cases impact them
Lagally: yes, I am going through the use cases and check how they apply
Lagally: there are about 20 use cases
in the pipeline
... in various Use Case categories
McCool: some of these are domains,
others are technical features, so we should separate them
... we should add Transportation and Discovery
Lagally: we will update this
<McCool> added 2h slot request to June F2F schedule: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,_Online#F2F_Topics_.28Tentative.29
Lagally: how to prioritize use cases
McCool: we need a champion for each
use case
... also, a customer and products
Lagally: requirement documents are
one-pagers
... based on a template
<McCool> McCool: think at the end we should wrap things up with a use-case/requirements table
<McCool> ... would give a useful visual summary; can happen at the end
Lagally: the output is a Group
Note
... there is a problem that people could not access diagrams
since the lack of a google account
... we should store in the repo the contributions
McCool: a problem is which is the master version for multiformat documents
Lagally: Transportation use case
... a kind of overview, let's just go ahead and merge it
<kaz> Pullrequest 470
Zoltan: I went a circle around
separating into categories and then realized it makes more
sense to have it in one file
... we can take it from here
Lagally: merged
<kaz> Pullrequest 487
<kaz> Pullrequest 495
Lagally: we also have the Smart Building use case
Pullrequest #495
Lagally: suggest merging it
McCool reviews the PR
Lagally: let's merge it
McCool: OK
[merged]
Lagally: Profile use case, #498
https://github.com/w3c/wot-architecture/pull/498
Lagally: let's keep this open, needs discussion
McCool: this is a technical feature use case
Lagally: Update Readme, #499
https://github.com/w3c/wot-architecture/pull/499
Lagally: just a cleanup
McCool: the issue is checking the links to all the use cases updated
Lagally: let's merge and then improve later
McCool: OK
... created a PR for Security & Privacy, asked for review,
now there is a conflict
Lagally: Update retail.md, #501
https://github.com/w3c/wot-architecture/pull/501
McCool: explains the changes
... we could merge it
[merged]
Lagally: #502
https://github.com/w3c/wot-architecture/pull/502
Lagally: presented by Ege this morning
Lagally presents the PR
scribe: it's about education and shared resources
McCool: there is a gap, question is
do we need it?
... we could merge it but needs further discussions
... also wrt Discovery
... not clear if the context is research or education
Lagally: it's not a problem, can be
generalized
... will merge it and then discuss
[merged]
<mlagally> https://github.com/w3c/wot-architecture/issues/479
Lagally: #478
https://github.com/w3c/wot-architecture/pull/478
Zoltan: it has been reviewed by
Clerley and small things were fixed
... now in pretty good shape for a proposal (just an
input)
... the diagram has also been reviewed, again small things
fixed
McCool: security review should be
still open
... and we can merge this PR
Lagally: I made a few comments on the
text
... confused about a couple of terms
<McCool> mm: we should note that not all transitions may be valid in all protocols
Zoltan: right, we are just describing existing protocols
<McCool> ... for example, not all protocols may allow revision to a "manufactured" state: some may only be provisioned once and then the key store is "locked"
Lagally: confused about the "native" word
Zoltan: it means the underlying
protocol for WoT
... I could change that
... we could also use "non-WoT" instead of native
Lagally: we could take it in for now and we could improve it later
[merged]
Lagally: will continue later
Zoltan: next Thursday is public holiday
Lagally: ok, need to reschedule
AOB?
[adjourned]