- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Thu, 19 Dec 2019 00:50:31 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
https://www.w3.org/2019/12/18-wot-minutes.html
also as text below.
Thanks a lot for taking the minutes, Daniel!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT-IG/WG
18 Dec 2019
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#18_Dec_2019
Attendees
Present
Kaz_Ashimura, Michael_McCool, Michael_Lagally,
Dave_Raggett, David_Ezell, Kunihiko_Toumura,
Takahisa_Suzuki, Tetsushi_Matsuda, Daniel_Peintner,
Tomoaki_Mizushima, Ryuichi_Matsukura
Regrets
Sebastian
Chair
McCool
Scribe
dape
Contents
* [3]Topics
1. [4]Quick Updates
2. [5]WG Charter
3. [6]How to deal with minutes from the TF calls
4. [7]Proposed Rec
5. [8]F2F planning
6. [9]Status binding templates document
7. [10]Remaining calls in 2019 and first calls in 2020
8. [11]New TFs
9. [12]TF reports
* [13]Summary of Action Items
* [14]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: dape
Quick Updates
McCool: In contact with Singapore Govtech
... planning meeting for January
... will setup call
Lagally: Who is driving initiative ?
McCool: me and other (discussions during meetup in Singapore)
Lagally: Sounds interesting
McCool: please send me email if you are interested
WG Charter
<kaz> [15]updated Charter (the official version on the W3C
server should be also updated)
[15] http://w3c.github.io/wot/charters/wot-wg-charter-draft-2019.html
McCool: the AC review ended today but the W3M meeting also
occurs today
... and needed to send an agendra request for approval to W3M
yesterday
... so requested 1-month extension to finalize the recharter
procedure
... as for the AC review itself, got sufficient supporters
... added internal liason (IoT CG) and GS1 liason
... first meeting next year on Jan 8
<kaz> [Note: McCool pointed out there was a typo within the
proposed Charter, and Kaz has just fixed the typo (=missing
closing bracket for "Interoperability Profiles")]
How to deal with minutes from the TF calls
McCool: TF mintues have been sent to the Members list
... but got a request from a Member to send it to the public
list
... IF we do that, we would only do it for the future minutes
Lagally: Agree, going forward makes sense. Not for "old"
minutes
McCool: Should let people know first.... let's wait for
feedback till the beginning of the next year
... will send out an email about that for people not attending
this call
Proposed Rec
McCool: static HTML is fixed
... W3M requested to have a transition call
... scheduling call was difficult.. might need to wait till Jan
7th
... wait for confirmation of official charter, PR transition
... press release needs to wait
... suggest to organize marketing call with press release
F2F planning
McCool: sent an email to Mozilla, Mountain view location
... proposed 2 weeks in March
... still on flight
... for Helsinki, Zoltan?
Zoltan: We can host open day
... need to make reservation though
... need to decide about main venue
... down-town or close to Intel
McCool: Should reach out to T2TRG also
... shall we setup wiki pages?
Kaz: Yes
McCool: Great, should create wiki pages for both the F2F
meetings
Zoltan: 9-12 June is conference
... beginning of June is better than July
Kaz: will create wiki pages
<kaz> ACTION: kaz to create wiki pages for March/June f2f
meetings
Status binding templates document
(Ege has trouble with audio connection and need to dial-in
again; so this topic will be revisited later during the TF
reports)
Remaining calls in 2019 and first calls in 2020
McCool: believe we do not have any call this year
Lagally: will have architecture this week to continue the
lifecycle discussion
McCool: OK, i see.. but no TD call
... first main call, Jan 8 or Jan 15?
... holidays in early January
... looks Jan 8 we might have main call
... update wiki to reflect the calls
... security Jan 13
... scripting Jan 13
Lagally: architecture call, still waiting for outcome of doodle
poll
... however, week of Jan 6
... will decide tomorrow
McCool: TD call, not decided yet
Kaz: Sebastian mentioned Jan 10 would be OK during the WoT
Chairs call but let's leave it open for now
McCool: plan to change marketing time also
... at the moment we could use Testing/Plugfest call... Jan 8
Ege: I think doodle poll for marketing would be good
McCool: agree, this is only tempory
[Remaining calls in 2019]
Architecture - Dec 19
No other calls this year - no TD call Dec 20
[First calls in 2020]
Main call - Jan 8
Security - Jan 13
Scripting - Jan 13
Thing Description - Jan 10? Discuss in Jan 8 main call
Architecture - doodle TBD - week of Jan 6
Marketing - use Testing/Plugfest slot temporarily, starting Jan
8
New TFs
McCool: lot of discussions about discovery
... can also collaborate with external groups
... need discovery time slot
... should setup doodle
<inserted> (McCool and Kaz will have some more offline
discussion, and then create a doodle poll)
TF reports
McCool: Marketing, doodle in flight
Kaz: Dave has already posted a blog post on the IG page
<kaz> [16]Blog post on the IG page
[16] https://www.w3.org/WoT/IG/
Dave: right
... also we need to plan for re-chartering and when documents
proceed
McCool: Scripting
Zoltan: had a call on Monday
... outstanding PR for TD (version 1.1)
... data-schema vs content types
... we also discussed how to map errors
Ege: doing PlugFest experiments might help to make a decision
Zoltan: fingerprinting area
... need to keep that in mind
McCool: errors are mentioned in swagger and also used in
Mozilla environment
Lagally: many aspects, some are related to profile
Zoltan: please make comments to issue
<zkis> [17]https://github.com/w3c/wot-scripting-api/issues/200
[17] https://github.com/w3c/wot-scripting-api/issues/200
McCool: should continue discussion in scripting and
architecture
... security TF
... update on lifecycle discussion
... wait for architecture changes/updates
Lagally: Architecture call
... looked into lifecycle (with security)
... lifecycle goes beyond lifecycle of device
... looked into other standards
... plan to look into OCF and oneM2M
McCool: stakeholder definitions from security might go to
architecture
... TD TF?
... neither Taki nor Sebastian is here today
Ege: mainly talked about binding templates
... binding templates draft is ready for review
McCool: Can you send email that document is ready for review?
... suggest to plan resolution for publication on Jan 8
<ege>
[18]https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templat
es/pull/82.html version with the latest PR and to be editors
darft
[18] https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/82.html
Kaz: binding templates is an updated WG Note, so I don't expect
any problems
Ege: lot of dicussion w.r.t. MQTT
McCool: MQTT in current draft?
Ege: yes
... how can we have request and response
<ege> [19]https://github.com/w3c/wot-binding-templates/issues
[19] https://github.com/w3c/wot-binding-templates/issues
Ege: or about retain flag
... issues in binding templates
... MQTT is in the document, but not with these "advanced" use
of MQTT in WoT
Koster: take away: being more abstract in bindings
... cannot fully describe bindings... driver may take over
<ege> [20]https://en.wikipedia.org/wiki/Draft:Thing_Description
[20] https://en.wikipedia.org/wiki/Draft:Thing_Description
Ege: marketing TF
... wikipedia draft gets pushed back
... will keep pinging
McCool: AOB?
... next main call on Jan 8
Kaz: quick note, 1 month extension for the current WoT WG
Charter has been approved!
[adjourned]
Summary of Action Items
[NEW] ACTION: kaz to create wiki pages for March/June f2f
meetings
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [21]scribe.perl version 1.154 ([22]CVS log)
$Date: 2019/12/18 15:48:53 $
[21] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[22] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 18 December 2019 15:50:40 UTC