- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 07 Apr 2020 12:59:43 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/03/26-wot-arch-minutes.html
also as text below.
Thanks,
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Architecture
26 Mar 2020
Attendees
Present
Call 1: Kaz_Ashimura, Sebastian_Kaebisch, Taki_Kamiya,
Ryuichi_Matsukura, Michael_Lagally
Call 2: Kaz_Ashimura, Michael_McCool, Michael_Lagally,
Zoltan_Kis, Elena_Reshetova, Chris_Needham
Regrets
Chair
Lagally
Scribe
kaz
Contents
* [2]Topics
1. [3]Call 1
1. [4]Review minutes from the Virtual F2F
2. [5]Static HTML for REC transition
3. [6]Issues
4. [7]Thing Templates
5. [8]Thing Description Fragments
2. [9]Call 2
1. [10]Prev minutes
2. [11]Static HTML for REC publication
3. [12]Issues and Pullrequests
4. [13]Media use cases
* [14]Summary of Action Items
* [15]Summary of Resolutions
__________________________________________________________
Call 1
Review minutes from the Virtual F2F
[16]day 1
[16] https://www.w3.org/2020/03/16-wot-minutes.html#item05
Lagally: would approve the minutes
[17]day 2
[17] https://www.w3.org/2020/03/17-wot-minutes.html#item02
Lagally: went through the use cases
... geolocation use caes and TD templates
... would go ahead and approve day 2 minutes as well
[18]day 4
[18] https://www.w3.org/2020/03/19-wot-minutes.html#item03
Lagally: any concerns?
(none)
Lagally: approved
[19]Mar-12 minutes
[19] https://www.w3.org/2020/03/12-wot-arch-minutes.html
Lagally: before the virtual f2f
... (goes through the minutes)
... any concerns?
(none)
Lagally: also approved
Static HTML for REC transition
[20]diff from PR
[20] https://w3c.github.io/wot-architecture/publication/rec/diff.html
Lagally: this is the final version for the publication
... (goes through the diffs)
... expect the draft will be published along with the press
release
... the specs will be used as the basis for actual products
... would like to send official thanks to all after the
transition approval
Issues
Lagally: would like to look into issues
[21]pullrequest 463
[21] https://github.com/w3c/wot-architecture/pull/463
Lagally: will remove the example template
[22]pullrequest 464
[22] https://github.com/w3c/wot-architecture/pull/464
Lagally: updates for the use case template. any comments?
(none)
[23]pullrequest 470
[23] https://github.com/w3c/wot-architecture/pull/470
Lagally: we need some more time
Thing Templates
[24]Thing Templates requirements
[24] https://github.com/w3c/wot-architecture/blob/master/REQUIREMENTS/thing-templates.md
Lagally: possibly inherit multiple blocks
... might implement two interfaces for a blueprint
... cooler, heater vs air conditioner having both capability
... Define an inheritance mechanism and corresponding handling
of namespaces to avoid naming conflicts, when things implement
more than one template.
... would add links for some more resources
Sebastian: different topics here
... TD template and relation types
... should have resources for them
[25]Issue 465 on requirements for web linking and link
relations
[25] https://github.com/w3c/wot-architecture/issues/465
related standards:
[26]https://tools.ietf.org/html/rfc8288
[26] https://tools.ietf.org/html/rfc8288
[27]https://tools.ietf.org/html/rfc8631
[27] https://tools.ietf.org/html/rfc8631
[28]https://tools.ietf.org/html/rfc6903
[28] https://tools.ietf.org/html/rfc6903
[29]https://www.iana.org/assignments/link-relations/link-relati
ons.xhtml
[29] https://www.iana.org/assignments/link-relations/link-relations.xhtml
Thing Description Fragments
<mlagally> A Thing Description Template is a description for a
class of Things. It describes the properties, actions, events
and common metadata that are shared for an entire group of
Things,
[30]C Thing Description Templates
[30] https://www.w3.org/TR/wot-thing-description/#thing-templates
Lagally: need to define terms clearly
[31]virtual f2f day 1
[31] https://www.w3.org/2020/03/16-wot-minutes.html#item04
Lagally: possible term is "snippet" during the call
Sebastian: would have Zoltan as well
... what is our minimum expectation for TD Template?
[32]Issue 458
[32] https://github.com/w3c/wot-architecture/issues/458
Sebastian: would like to see the analogy of Object-oriented
programming approach as well
Lagally: Sebastian mentioned:
... Expose a Servient: Templates are used to define a WoT
producer such as for a WoT runtime implementations (e.g.,
node-wot)
... and Zoltan responded:
... That is not a TD template, but a partial TD (or TD
fragment) that may contain parts that cannot be part of a TDT.
... (goes through the discussion on Issue 458)
... we need to keep things separately
... Zoltan mentions instance-specific data
Sebastian: my use case is mass-production
... including 10000 things
... the data model can be taken over by some TD instance
... information within a TD template will be used by the
instance
... technically, a TD template could have some
instance-specific data
... but would like to have a concrete example for that use case
Lagally: is there any additional requirement?
... we need to have some term for partial TD, etc.
... let's keep the discussion clean
... and define "Thing Description Template"
[33]Issue 454
[33] https://github.com/w3c/wot-architecture/issues/454
Sebastian: A TDT does not contain enough information to
identify or interact with a real Thing.
Lagally: (adds a comment to Issue 454)
... a TD Template is a description for a class of Things
... (adds some tweaks to the definition of "TD Template")
<ryuichi> (sorry, have to move another meeting. bye)
[34]proposed definition for "Thing Description Template"
[34] https://github.com/w3c/wot-architecture/issues/454#issuecomment-604272883
Lagally: let's wrap up the discussion
... talk to you later at the second call!
[Call 1 adjourned]
__________________________________________________________
Call 2
Prev minutes
[35]Virtual F2F minutes - Day 1
[35] https://www.w3.org/2020/03/16-wot-minutes.html#item05
Lagally: (goes through the minutes)
[36]Virtual F2F minutes - Day 2
[36] https://www.w3.org/2020/03/17-wot-minutes.html#item02
Lagally: (goes through the minutes)
McCool: sanity check for the use case template
... we should go through the whole minutes and create create
actions and issues
Lagally: (creates an issue for security checklist)
[37]Issue 472
[37] https://github.com/w3c/wot-architecture/issues/472
Lagally: (creates another issue to update the lifcycle use
case)
[38]Issue 473
[38] https://github.com/w3c/wot-architecture/issues/473
[39]Virtual F2F minutes - Day 4
[39] https://www.w3.org/2020/03/19-wot-minutes.html#item03
Lagally: (goes through the minutes)
[Zoltan joins]
Lagally: would take an action to clarify the Architecture call
times
<scribe> ACTION: Lagally to clarify the Architecture call times
McCool: some typo there?
... peofiles => profiles
Lagally: other than that, would approve all the Virtual F2F
minutes (Architecture part)
[40]Mar-12 minutes
[40] https://www.w3.org/2020/03/12-wot-arch-minutes.html
Lagally: (goes through the minutes)
... would like to approve these minutes as well
... still need final decision for the Virtual F2F minutes
during the next main call, though
Static HTML for REC publication
[41]Diff from the PR version
[41] https://w3c.github.io/wot-architecture/publication/rec/diff.html
Lagally: (goes through the diff file)
... this should be the final version for the V1 spec
(no problems within the HTML)
Issues and Pullrequests
[42]Issues
[42] https://github.com/w3c/wot-architecture/issues
[43]Issue 435
[43] https://github.com/w3c/wot-architecture/issues/435
Lagally: there is an issue for the fleet management use cases
Zoltan: we can have separate use cases depending on the targets
[44]Issue 469
[44] https://github.com/w3c/wot-architecture/issues/469
Zoltan: transportation use case could be split into separate
use cases depending on the vehicle
McCool: transportation should be a category
Lagally: (adds a comment to Issue 469 saying "see also #435")
[45]new comment for Issue 469
[45] https://github.com/w3c/wot-architecture/issues/469#issuecomment-604499014
[46]Pullrequest 463
[46] https://github.com/w3c/wot-architecture/pull/463
Lagally: remove use-case-example.md
McCool: fine
Lagally: (merges #463)
[47]Pullrequest 464
[47] https://github.com/w3c/wot-architecture/pull/464
Lagally: update use-case-template.md
... (merges #464)
<McCool> mm: under dependencies it would be helpful to list
work items, not just deliverables
<McCool> ... but can go ahead and merge this for now
Lagally: (updates use-case-template.md)
[48]updated use-case-template.md
[48] https://github.com/w3c/wot-architecture/blob/master/USE-CASES/use-case-template.md
[49]Pullrequest 467
[49] https://github.com/w3c/wot-architecture/pull/467
Lagally: update lifecycle diagram
Elena: latest change on commission state
[50]new lifecycle diagram
[50] https://github.com/w3c/wot-architecture/blob/master/proposals/WoT lifecycle diagram-WoT new lifecycle.svg
Lagally: wondering if GitHub can hosts the online version of
draw.io
Elena: (shares here screen showing the online version diagram)
... actors on the arcs
... manufacturer, service provider, network provider, device
owner
... and others?
... (adds edits)
... Device Owner or Service Provider between "Manufacture /
Decommissioned" state and "Bootstrapped / Onboarded" state
(discussion on the Actors)
McCool: ownership doesn't usually matter
... the point is whether having write permission or not
Kaz: btw, maybe this is kind of overkill at the moment, but at
some point we might want to think about apartment buildings in
addition to smart homes
McCool: right. apartment has mixture inside
... roles of person
Lagally: everybody has different scenario
Zoltan: what is the main purpose of this diagram then?
Lagally: to clarify the common model
McCool: one role is missing here
... state before manufacturing
Elena: an optional state?
McCool: basically this diagram is drawn from the service
provider's viewpoint
... precondition and postcondition
Lagally: would update the diagram to include all the points
discussed today
McCool: would like to consider Oliver's summarized lifecycle
descriptions on IETF Anima and OPC-UA
Elena: mapping between them and the states within this diagram?
McCool: maybe could add some vocabulary from them
Lagally: McCool, could you work on Oliver's diagram?
Zoltan: we should do a homework now
... overview of concrete protocols, etc.
Lagally: make sense
<McCool> mm: I can review. Make an issue and assign it to me
(if there isn't one already...)
<McCool> mm: basically I will look at Anima/Oliver's slides and
see if they align
<McCool> ... also, never mind, I will add the issue myself
right now
Lagally: there is an SVG version of the diagram on the
wot-architecture GitHub repo
<McCool> mm: new issue to review Anima terminology:
[51]https://github.com/w3c/wot-architecture/issues/474
[51] https://github.com/w3c/wot-architecture/issues/474
<inserted> ml: we should have an editable SVG version of the
diagram on GitHub
Kaz: how to identify who created the updated SVG diagram when?
maybe we need to use "YYYYMMDD-author-wot-lifecyle.svg" as the
file name?
Zoltan: we can create a subdirectory?
[Elena leaves]
Media use cases
Lagally: would like to talk with the media guys about the use
cases
... any updates from your side, Chris?
Chris: no concrete updates so far
... maybe need some more direct/individual approach to get
concrete feedback
... reaching out directly
... some of the possible use cases are related to the ones
generated by the MEIG (Web&TV IG) Home Network TF
... related to timing information
... kind of like Netflix experience
... watching a content from various environments
Lagally: ok
... but we should not preclude cloud-based approach
Chris: right
... maybe split into several use cases?
<McCool> mm: (sorry, I have to drop; ttyl)
<mlagally> tty
Kaz: maybe we might want to think about combination of home
network use cases and bullet chatting
... massive number of users accessing same content at once
... and share the users' feedback/comments as well as the basic
video content
Chris: may be an interesting combination
Lagally: anybody interested from the media side?
Chris: multi-room synchronized playback, etc.?
... the scenario itself might be similar
(though media requirements have been covered by HTML5
extensions)
Chris: can share some resources
Lagally: companion screen for additional information like audio
commentary
... accessibility is a possible use case
Chris: also immersive purposes using multiple cameras
... could share some links about research projects
... currently more research topics than products/services,
though
Lagally: we already have a template for use case description
[Zoltan leaves]
Lagally: so we can create a "bucket" for media use case
description based on the template :)
(generates a bucket use case description)
Chris: we can include the information about NHK's proposal
during the MEIG meeting at TPAC
[52]Hybridcast updates
[52] https://www.w3.org/2011/webtv/wiki/images/d/d1/MediaTimedEventsInHybridcast_TPAC20190916.pdf
[53]MediaTimedEvents in Hybridcast
[53] https://www.w3.org/2011/webtv/wiki/images/d/d1/MediaTimedEventsInHybridcast_TPAC20190916.pdf
<mlagally>
[54]https://github.com/w3c/wot-architecture/edit/master/USE-CAS
ES/media-information-references.md
[54] https://github.com/w3c/wot-architecture/edit/master/USE-CASES/media-information-references.md
Lagally: media-related bucket use case description above
<cpn> [55]https://2immerse.eu/motogp-at-home/
[55] https://2immerse.eu/motogp-at-home/
Chris: some more possible use cases (as R&D work) above
... we can show this bucket use case to the MEIG
... and ask them for feedback
Lagally: ok
... please let me add a disclaimer at the top
Chris: will share this with the MEIG guys
Lagally: tx!
[call 2 adjourned]
Summary of Action Items
[NEW] ACTION: Lagally to clarify the Architecture call times
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [56]scribe.perl version 1.154 ([57]CVS log)
$Date: 2020/04/05 08:23:39 $
[56] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[57] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 7 April 2020 03:59:45 UTC