- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 10 Jan 2022 18:14:23 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2021/11/15-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
15 November 2021
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#15_November_2021
[3] https://www.w3.org/2021/11/15-wot-discovery-irc
Attendees
Present
Andrea_Cimmino, Christian_Glomb, Cristiano_Aguzzi,
Farshid_Tavakolizadeh, Kaz_Ashimura, Kunihiko_Toumura,
Michael_McCool, Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
glomb, kaz
Contents
1. [4]Minutes
2. [5]Agenda
3. [6]JSON Path
Meeting minutes
Minutes
[7]https://www.w3.org/2021/11/08-wot-discovery-minutes.html
[7] https://www.w3.org/2021/11/08-wot-discovery-minutes.html
Approved
Agenda
no changes to the agenda
JSON Path
[8]JSONPath - draft-ietf-jsonpath-base-02
[8] https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-02.txt
McCool: Update on JSON path
IETF- still draft
Important issues:
- Selectors applied in sequence; each has input and output;
when searching for keywords - no regex selector yet defined -
exact comparison required
- "in": Can look for number or path but not string in string
AI for us: generate some "typical" queries needed
Cristiano agrees on found issues
Cristiano: should we continue w/ own query mechanism?
McCool: Several options: - Only rely on Xpath, but only one
implementation at the moment
- Or: define own query mechanism
Cristiano: Yes, but should be simple to implement, just
filtering instead of search
See: [9]https://github.com/w3c/wot-discovery/issues/231
[9] https://github.com/w3c/wot-discovery/issues/231
Minutes manually created (not a transcript), formatted by
[10]scribe.perl version 159 (Fri Nov 5 17:37:14 2021 UTC).
[10] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 10 January 2022 09:14:28 UTC