- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 13 May 2020 17:27:40 +0900
- To: public-wot-wg@w3.org
available at: https://www.w3.org/2020/04/30-wot-arch-minutes.html also as text below. Thanks, Kazuyuki --- [1]W3C [1] http://www.w3.org/ - DRAFT - WoT Architecture 30 Apr 2020 Attendees Present Call 1: Kaz_Ashimura, Michael_Lagally, Tomoaki_Mizushima, Zoltan_Kis Call: Kaz_Ashimura, Christian_Glomb, Michael_Lagally, Michael_McCool, Zoltan_Kis, Tomoaki_Mizushima, Elena_Reshetova Regrets Chair Lgally Scribe Kaz, McCool Contents * [2]Topics 1. [3]Call 1 1. [4]Previous minutes 2. [5]Call 2 1. [6]Review minutes 2. [7]Issues 3. [8]Smart Grid use case 4. [9]Lifecycle 5. [10]Next week * [11]Summary of Action Items * [12]Summary of Resolutions __________________________________________________________ Call 1 (Lagally asks Zoltan to share the updated lifecycle diagram so that we can discuss it during the 2nd call.) Previous minutes <kaz> [13]Apr-23 minutes [13] https://www.w3.org/2020/04/23-wot-arch-minutes.html Lagally: (goes through the prev minutes) ... minor typo, "discus" <kaz> [just fixed] Lagally: ok ... let's approve the minutes then ... and then talk to you all later during the second call <kaz> [call 1 adjourned] __________________________________________________________ Call 2 <kaz> scribenick: McCool Review minutes <kaz> [14]Apr-23 minutes [14] https://www.w3.org/2020/04/23-wot-arch-minutes.html Lagally: (reviews minutes) ... any objections to approving minutes? ... no objections, approved. Issues <mlagally> [15]https://github.com/w3c/wot-architecture/issues [15] https://github.com/w3c/wot-architecture/issues <kaz> (go through the use case issues) <kaz> [16]Issue 490 - people density [16] https://github.com/w3c/wot-architecture/issues/490 <mlagally> [17]https://github.com/w3c/wot-architecture/issues/489 [17] https://github.com/w3c/wot-architecture/issues/489 <kaz> [18]Issue 489 - smart city dashboard [18] https://github.com/w3c/wot-architecture/issues/489 McCool: will discuss and convert to template in next call with GovTech <kaz> [19]Issue 481 - energy efficiency [19] https://github.com/w3c/wot-architecture/issues/481 <kaz> PR to be created <mlagally> [20]https://github.com/w3c/wot-architecture/issues/480 [20] https://github.com/w3c/wot-architecture/issues/480 McCool: we will also work through this one with Fraunhofer in next week's discovery call <kaz> [21]Issue 480 - NHK's one [21] https://github.com/w3c/wot-architecture/issues/480 Lagally: can close this one, done <kaz> [22]Issue 479 - agriculture [22] https://github.com/w3c/wot-architecture/issues/479 Lagally: will probably have to discuss this one after golden week <kaz> [23]Issue 476 - lifecycle discussion [23] https://github.com/w3c/wot-architecture/issues/476 <inserted> scribenick: kaz McCool: original requirement was adding high-level considerations ... then technical requirements on different points for different players [24]PR 488 on new use case/requireement remplate sections [24] https://github.com/w3c/wot-architecture/pull/488 McCool: features and schemes Lagally: good to have an example to illustrate the granularity McCool: discussion by the security tf will happen in May ... this is a template for that purpose ... will discuss examples during the security calls Lagally: ok McCool: btw, it seems there is a typo on "####" for the section title Lagally: don't worry <mlagally> [25]https://github.com/w3c/wot-architecture/pull/488 [25] https://github.com/w3c/wot-architecture/pull/488 <inserted> scribenick: McCool Lagally: no problem, will merge McCool: I will fix typo later Smart Grid use case <kaz> [26]PR 487 [26] https://github.com/w3c/wot-architecture/pull/487 <kaz> [27]rendered UC on smart grids [27] https://github.com/wiresio/wot-architecture/blob/master/USE-CASES/smart-grid.md McCool: all Michael and non-Michaelss are invited to review Christian: any inputs, let us know, can incorporate ... reviews PR McCool: comment, consider technicians as stakeholders and emergency response as a variant Lagally: let's defer that until later ... please expand acronyms, DSO, TSO, VPP, etc Christian: ok; also PMU (expanded, but used in more than one place...) McCool: I would add storage somewhere ... i.e. batteries or pumped water; both amount stored and capacity Christian: some variants: Decentralized power generation (expand CHP); ... Virtual Power Plants (VPP) ... Smart metering Lagally: VPPs would be energy brokers? Christian: would also organize physical sources McCool: would add storage to DER (call it Distributed Energy Resources rather than "Generation"; Resources includes Storage and DER is an accepted term) ... also add a separate variant for "Emergency Response": should support bypass of parts of the grid when maintenance is required to protect workers and keep power distribution going as much as possible ... (I will add these comments to the issue) Lagally: any more comments? please do add to the PR Lifecycle Zoltan: (shares updated diagram showing levels WoT/Provider/Manufacturer) <inserted> scribenick: kaz McCool: would call the top layer "application" rather than "WoT" Kaz: +1 McCool: what happens when the given system needs update for several layers? ... would make application keys "none" in the middle box ... could imagine the case of rotating the keys Zoltan: have just updated the diagram ... please reload it Lagally: reloads the diagram Zoltan: application keys: none ... for the operational state McCool: ok Zoltan: still have to go through the main system Lagally: one comment on the "destroy" state ... there is specific transitions we discourage McCool: the device is permanently disabled for "destroyed" ? <inserted> scribenick: McCool McCool: suggest we use phrase "permanently disabled" Lagally: we now need a description in the notes explaining the keys in particular ... related to an issue in the security dicussion scribenick: kaz Kaz: wondering about the top layer ... the other two layers are players' names ... so might be better to have some name for the player for the top layer too? ... not sure how to call it at the moment, though <kaz> (we need further discussion about the lifecycle topic, and will continue the discussion based on the updated diagram) <mlagally> [28]updated lifecycle diagram [28] https://drive.google.com/file/d/1E7dF65r8i1rx5ykJujMYe14RYPOvXAPf/view?ts=5ea9d15c Next week Lagally: would suggest we skip call 1 and have call 2 on May 7 scribenick: McCool McCool: regrets.. need to drop [adjourned] Summary of Action Items Summary of Resolutions [End of minutes] __________________________________________________________ Minutes manually created (not a transcript), formatted by David Booth's [29]scribe.perl version 1.154 ([30]CVS log) $Date: 2020/05/04 08:55:23 $ [29] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [30] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 13 May 2020 08:27:18 UTC