15:02:41 RRSAgent has joined #wot-discovery 15:02:41 logging to https://www.w3.org/2021/03/08-wot-discovery-irc 15:02:55 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#8_March_2021 15:03:03 meeting: WoT Discovery 15:03:32 present+ Kaz_Ashimura, Michael_McCool, Christian_Glomb, Farshid_Tavakolizadeh, Kunihiko_Toumura 15:05:29 FarshidT has joined #wot-discovery 15:05:32 Mizushima has joined #wot-discovery 15:06:28 topic: minutes 15:06:36 scribenick: FarshidT 15:07:10 -> https://www.w3.org/2021/03/01-wot-discovery-minutes.html March-1 15:07:35 no objections. Publishing minutes. 15:08:33 cris has joined #wot-discovery 15:09:25 topic: discussions points 15:09:43 kaz: ongoing discussion related to pagination in the scripting API 15:10:02 s/ongoing/some/ 15:10:08 s/API/API today/ 15:10:26 ca: streaming of TDs instead of paginating 15:10:51 acimmino has joined #wot-discovery 15:11:59 mmc: incremental loading of TDs, need to match the underlying networking protocol 15:12:38 kaz: small devices may need to extract TD fragments/elements one by one 15:13:16 mmc: scripting API can use JSONPath to select parts of the TD 15:13:48 mmc: maybe JSONPath should be added an optional feature for self-describing devices 15:13:55 s/one by one/one by one, but the Scripting TF wanted to know about the detailed use case scenario before thinking about the details. that was today's discussion./ 15:14:10 s/added an/added as an/ 15:15:10 mmc: There is PR to clarify fragment from element 15:15:51 s/clarify/distinguish/ 15:18:24 rrsagent, make log public 15:18:30 rrsagent, draft minutes 15:18:30 I have made the request to generate https://www.w3.org/2021/03/08-wot-discovery-minutes.html kaz 15:19:51 present+ Andrea_Cimmino, Cristiano_Aguzzi, Tomoaki_Mizushima 15:19:55 Chair: McCool 15:20:25 ft: if self-describing device cannot perform the filtering, it should reject to avoid surprise on the client side (unexpected model, size) 15:20:56 ca: the filtering could be on a dedicated endpoint, similar to the TDD 15:22:55 Issue: https://github.com/w3c/wot-discovery/issues/130 15:23:34 s/130/132/ 15:25:07 topic: plugfest outcome 15:26:18 -> https://github.com/w3c/wot-testing/issues/122 wot-testing issue 122 - Create Outcomes Presentation for 2021.03 Plugfest 15:26:52 rrsagent, draft minutes 15:26:52 I have made the request to generate https://www.w3.org/2021/03/08-wot-discovery-minutes.html kaz 15:28:19 mm: wonders if the next plugfest is in October during TPAC 15:28:39 kaz: if we don't schedule any additional meetings, yes 15:29:01 ... probably we need to hold testfests to check the implementation status, though 15:29:30 ft: need to focus on closing critical issues, before implementing more 15:30:06 +1 15:30:18 mmc: we could remove less important features 15:30:42 mmc: pagination could be removed. 15:31:32 ac: adding pagination to ontology is not appropriate. We can try to remove the pagination from ontology and move the headers 15:31:50 s/the/them/ 15:32:25 ac: commented on https://github.com/w3c/wot-discovery/issues/54#issuecomment-792660587 15:32:42 https://www.w3.org/TR/ldp-paging/ 15:32:58 mmc: Linked Data Platform Paging is a note, not a standard 15:33:23 ac: this means we need to rely on the protocol for pagination 15:33:31 s/ac/ca/ 15:34:31 ca: other protocols may have their own pagination mechanism 15:35:49 ac: this is an http solution, we don't need to worry about other hypothetical protocols 15:36:00 mmc: need to also check if we can paginate within a TD 15:37:50 mmc: we have to make a decision on this, latest by March 29th 15:39:42 ft: the header-based proposal was similar. Since we need to rely on HTTP headers and spec and return a plain array, there is not much to decide. 15:40:05 cg: can we support several mechanisms? Not just one? 15:41:01 ca: shouldn't other responses also support pagination? 15:41:18 s/responses/endpoints/ 15:41:51 mmc: pagination annotation in TD may be useful 15:42:11 topic: cancellations 15:42:39 mmc: no calls in the next two, due to conflicts with F2F 15:44:14 mmc: we need to continue working on the issues and create PRs in the meantime 15:44:18 s/two,/two weeks,/ 15:44:42 https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-03-online-f2f 15:45:20 topic: F2F slides 15:45:25 upload to https://github.com/w3c/wot/tree/main/PRESENTATIONS/2021-03-online-f2f 15:46:30 mmc: discovery meeting is on Mar 17th (next Wednesday) 15:48:30 topic: JSONPath 15:51:37 mmc: need to change the reference in the draft 15:52:00 update JSONpath ref to point at draft-ietf-jsonpath-jsonpath/ 15:53:03 topic: PR Updated ontology source code, diagrams, and spec text 15:53:06 https://github.com/w3c/wot-discovery/pull/127 15:55:01 ac: Removed the id from RegistrationInfo, because if there is an id there, it would be the RegistrationInfo's ID, not the TD 15:56:08 mmc: the context URL need to change in future to use the w3.org domain 15:56:46 kaz: the current URL is fine for the editor's draft 15:59:10 no objections to merging 15:59:22 s/draft/draft, but what concrete URL do we want to use for the "update"? 16:00:48 topic: PR updates to geolocation proposal 16:00:51 https://github.com/w3c/wot-discovery/pull/128 16:02:27 topic: PR Specify additional responses 16:02:36 https://github.com/w3c/wot-discovery/pull/131 16:03:10 merged 16:03:32 [adjourned] 16:03:37 rrsagent, draft minutes 16:03:37 I have made the request to generate https://www.w3.org/2021/03/08-wot-discovery-minutes.html kaz 17:45:05 Zakim has left #wot-discovery 20:18:24 zkis has joined #wot-discovery 20:25:54 zkis2 has joined #wot-discovery