- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 24 May 2021 18:31:05 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2021/04/19-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Christian!
Kazuyuki
---
[1]W3C
[1] https://www.w3.org/
WoT Discovery
19 April 2021
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#19_April_2021
[3] https://www.w3.org/2021/04/19-wot-discovery-irc
Attendees
Present
Andrea_Cimmino, Christian_Glomb, Farshid_Tavakolizadeh,
Kaz_Ashimura, Kunihiko_Toumura, Michael_Koster,
Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
glomb
Contents
1. [4]Agenda bashing
2. [5]Prev minutes
3. [6]WD publication
4. [7]PR 152
5. [8]PR 153
6. [9]PR 155
Meeting minutes
Agenda bashing
<FarshidT> Hosting contexts under w3.org: [10]https://
github.com/w3c/wot-discovery/issues/148
[10] https://github.com/w3c/wot-discovery/issues/148
[11]https://github.com/w3c/wot-discovery/issues/154
[11] https://github.com/w3c/wot-discovery/issues/154
Resolution on April 28th
Prev minutes
<kaz> [12]Apr-12
[12] https://www.w3.org/2021/04/12-wot-discovery-minutes.html
Minutes from last week - Ben Francis needed for Security
Wrt object security
McCool: Registration ID meant as local ID
Minutes approved
WD publication
<kaz> [13]Issue 154 - Publish updated WD
[13] https://github.com/w3c/wot-discovery/issues/154
glomb Two groups of comments: Editorial wrt http, non-editorial
wrt server-side information
McCool Submit PR for it
McCool Would add implication for implementors
Farshid Server-side content negotiation still possible
Farshid: What is the use case for pagination in body?
McCool - Has advantages for object security.
McCool - Could you tweak headers?
Farshid: Will not have REST API more SOAP like.
McCool: In the header consisting w/ REST
Christian: Developers not using it.
Christian: How does "wire format" impair RDF processing?
Andrea: JSON-LD a way to express RDF
Cannot translate mixed payloads.
Mixing formats.
McCool: What about having JSON-LD envelope?
Farshid: What was the problem with having "outside" context?
Christian: Should present "envelope" based pagination.
See comments in issue
Andrea: JSON envelope was changed since it was incorrect.
Farshid already provided a summary on pagination discussion.
[14]https://github.com/w3c/wot-discovery/issues/154
[14] https://github.com/w3c/wot-discovery/issues/154
McCool Comments
Spec. is http centric. [15]New issue:
[15] https://github.com/w3c/wot-discovery/issues/157
PR 152
[16]https://github.com/w3c/wot-discovery/pull/152 PR 152 - Add
Registration ID to Enriched TD
[16] https://github.com/w3c/wot-discovery/pull/152
Farshid: Found a way identifying anonymous TDs (6.2.1.1,
6.2.1.2)
McCool Breaks canonicalization and signing
Farshid: Must "un-enrich"
To be described
Enrichment needed for anon. TDs otherwise not
McCool Should also be discussed in WoT-Security wrt UUID
Farshid will create issue about this.
PR 153
[17]https://github.com/w3c/wot-discovery/pull/153 PR 153 -
Listing with pagination
[17] https://github.com/w3c/wot-discovery/pull/153
Header based pagination
McCool JSONpath queries instead of envelope based pagination
Header based pagination -> optional
According to RFC8288
Not identical to LDP paging
McCool Merged for future proposal, only optional
PR 155
[18]https://github.com/w3c/wot-discovery/pull/155 PR 155 -
Simplifying the events API query and payload
[18] https://github.com/w3c/wot-discovery/pull/155
Events API
Section Notification
McCool: Merge it to have a foundation for further discussions.
"Anon." identifier sent along
Minutes manually created (not a transcript), formatted by
[19]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).
[19] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 24 May 2021 09:31:10 UTC