11:59:07 <RRSAgent> RRSAgent has joined #wot-script
11:59:07 <RRSAgent> logging to https://www.w3.org/2022/02/07-wot-script-irc
11:59:13 <kaz> meeting: WoT Scripting API
11:59:24 <kaz> present+ Kaz_Ashimura, Jan_Romann
12:01:07 <dape> dape has joined #wot-script
12:02:40 <kaz> present+ Daniel_Peintner
12:03:08 <JKRhb> JKRhb has joined #wot-script
12:03:39 <kaz> regrets+ Zoltan
12:05:15 <cris> cris has joined #wot-script
12:05:21 <Mizushima> Mizushima has joined #wot-script
12:06:11 <kaz> present+ Cristiano_Aguzzi, Michael_McCool
12:07:12 <dape> scribe: dape
12:07:31 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#7_February_2022
12:07:42 <dape> TOPIC: Previous minutes
12:07:47 <dape> --> https://www.w3.org/2022/01/31-wot-script-minutes.html
12:07:57 <kaz> s/html/html Jan-31/
12:08:04 <kaz> present+ Toamoaki_Mizushima
12:09:36 <dape> ... Minutes approved
12:10:02 <dape> TOPIC: PRs
12:10:11 <dape> SUBTOPIC: Fix #355: change use cases,
12:10:19 <dape> -> https://github.com/w3c/wot-scripting-api/pull/375
12:11:36 <kaz> s/375/375 PR 375 - Fix #355: change use cases/
12:12:48 <kaz> q+
12:14:02 <kaz> ack k
12:14:48 <kaz> mm: the text "The following scripting use case scenarios are supported" is fine
12:14:50 <dape> Kaz: think section should read "Scripting Use Cases"
12:15:33 <dape> s/"Scripting Use Cases"/Scripting Use Case Scenarios"
12:16:29 <kaz> s/think section should read Scripting Use Case Scenarios"/agree. so would suggest the title also should say "Scripting Use Case Scenarios"./
12:16:46 <dape> DP: suggest to wait for Zoltans feedback
12:16:55 <kaz> i/Kaz:/scribenick: kaz/
12:17:08 <kaz> i/DP:/scribenick: dape/
12:17:09 <dape> TOPIC: Issues
12:17:35 <dape> SUBTOPIC: Using a callback-based approach for Discovery?,
12:17:40 <dape> --> https://github.com/w3c/wot-scripting-api/issues/364
12:18:16 <kaz> s/364/Issue 364 - Using a callback-based approach for Discovery?/
12:18:21 <kaz> rrsagent, make log public
12:18:26 <kaz> rrsagent, draft minutes
12:18:27 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/07-wot-script-minutes.html kaz
12:18:33 <cris> q?
12:18:39 <dape> MMC: discovery API should deal with all possible options
12:18:53 <cris> q+
12:18:56 <kaz> chair: Daniel
12:19:34 <kaz> s/-->/->/g
12:19:37 <kaz> rrsagent, draft minutes
12:19:37 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/07-wot-script-minutes.html kaz
12:20:15 <kaz> s/... Minutes approved/Minutes approved/
12:20:21 <dape> DP: we currentle have direct and directory
12:21:11 <dape> CA: w.r.t. registration is left to runtime
12:21:31 <dape> ... shall we make this explicit
12:21:50 <dape> MMC: self- description is another argument
12:21:55 <dape> ... like .well-known
12:21:55 <kaz> i|we curr|-> https://w3c.github.io/wot-scripting-api/#the-discoverymethod-enumeration 10.2 The DiscoveryMethod enumeration|
12:21:58 <kaz> rrsagent, draft minutes
12:21:58 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/07-wot-script-minutes.html kaz
12:22:53 <dape> MMC: need to re-read the scripting spec
12:23:02 <dape> ... generate issues for missing features
12:23:25 <dape> CA: I suggest to wait for feature freeze of discovery
12:23:34 <dape> MMC: should happen soon
12:24:07 <dape> CA: exploration methods only ?
12:24:20 <dape> MMC: simple call, just "discover"
12:24:52 <dape> CA: problematic to be implemented
12:25:05 <dape> MMC: testing of discovery
12:25:13 <dape> ... client-side implementations
12:25:26 <dape> ... "introduction" is open-ended
12:26:00 <dape> ... DNSD should be supported
12:26:18 <dape> ... need external management API
12:27:12 <dape> DP: Separate API
12:27:44 <dape> CA: filtering TDs (query) ?
12:27:58 <dape> ... tricky to filter
12:28:08 <dape> MMC: Filters are a real problem
12:28:16 <dape> ... SPARQL is heavy weight
12:28:24 <dape> .... JSON-PATH is not ready yet
12:28:34 <dape> ... XPATH lacks implementations
12:29:00 <dape> ... we ended up not having mandatory query mechanism
12:29:16 <dape> ... should support filter like JSON-Path in node-wot
12:29:36 <dape> ... do apply filters locally
12:30:32 <dape> CA: not suggest JSON-path on client-side
12:30:39 <dape> ... implementation burden
12:31:57 <dape> CA: application knows TD
12:32:03 <dape> ... how can I fetch TD
12:32:10 <dape> ... using discovery API?
12:32:28 <dape> MMC: optional argument is fine with URL
12:32:35 <kaz> s/JSON-PATH/JSONPath/
12:32:41 <kaz> s/JSON-path/JSONPath/
12:32:50 <kaz> s/XPATH/XPath/
12:33:27 <dape> ... description of discovery process is missing
12:34:16 <dape> ... set of TDs
12:34:25 <cris> q+
12:35:01 <dape> q?
12:36:08 <dape> CA: discovery process would be great, we just follow
12:36:49 <dape> ... Scripting task-force needs to review the process
12:37:03 <dape> MMC: need to still describe it
12:37:15 <dape> ... proposed text in introduction section
12:37:58 <dape> CA: Sounds great
12:39:31 <dape> DP: different discovery entry points
12:39:52 <dape> MMC: options to set
12:40:04 <dape> ... we might want to have multiple options
12:40:55 <dape> CA: JS allows to check for which method is supported
12:41:10 <dape> MMC: configuration option might be better
12:41:53 <dape> MMC: "automatic" method is missing
12:43:13 <dape> ... I am working on integrating discovery services
12:44:01 <dape> DP: unsure about "automatic" method
12:44:18 <dape> MMC: question about limiting the scope
12:44:24 <dape> ... in local networks it might be fine
12:44:40 <dape> we lack geo-spatial control
12:45:52 <dape> MMC: discovery does support mDNS etc
12:46:47 <dape> ... "local" could be local discovery (like "automatic" in local network)
12:46:54 <dape> CA: what about BT ?
12:46:56 <dape> MMC: is local
12:47:15 <dape> CA: What about process?
12:47:28 <dape> ... partially describe it
12:47:48 <dape> MMC: there is an informative description
12:47:53 <dape> ... should make it more formal
12:48:06 <dape> ... but we are running out-of-time
12:49:00 <dape> DP: timeline?
12:49:08 <dape> MMC: overdue, last week
12:49:35 <dape> ... best we can do, having informative description
12:50:36 <dape> <McCool needs to leave>
12:50:46 <dape> MMC: will create issue with adding "local" back
12:51:18 <dape> ... will re-read the document
12:51:33 <dape> ... self-description
12:51:39 <dape> CA: left to implementation?
12:52:20 <dape> MMC: when exposing ... like under .well-known
12:52:31 <dape> ... how to decide where to broadcast
12:53:13 <dape> CA: opposition in scripting: expose() makes it available
12:53:59 <dape> MMC: self description should not be required..  there might be cases you don't want
12:54:51 <dape> DP: Issue with having *one* TD only on .well-known
12:55:07 <dape> MMC: working on fixing it
12:55:16 <dape> ... look for simple mechanims
12:55:21 <dape> ... thing-links
12:55:37 <dape> ... pointing to other TDs ... index on host
12:55:58 <dape> ... several runtimes on same host is problematic
12:57:22 <dape> CA: Suggest to wait for feature freeze
12:57:42 <dape> ... w.r.t. "local" ... I am surprised .. but god the point from McCool
12:58:01 <dape> ... should re-iterate on API... e.g. from Jan
12:59:52 <dape> CA: should try to have another call with MMC
13:00:28 <kaz> [adjourned]
13:00:34 <kaz> rrsagent, draft minutes
13:00:34 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/07-wot-script-minutes.html kaz