- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Sun, 12 Apr 2020 12:21:24 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
https://www.w3.org/2020/04/01-wot-minutes.html
also as text below.
Thanks a lot for taking the minutes, Zoltan!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-IG/WG
01 Apr 2020
Attendees
Present
Kaz_Ashimura, Sebastian_Kaebisch, Michael_McCool,
Jaime_Jimenez, Michael_Lagally, Daniel_Peintner,
Ege_Korkan, Kunihiko_Toumura, Taki_Kamiya,
Michael_Koster, Zoltan_Kis, Ryuichi_Matsukura,
Tetsushi_Matsuda, Tomoaki_Mizushima
Regrets
Takahisa_Suzuki, David_Ezell
Chair
Sebastian, McCool
Scribe
zkis
Contents
* [2]Topics
1. [3]Agenda
2. [4]Review minutes
3. [5]Virtual F2F minutes
4. [6]Quick updates
5. [7]REC transition
6. [8]Press release
7. [9]F2F planning
8. [10]node-wot
9. [11]Task force updates
* [12]Summary of Action Items
* [13]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: zkis
Agenda
Sebastian: agenda bashing
... Jaime please make an introduction
Jaime: worked with various protocols and data models (LwM2M,
CoAP, IPSO, ...)
Review minutes
<kaz> [14]Mar-25 minutes
[14] https://www.w3.org/2020/03/25-wot-minutes.html
Sebastian: reviewing past minutes
... any objections?
[no objections, minutes approved]
Virtual F2F minutes
Sebastian: asking task forces if they approved the past minutes
from the virtual F2F
[all approved]
<kaz> [15]Day 1
[15] https://www.w3.org/2020/03/16-wot-minutes.html
<kaz> [16]Day 2
[16] https://www.w3.org/2020/03/17-wot-minutes.html
<kaz> [17]Day 3
[17] https://www.w3.org/2020/03/18-wot-minutes.html
<kaz> [18]Day 4
[18] https://www.w3.org/2020/03/19-wot-minutes.html
Quick updates
Sebastian: DST changed in EU, meetings back to normal
McCool: we should go through the meetings and check if calendar
invites need updating
Zoltan: we should mention UTC times for info
Koster: the invite is based on Boston time zone
... as a group we could decide to stick to UTC, but would cause
problems to people who use W3C time (US eastern time)
Lagally: UTC is more used globally than Eastern Time
McCool: this is W3C policy
<kaz> [19]Note on the Architecture call
[19] https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Schedule_and_WebEx
Kaz: agree with McCool
... UTC is fine but we could not resolve the whole issue (DST
differences)
... using UTC would be very useful for countries without DST
but not for US or European countries
... we should be clear about when the time zones change
McCool: the least confusion would be to use the W3C policy,
i.e. Boston time as reference
Zoltan: just include UTC as well in the invite :)
<kaz> [20]time&date including UTC :)
[20] https://www.timeanddate.com/worldclock/converter.html?iso=20200402T060000&p1=137&p2=43&p3=tz_at&p4=1440&p5=136&p6=195&p7=101&p8=236&p9=248
Kaz: pasted a converter link including UTC for convenience
Sebastian: it's always a mess anyway, so we need to take care
to organize
McCool: will send invites
Sebastian: Singapore GovTech call?
McCool: we went to 2 weeks cadence
Sebastian: news about the PoC with Conexxus?
McCool: some internal meetings, more info later
REC transition
Sebastian: we have approval
... to make a public REC
[21]Transition request
[21] https://github.com/w3c/transitions/issues/236
Lagally: what changes are planned for the press release?
Sebastian: next topic
Press release
Sebastian: Alan Bird provided new version
<kaz> [22]proposed draft
[22] https://w3c.github.io/wot-marketing/pressrelease-wot-rec.html
<kaz> [23]remaining issues
[23] https://github.com/w3c/wot-marketing/issues
McCool: everyone who made testimonial should review
... we could mention languages and frameworks like Python,
node-js
Sebastian: MK mentioned to be working on a testimonial?
Koster: will confirm later this week
Sebastian: ML, did that answer the question?
Lagally: yes
... concerned about the delays
Sebastian: April 9 is still OK?
Lagally: yes
McCool: the question is the deadline for testimonials etc
Sebastian: we could have a testimonial on a later day
Koster: could give a proposed text and then tell when it's
approved
McCool: made a placeholder for SmartThings
Sebastian: we are also waiting for Mozilla's statements
McCool: trying to figure out whom to talk to
... to check can we mention their implementation
Sebastian: will contact also other people from Mozilla IoT
Kaz: we can add testimonials at any point, of course it's nice
to have everything by one go, but we can include them also
later
F2F planning
Sebastian: we will have a virtual F2F instead of Helsinki
McCool: the final resolution is not yet made
... did we check with Aalto?
Zoltan: not yet
... it is expected the epidemic still be there in June
McCool: then we can make the decision about virtual F2F
Sebastian made a proposal
<sebastian> proposal: due to the corona situation, the Helsinki
f2f meeting will be a virtual f2f meeting
[no objections]
RESOLUTION: due to the corona situation, the Helsinki f2f
meeting will be a virtual f2f meeting
Ege: regarding T2TRG, what about the annual event on April 9?
Koster: there will be a CoRE meeting together with T2TRG
... with hackathon, interop testing etc
... at least personally I am interested
McCool: let's discuss this in the Plugfest call
... we could insert this into our event list
Sebastian editing the WoT WebConf wiki
[24]Events section
[24] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Events
Kaz: why don't we add past and future events?
... as separate sections?
Sebastian: right now?
<mjk> [25]https://github.com/t2trg/wishi/wiki/Agenda-items
[25] https://github.com/t2trg/wishi/wiki/Agenda-items
<mjk> April 9th (Thursday), 7:00-11:00 PDT (16:00-20:00 CET,
14:00-18:00 UTC)
McCool: let's discuss the details in the Plugfest call
Sebastian: please register to these events
node-wot
Sebastian: there was a question if there should be a separate
meeting for that?
... it is developed under the Eclipse Foundation, there is no
agreement with W3C yet
Kaz: we should discuss this in marketing call for liaison with
Eclipse, and in the plugfest/testing call for the technical
issues
McCool: we need some developer support and outreach
... there have been requests for that
... so we need to figure that out
... agreed we should discuss under marketing
Task force updates
Zoltan: discussed Events, semantic API (needs developer
feedback)
... also how to expose values (mediaType etc)
Sebastian: will join the next meeting
Lagally: on the Thing Template we already had a discussion in
Architecture
... we align it there
... terminology should be agreed in Architecture, don't
fragment the discussion
Sebastian: it's not about to make an agreement, just to
understand
... the init dictionary etc
Lagally: sounds good
Koster: would like to follow up on TD templates vs fragments
... to say where do these come from
<mjk> ackm
Lagally: will discuss this in Architecture
<McCool> [26]https://www.w3.org/2020/03/30-wot-sec-minutes.html
[26] https://www.w3.org/2020/03/30-wot-sec-minutes.html
McCool: in security call discussed lifecycle
... we will follow up in Architecture, second call
... discussed the issue of keys and what kind of keys needed
... manufacturing, site, app keys
Zoltan: site keys are not standard terms
McCool: looked at PRs and merged Oliver's PR
<McCool>
[27]https://www.w3.org/2020/03/30-wot-discovery-minutes.html
[27] https://www.w3.org/2020/03/30-wot-discovery-minutes.html
McCool: in the Discovery call, we discussed Vorto
... related to templates and class definitions
... we could define TD templates for Vorto
Koster: they are more like type definitions
McCool: discussed models vs directory vs OpenAPI, edgeX, Vorto
... created issues
Koster: I requested some example Vorto definitions we could use
McCool: discussed node-wot run in Docker
... for the EdgeX use case
Sebastian: wondering if Vorto model would match our TD
template?
McCool: the reason for partial TDs is search/discovery
... we want to do that
... the Vorto stuff is somewhat different
Koster: would be nice to have a serialization of models
... e.g. TD template being a serialization model
(Koster leaves)
McCool: the question is if we have a common model or are they
in conflict
... if translation is possible
... we are currently discussing that
Lagally: in architecture first call, some bookkeeping,
discussed TD template definition
[28]Mar-26 Architecture minutes
[28] https://www.w3.org/2020/03/26-wot-arch-minutes.html
Lagally: in the second call, discussed lifecycle, running out
of time with that
... tomorrow we allocate the second call for that discussion
... in addition there are 3-4 PRs
... discuss use cases for media
Ege: about the plugfest call, we discussed about VPN setup, the
use of node-wot in general
... we should find more people
... it's important to add features to node-wot
Sebastian: in marketing call, discussed the press release and
web page
... in the TD call, discussed topics for the virtual F2F
... on efficient TD representations, by Taki and Daniel
... also about Events
... on the bindings call, no topics
... any final questions?
[adjourned]
Summary of Action Items
Summary of Resolutions
1. [29]due to the corona situation, the Helsinki f2f meeting
will be a virtual f2f meeting
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [30]scribe.perl version 1.154 ([31]CVS log)
$Date: 2020/04/12 03:18:59 $
[30] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[31] http://dev.w3.org/cvsweb/2002/scribe/
Received on Sunday, 12 April 2020 03:24:24 UTC