- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 10 Jan 2022 18:08:27 +0900
- To: public-wot-wg@w3.org
available at: https://www.w3.org/2021/10/18-wot-discovery-minutes.html also as text below. Thanks a lot for taking the minutes, Farshid! Kazuyuki --- [1]W3C [1] https://www.w3.org/ WoT Discovery 18 October 2021 [2]IRC log. [2] https://www.w3.org/2021/10/18-wot-discovery-irc Attendees Present Cristiano_Aguzzzi, Farshid_Tavakolizadeh, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool Regrets Christian_Glomb Chair McCool Scribe FarshidT Contents 1. [3]Minutes review 1. [4]Sep 20th Minutes 2. [5]Oct 4th Minutes 2. [6]PRs 1. [7]PR: Clarify validation statements (#230) 3. [8]F2F action items 1. [9]Simplified JSONPath 4. [10]Next meeting Meeting minutes Minutes review Sep 20th Minutes <McCool> [11]https://www.w3.org/2021/09/ 20-wot-discovery-minutes.html [11] https://www.w3.org/2021/09/20-wot-discovery-minutes.html no objections to publishing the minutes Oct 4th Minutes <kaz> [12]https://www.w3.org/2021/10/ 04-wot-discovery-minutes.html [12] https://www.w3.org/2021/10/04-wot-discovery-minutes.html McCool: Farshid to be added to guests list for this meeting no objections to publishing PRs PR: Clarify validation statements (#230) [13]https://github.com/w3c/wot-discovery/pull/230 [13] https://github.com/w3c/wot-discovery/pull/230 McCool: It would be good to add an assertion in the validation section to clarify the directory does the validation. Also, to say that the directory MAY reject the request if the input is invalid. [14]https://github.com/w3c/wot-discovery/issues/ 99#issuecomment-945823118 [14] https://github.com/w3c/wot-discovery/issues/99#issuecomment-945823118 no objections to merging F2F action items <kaz> [15]Day 1 [15] https://www.w3.org/2021/10/05-wot-minutes.html <kaz> [16]Day 2 [16] https://www.w3.org/2021/10/07-wot-minutes.html <kaz> [17]Open Day 1 [17] https://www.w3.org/2021/10/11-wot-minutes.html <kaz> [18]Open Day 2 [18] https://www.w3.org/2021/10/14-wot-minutes.html Simplified JSONPath McCool: simple keyword search McCool: could be added to appendix Farshid: or non-normative section in place Farshid: JSONPath is also used for selection Farshid: keyword search could also be complicated (search in array, dictionary key/values, etc). Limiting to root level would make it simple Cristiano: maybe simple keyword search (no jsonpath) would be better McCool: Agrees to JSONPath keyword search, limited to the top level. McCool: the keywork search would be a separate API e.g. /search/keyword?query= McCool: maybe limited to title and descriptions Farshid: string search is often not enough. What about datetime attributes? McCool: we need to mandate at least one way to allow searching. The directory could contain millions of entires. McCool: writing a issue to discuss the problem in detail [19]https://github.com/w3c/wot-discovery/issues/231 [19] https://github.com/w3c/wot-discovery/issues/231 Farshid: there could be many different simple use cases. It is hard to cover all. Kaz: we need to clarify the scenarios that we're addressing. Farshid: full text search on millions of items could longer than querying all and doing efficient filtering on the client side McCool: true but it would consume less networking resources Next meeting cancelled Minutes manually created (not a transcript), formatted by [20]scribe.perl version 147 (Thu Jun 24 22:21:39 2021 UTC). [20] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 10 January 2022 09:08:31 UTC