- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 22 Jun 2020 15:02:40 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/05/28-wot-arch-minutes.html
also as text below.
Thanks a lot for taking the minutes, Zoltan!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Architecture
28 May 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Agenda
Attendees
Present
Call 1: Kaz_Ashimura, Michael_Lagally,
Tomoaki_Mizushima, Ryuichi_Matsukura
Call 2: Kaz_Ashimura, Michael_Lagally, Michael_McCool,
Tomoaki_Mizushima, Zoltan_Kis, Michael_Koster
Regrets
Chair
Lagally
Scribe
kaz, zkis
Contents
* [3]Topics
1. [4]Call 1
1. [5]Agenda
2. [6]Prev minutes
3. [7]Virtual f2f planning
4. [8]Reorganizing the WoT Architecture page
5. [9]Issues
6. [10]Pullrequests
7. [11]Roadmap
2. [12]Call 2
1. [13]Agenda
2. [14]Prev minutes
3. [15]F2F planning
4. [16]Use Cases
5. [17]Pull Request 498
6. [18]Pull Request 500
7. [19]Pull Request 504
8. [20]Pull Request 505
9. [21]Pull Request 509
10. [22]Use case prioritization questionnaire
11. [23]How to proceed with the use case discussion
* [24]Summary of Action Items
* [25]Summary of Resolutions
__________________________________________________________
Call 1
<kaz> scribenick: kaz
Agenda
Lagally: (goes through the agenda for today)
... logistics and roadmap
... use case document, prioritization, IG work, requirements
Prev minutes
[26]May-14 minutes
[26] https://www.w3.org/2020/05/14-wot-arch-minutes.html
Lagally: have I uploaded the slides?
Kaz: maybe not?
<mlagally_>
[27]https://github.com/w3c/wot-architecture/blob/master/proposa
ls/WoT%20Use%20Cases%20-%20Next%20steps-200514.pdf
[27] https://github.com/w3c/wot-architecture/blob/master/proposals/WoT Use Cases - Next steps-200514.pdf
Lagally: available at the URL above
Kaz: will add it to the minutes then
Lagally: ok to approve the minutes with the addition?
(no objections)
Lagally: approved
Virtual f2f planning
Lagally: lifecycle and use cases
... the plan is finalizing the lifecycle discussion by the
virtual meeting
... also prioritizing the UC
[28]Virtual F2F page
[28] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,_Online
Lagally: T2T workshop on June 8
... then PlugFest and F2F
(PlugFest on June 15-19; F2F on Jun 22-26)
[29]Requests to speak
[29] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,_Online#Requests_to_Speak_2
scribe: update, lifecycle, discovery, PoCs, CHIP, ODM, IRTF WS
[30]F2F topics
[30] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,_Online#F2F_Topics_.28Tentative.29
Matsukura: couldn't join the recent lifecycle discussions
... what's the main point?
... lifecycle of what?
Lagally: device lifecycle
<mlagally_>
[31]https://github.com/w3c/wot-architecture/blob/master/proposa
ls/unified%20device%20lifecycle.svg
[31] https://github.com/w3c/wot-architecture/blob/master/proposals/unified device lifecycle.svg
<mlagally_>
[32]https://github.com/w3c/wot-architecture/blob/master/proposa
ls/lifecycle-model-proposal-zolkis.md
[32] https://github.com/w3c/wot-architecture/blob/master/proposals/lifecycle-model-proposal-zolkis.md
Lagally: Zoltan should upload his updated diagram
<scribe> ACTION: zkis to upload his updated diagram to the GH
repo
Kaz: in short, we've been discussing the lifecycle of WoT-based
service in general
... Elena gave a diagram from WoT security viewpoint
... Lagally gave a diagram from a bit different viewpoint
including device and data transfer
... Zoltan also gave a diagram from another viewpoint including
the 3-layer model of device, network and application
[33]Elena's diagram (lifecycle diagram-WoT new lifecycle.svg)
[33] https://github.com/w3c/wot-architecture/blob/master/proposals/WoT
[34]Lagally's diagram (device lifecycle.svg)
[34] https://github.com/w3c/wot-architecture/blob/master/proposals/unified
[35]Zoltan's diagram (Google account required)
[35] https://drive.google.com/file/d/1E7dF65r8i1rx5ykJujMYe14RYPOvXAPf/view?ts=5ea9d15c
Lagally: right
... (shows his own generated diagram)
Matsukura: which part is in the scope of WoT?
... onboarding is already done by the other SDOs
Kaz: the application layer in Zoltan's diagram is the main
target of WoT, I think
Lagally: we need to have clear terminology definition as well
... (then updated the "F2F Topics" section)
[36]F2F Topics section from the online f2f meeting wiki
[36] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,_Online#F2F_Topics_.28Tentative.29
Lagally: use case prioritization - 2h
... profiles - 2h
... requirements - 1h
... lifecycle - 2h
... so 7 hours for architecture topics
Reorganizing the WoT Architecture page
Lagally: this wiki page is getting bigger
... not sure how to improve it, though
Kaz: we can create a separate "previous" page
... might be better to have ones based on the year, though
... e.g., "2019", "2018" and "2017"
Lagally: ok
Issues
Lagally: an issue for update from NHK
[37]Issue 507
[37] https://github.com/w3c/wot-architecture/issues/507
Lagally: need a pullrequest
Kaz: they would like to generate a pullrequest but not for the
WG repo but an IG repo
Lagally: ok
Pullrequests
[38]Pullrequest 498
[38] https://github.com/w3c/wot-architecture/pull/498
Lagally: adding profile use case
... (goes through the description)
... TD is an extremely descriptive format
... but need common ground on how to understand it
... would like to present this proposal during the call 2 too
Kaz: as you already mentioned, the title of this proposal
should be something descriptive rather thant "need for wot
profile"
Lagally: right
... (and add a proposed title, e.g., "Out of the box
interoperability")
[39]Pullrequest 500
[39] https://github.com/w3c/wot-architecture/pull/500
Lagally: update for retail with security and privacy
considerations
... OK with merging this proposal but would talk about this
during call 2 as well
[40]Pullrequest 504
[40] https://github.com/w3c/wot-architecture/pull/504
Lagally: medical device use case from Taki
... think this is a good use case
... note that there should be many existing standards for
medical purposes
... (Lagally gave comments like "adding references would b
useful")
... might want to think about some kind of semantic tags
... we already have units but don't have mechanism for this
kind of interaction for medical purposes
... my plan is merging this but would discuss this during the
call 2 again
[41]Pullrequest 505
[41] https://github.com/w3c/wot-architecture/pull/505
Matsukura: agriculture use case
... there are 3 kinds of requirements
... device virtualization, state for things, units
... reference to Genivi's site suggested by somebody
Lagally: btw, maybe you should remove extra <br> tags from the
MD file :)
Matsukura: ok
Roadmap
Lagally: initial use case document to be generated
... the idea is making the use case discussion part of the IG
... so that non-WG participants can join it easily
... by creating a separate wot-usecases repo, etc.
... technical contributions to the actual specs still remain at
the Architecture TF
Kaz: think the separation is reasonable
... uc/req discussion can be done by the IG
... actual REC work to be done by the WG
Lagally: official resolution is still to be done
... but we can move the "USE-CASES" resources to the new repo
... (shows the initial UC/REQ Note)
[42]Pullrequest 506
[42] https://github.com/w3c/wot-architecture/pull/506
Kaz: so we can make a preliminary resolution from this call 1,
and make the final resolution during call 2
Lagally: (generates it)
<mlagally_> proposal: hand over contents of thre USE-CASE
directory to the Use Case IG TF for inclusion into a Use Cases
document
RESOLUTION: hand over contents of the USE-CASE directory to the
Use Case IG TF for inclusion into a Use Cases document
Lagally: we have two additional co-Editors for this UC
document, Matsukura-san and Mizushima-san
Kaz: great
Lagally: btw, Kaz has just created a draft UC prioritization
questionnaire
... which lists all the UCs so far classified by its category
... that's it for today
... anything else?
(none)
Lagally: please join the Use Case TF call later today as well!
[Call 1 adjourned; UC call in 4 hours; Call 2 in 8 hours]
__________________________________________________________
Call 2
<scribe> scribenick: kaz
<mlagally__> fyi,
[43]https://www.iamexpat.de/education/primary-secondary-educati
on/school-holiday-dates-germany
[43] https://www.iamexpat.de/education/primary-secondary-education/school-holiday-dates-germany
Agenda
Lagally: (goes through the agenda)
[44]Agenda
[44] https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Agenda
Prev minutes
[45]May-14
[45] https://www.w3.org/2020/05/14-wot-arch-minutes.html
Lagally: posted the slides
... to be added to the May-14 slides
<scribe> scribenick: zkis
Lagally: propose to accept with the small fix
[minutes accepted]
F2F planning
[46]June virtual f2f wiki
[46] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_1-12_June_2020,_Online#F2F_Topics_.28Tentative.29
Lagally: There was a call earlier today
... editing wiki with F2F agenda proposal
McCool: in the future, we should avoid putting dates in the
title, since it may change
Kaz: I could create another page and put a link to the old page
(after this call)
Lagally: goes through the proposed F2F agenda topics and
figuring out the time needed
... a new section is needed for the lifecycle discussion
... shows the lifecycle proposals
Zoltan: the new section should be concise enough and we need to
discuss content prioritization
Lagally: state names, transitions, security, etc
Zoltan: sounds good
Lagally: a small request: please create an SVG snapshot from
the latest diagram and upload to the repo
<scribe> ACTION: ZK updates the SVG snapshot
McCool: let's note which Architecture calls we can have due to
holidays
Lagally: records the call dates in the wiki
McCool: we will have similar issues with the Use Case call
... therefore we should have it also with the plugfest call
... will put placeholder agenda sections and mention what is
cancelled or not
... we should also have a summer break
Lagally: fine with that
McCool: will update the invites and will send updates to the
members list
<scribe> ACTION: MM to update meeting invites
Use Cases
Lagally: there is the new Use Case IG taskforce forked from the
Architecture TF
... there is a new call
... all IG members could contribute use cases
... not only WG members
... there is a new Use Cases document
[47]Use Cases and Requirements
[47] https://w3c.github.io/wot-architecture/USE-CASES/wot-use-cases/index.html
Lagally: will be a Note
... right now it's only a skeleton
... Requirements will be separated from Use Cases
... and should happen in the WG because of potential IPR
context
... co-editors are welcome to the Use Case doc
McCool: looks good, we could merge the PR
[48]Pullrequest 506
[48] https://github.com/w3c/wot-architecture/pull/506
Pull Request 498
<inserted> [49]Pullrequest 498
[49] https://github.com/w3c/wot-architecture/pull/498
Lagally: #498
... adds the profiles use case
Koster: there could be something specific about code generation
... the system should be able to do adaptation
McCool: profiles in general need some pre-work
Lagally: this is still good for starting the profile discussion
during the F2F
... automatic code generation could be a requirement
McCool: well, we should avoid _automatic_ code generation,
maybe in development time
... we should avoid too fancy stuff, rather define the context
better
Lagally: ok, let's merge this now
McCool: agreed
Pull Request 500
<inserted> [50]Pullrequest 500
[50] https://github.com/w3c/wot-architecture/pull/500
McCool: updates retail.md with security and privacy
considerations
Lagally: good to merge
Pull Request 504
<inserted> [51]Pullrequest 504
[51] https://github.com/w3c/wot-architecture/pull/504
Lagally: adds medical devices use case
Lagally: it is under review still
McCool: needs more review and Taki is not here, so let's defer
Lagally: ok, let's keep it open for now
... will add comments
Pull Request 505
<inserted> [52]Pullrequest 505
[52] https://github.com/w3c/wot-architecture/pull/505
Lagally: agriculture use cases
McCool: would separate greenhouse use case from generic
agriculture use case category
Lagally: should we merge?
McCool: maybe review it more, as the author is not here
Lagally: ok, adding a comment
Pull Request 509
<inserted> [53]Pullrequest 509
[53] https://github.com/w3c/wot-architecture/pull/509
Lagally: adding smart building use case
McCool: discovery stuff should be moved
... ok with merging it and will make a comment
Lagally: adding a comment with summary
... merging
... ok, we finished the PRs
... AOB?
Use case prioritization questionnaire
Lagally: working on the draft questionnaire
... I would keep it open for 2 weeks
McCool: ok that's enough to process and prepare for the PF and
F2F
... note that discovery is not a category, but a horizontal
thing
... automotive is a vertical use case
Lagally: yes these will need to be broken down
McCool: ok it's good enough for collecting information
... features are horizontal, use cases are vertical
... we could have a table/matrix with these
Lagally: I am more inclined to break down the categories
... let's not overcomplicate, use this questionnaire and then
process the results
McCool: agreed to go ahead, the suggestion was for future work
Lagally: OK.
... well, that concludes. We will look into the Issues next
time.
How to proceed with the use case discussion
Kaz: we need the final resolution of moving the use cases into
the new use case repository?
Lagally: yes - we made a resolution in the Arch call 1
<kaz> Proposal: hand over contents of the USE-CASE directory to
the Use Case IG TF for inclusion into a Use Cases document
Lagally: does everybody approve this?
McCool: we need to deal with IP consequences
... since we move from WG repo to an IG repo
... this loosens the IP requirements
... so it's unlikely there will be complaints
Lagally: since one cannot patent a use case, there should not
be much problem
McCool: but formally needs to be addressed since the WG -> IG
move
Lagally: so, do we approve the resolution?
... all IG members would access it
McCool: would we extend the rights to guests as well?
Lagally: yes
[accepted]
RESOLUTION: hand over contents of the USE-CASE directory to the
Use Case IG TF for inclusion into a Use Cases document at the
expected wot-usecases repo
Lagally: will make the move later
<kaz> ACTION: kaz to create a new repo of wot-usecases
Lagally: AOB?
[adjourned]
<kaz> (next call in 2 weeks)
Summary of Action Items
[NEW] ACTION: kaz to create a new repo of wot-usecases
[NEW] ACTION: MM to update meeting invites
[NEW] ACTION: ZK updates the SVG snapshot
[NEW] ACTION: zkis to upload his updated diagram to the GH repo
Summary of Resolutions
1. [54]hand over contents of the USE-CASE directory to the Use
Case IG TF for inclusion into a Use Cases document
2. [55]hand over contents of the USE-CASE directory to the Use
Case IG TF for inclusion into a Use Cases document at the
expected wot-usecases repo
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [56]scribe.perl version ([57]CVS log)
$Date: 2020/06/02 08:09:55 $
[56] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[57] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 22 June 2020 06:01:47 UTC