<kaz> scribenick: glomb
Agenda approved
Minutes https://www.w3.org/2020/11/23-wot-discovery-minutes.html typos fixed by Kaz - approved
Half a year to get through entire process from now on - latest Dec 2021
<kaz> Updated publication schedule
1st of July -> CR transition
<kaz> Milestones calculator
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
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 https://github.com/w3c/wot-discovery/issues/99
Issue name updated
Lot's of libraries out for implementing patch
https://github.com/w3c/wot-discovery/pull/102 - merged
Koster - RFC7396 better choice than RFC6902
https://github.com/w3c/wot-discovery/issues/94
<scribe> Closed due to the discussion before
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?
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)
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> comments for Issue 98 updated
<kaz> [adjourned]