- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 02 Jun 2020 17:17:16 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/05/14-wot-arch-minutes.html
also as text below.
Thanks a lot for taking the minutes, Toumura-san and Zoltan!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Architecture
14 May 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Agenda
Attendees
Present
Kaz_Ashimura, Michael_Lagally, Tomoaki_Mizushima,
Ryuichi_Matsukura, Ege_Korkan, Kunihiko_Toumura
Call 1: Kaz_Ashimura, Michael_Lagally,
Tomoaki_Mizushima, Ryuichi_Matsukura, Ege_Korkan,
Kunihiko_Toumura
Call 2: Zoltan_Kis, Tomoaki_Mizushima, Kaz_Ashimura,
Michael_Lagally, Michael_McCool, Elena_Reshetova
Regrets
Chair
Lagally
Scribe
ktoumura, zkis
Contents
* [3]Topics
1. [4]Call 1
1. [5]Agenda review
2. [6]Minutes review
3. [7]Virtual f2f planning
4. [8]Use case
2. [9]Call 2
1. [10]Prev minutes
2. [11]Use cases
3. [12]Pull requests
4. [13]Smart Grid Use case
5. [14]Lifecycle
* [15]Summary of Action Items
* [16]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: ktoumura
Call 1
Agenda review
<kaz> [17]Agenda for today
[17] https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Agenda
Minutes review
<kaz> [18]May-7
[18] https://www.w3.org/2020/05/07-wot-arch-minutes.html
Lagally: some typo
<kaz> [typos fixed]
<kaz> minutes approved
Virtual f2f planning
[19]Lagally's slides
[19] https://github.com/w3c/wot-architecture/blob/master/proposals/WoT Use Cases - Next steps-200514.pdf
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> [20]strategy funnel
[20] https://github.com/w3c/strategy/projects/2
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
Use case
(issue #496)
Ege: Educational use cases.
<kaz> [21]Issue 496
[21] https://github.com/w3c/wot-architecture/issues/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]
__________________________________________________________
Call 2
<kaz> scribenick: zkis
Prev minutes
<kaz> [22]May-7
[22] https://www.w3.org/2020/05/07-wot-arch-minutes.html
<inserted> minutes approved
Use cases
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:
[23]https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,
_Online#F2F_Topics_.28Tentative.29
[23] 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
Pull requests
Lagally: Transportation use case
... a kind of overview, let's just go ahead and merge it
<kaz> [24]Pullrequest 470
[24] https://github.com/w3c/wot-architecture/pull/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> [25]Pullrequest 487
[25] https://github.com/w3c/wot-architecture/pull/487
Smart Grid Use case
<kaz> [26]Pullrequest 495
[26] https://github.com/w3c/wot-architecture/pull/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
[27]https://github.com/w3c/wot-architecture/pull/498
[27] 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
[28]https://github.com/w3c/wot-architecture/pull/499
[28] 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
[29]https://github.com/w3c/wot-architecture/pull/501
[29] https://github.com/w3c/wot-architecture/pull/501
McCool: explains the changes
... we could merge it
[merged]
Lagally: #502
[30]https://github.com/w3c/wot-architecture/pull/502
[30] 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]
Lifecycle
<mlagally>
[31]https://github.com/w3c/wot-architecture/issues/479
[31] https://github.com/w3c/wot-architecture/issues/479
Lagally: #478
[32]https://github.com/w3c/wot-architecture/pull/478
[32] 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]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [33]scribe.perl version 1.154 ([34]CVS log)
$Date: 2020/06/02 08:15:00 $
[33] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[34] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 2 June 2020 08:16:37 UTC