- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 16 Dec 2020 14:11:44 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/11/30-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Christian!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
WoT Discovery
30 Nov 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#30_November_2020
Attendees
Present
Kaz_Ashimura, Michael_McCool, Andrea_Cimmino,
Farhsid_Tavakolizadeh, Kunihiko_Toumura,
Christian_Glomb, Tomoaki_Mizushima, Michael_Koster
Regrets
Chair
McCool
Scribe
Christian_Glomb
Contents
* [3]Topics
1. [4]Agenda
2. [5]Prev minutes
3. [6]Scheduling
4. [7]PR 102
5. [8]Issue 94
6. [9]Issue 104
* [10]Summary of Action Items
* [11]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: glomb
Agenda
Agenda approved
Prev minutes
Minutes
[12]https://www.w3.org/2020/11/23-wot-discovery-minutes.html
typos fixed by Kaz - approved
[12] https://www.w3.org/2020/11/23-wot-discovery-minutes.html
Scheduling
Half a year to get through entire process from now on - latest
Dec 2021
<kaz> [13]Updated publication schedule
[13] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Deliverable_and_F2F_Meeting_Plan
1st of July -> CR transition
<kaz> [14]Milestones calculator
[14] https://w3c.github.io/spec-releases/milestones/
Stable draft two months before
1st of May 2021
Preliminary implementation until 1st of May, then clean up
Let's think about primary and stretched goals
PR 102
[15]https://github.com/w3c/wot-discovery/pull/102
[15] https://github.com/w3c/wot-discovery/pull/102
Farshid: Cited RFC and changed one statement to make it
compatible with it
In TD Update section
Content-type application/merge-patch+json
Cited RFC in "TD terminology"
Validation to be described in own section
See McCools comment in
[16]https://github.com/w3c/wot-discovery/issues/99
[16] https://github.com/w3c/wot-discovery/issues/99
Issue name updated
Lot's of libraries out for implementing patch
[17]https://github.com/w3c/wot-discovery/pull/102 - merged
[17] https://github.com/w3c/wot-discovery/pull/102
Koster - RFC7396 better choice than RFC6902
Issue 94
[18]https://github.com/w3c/wot-discovery/issues/94
[18] https://github.com/w3c/wot-discovery/issues/94
<scribe> Closed due to the discussion before
Issue 104
[19]https://github.com/w3c/wot-discovery/issues/104
[19] https://github.com/w3c/wot-discovery/issues/104
Use case for encrypted TDs?
Use case for (signed) fragments?
Canonicalization quite tricky for JSON
Signatures can be broken easily
Trust endpoint or trust directory?
[20]https://github.com/w3c/wot-discovery/issues/98
[20] https://github.com/w3c/wot-discovery/issues/98
Can trust your own directory, then signing makes sense
Farshid: some proposals already there (see: links in issue)
[21]https://github.com/w3c/wot-discovery/issues/18
[21] https://github.com/w3c/wot-discovery/issues/18
Either additions to TD or separate endpoint
Inband info can be easily queried
<mjk> Does it mean the TD with embedded metadata can be scanned
for metadata
Metadata can be queried
Will be sorted by Farshid (pros and cons)
Metadata? Directory data? TD management data?
Then figure out pagination
<kaz> [22]comments for Issue 98 updated
[22] https://github.com/w3c/wot-discovery/issues/98
<kaz> [adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [23]scribe.perl version ([24]CVS log)
$Date: 2020/12/16 05:09:53 $
[23] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[24] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 16 December 2020 05:11:50 UTC