12:00:49 <RRSAgent> RRSAgent has joined #wot-script
12:00:49 <RRSAgent> logging to https://www.w3.org/2022/02/14-wot-script-irc
12:01:30 <JKRhb> JKRhb has joined #wot-script
12:02:27 <kaz> meeting: WoT Scripting API
12:02:37 <kaz> present+ Kaz_Ashimura, Cristiano_Aguzzi
12:02:45 <kaz> present+ Jan_Romann
12:03:06 <cris> cris has joined #wot-script
12:03:40 <Mizushima> Mizushima has joined #wot-script
12:05:15 <zkis> zkis has joined #wot-script
12:06:21 <kaz> present+ Michael_McCool
12:06:27 <kaz> present+ Daniel_Peintner
12:07:05 <kaz> present+ Zoltan_Kis, Tomoaki_Mizushima
12:07:16 <cris> topic: minutes
12:07:20 <dape> --> https://www.w3.org/2022/02/07-wot-script-minutes.html
12:07:59 <cris> dp: we talked about use cases section renaming and discovery issues
12:08:07 <McCool> McCool has joined #wot-script
12:08:23 <cris> dape: minor typo
12:09:38 <kaz> q+
12:09:46 <kaz> q-
12:10:08 <cris> dape: minutes looks good
12:10:19 <cris> ... no objections to publish
12:10:24 <cris> topic: quick updates
12:10:32 <cris> subtopic: discovery
12:10:37 <McCool> https://github.com/w3c/wot-discovery/issues/272
12:10:48 <McCool> https://github.com/w3c/wot-discovery/pull/274
12:10:59 <cris> mc: please review the links above
12:11:13 <cris> <mccool sharing the screen>
12:11:35 <kaz> i/topic: minutes/scribenick: cris/
12:11:40 <kaz> rrsagent, make log public
12:11:43 <kaz> rrsagent, draft minutes
12:11:43 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
12:11:44 <cris> mc: the problem is that we didn't describe the process of a consumer
12:12:11 <cris> ... I listed some issues
12:12:41 <cris> ... how  we handle external links (federated TDDs?)
12:12:45 <dape> q+
12:13:05 <cris> ... how we manage external links? how much control the application
12:13:09 <cris> ... should have?
12:13:18 <dape> ack dape
12:13:21 <cris> dape: should the script download the whole directory?
12:13:43 <cris> mc: we have no normative query mechanism
12:13:52 <cris> ... worst case you download everything
12:14:00 <cris> ... no solution so far
12:14:06 <dape> q+
12:14:09 <cris> ... json path non ready yet
12:14:45 <cris> ... I have a PR which describes most of the discovery process
12:15:15 <cris> ... there's new section Discover Consumer
12:15:33 <cris> ... with a set of assertions
12:15:40 <cris> ... trying to be permessive
12:16:30 <cris> ... the arch will have a SHOULD assertion for implementing the discovery process on a consumer
12:17:22 <kaz> chair: Daniel
12:17:22 <kaz> rrsagent, draft minutes
12:17:22 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
12:17:34 <cris> ... what is the minimum implementation?
12:17:36 <zkis> q?
12:18:06 <cris> dape: ok having just ONE required mechanisms
12:18:21 <kaz> s|--> https://www.w3.org/2022/02/07-wot-script-minutes.html|-> https://www.w3.org/2022/02/07-wot-script-minutes.html Feb-7|
12:18:21 <cris> mc: ok, remember that introduction mechanisms are not TDDs
12:18:22 <kaz> rrsagent, draft minutes
12:18:22 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
12:18:38 <dape> ack dape
12:18:47 <cris> q+
12:19:20 <zkis> q+
12:19:49 <kaz> ack c
12:21:43 <cris> cris: I would ok about having the direct mechanism as the basic required introductio mechanism
12:21:53 <cris> mc: I can expand adding use cases
12:22:23 <cris> zoltan: In this scenario the consumer might be also a server?
12:22:51 <cris> mc: these are requirements on the client
12:24:32 <cris> zoltan: priorior knowledge for discovery with direct is the URL
12:24:43 <cris> mc: yeah we can defined two use cases
12:24:48 <cris> ... automatic and manual
12:24:54 <dape> s/priorior/prior
12:26:20 <cris> zoltan: what should we expose to the client script
12:26:42 <cris> mc: direct and directories stays on two different level of discovery
12:27:28 <cris> ... the output of the introduction is a set of URLs
12:27:57 <cris> ... remember that URLs pointing to a TD might be a TDD TD
12:28:07 <cris> ... so you might need to futher explore it
12:28:45 <cris> ... you might need to implement logic
12:28:51 <cris> ... to futher explore
12:29:57 <cris> ... also applicatio may choose to futher explore a TDD or a link
12:30:24 <cris> zoltan: I was thinking that the application might have an higher level
12:30:29 <cris> ... of abstraction
12:30:49 <cris> mc: the problem is that queries are not mandotory
12:31:08 <cris> ... for example jsonpath does not have regex
12:31:48 <cris> zoltan: we need to focus on the use case
12:31:50 <cris> q+
12:32:24 <cris> ack z ?
12:32:32 <cris> ack z
12:32:51 <cris> mc: in the future yeah we can have something more abstract
12:33:20 <dape> q+
12:33:50 <cris> mc: directory is not required
12:34:00 <cris> ... you can use different introduction mechanism
12:34:18 <zkis> q?
12:34:38 <zkis> ack cris
12:36:15 <cris> cris: I think it is fine to support both use cases
12:36:31 <zkis> q?
12:36:34 <zkis> ack dape
12:36:45 <cris> dape: currently the implementation is hiding a lot of this details
12:37:05 <cris> ... I am worried about the fact that this can be overcomplicated
12:37:44 <cris> mc: I agree it is complicated
12:37:58 <zkis> q+
12:38:01 <cris> ... I want to avoid situations where it won't work well
12:38:04 <dape> ack dape
12:38:26 <cris> ... infinite loop
12:38:34 <cris> s/loop/loops/
12:38:40 <cris> ... might be problematic
12:39:50 <cris> zoltan: implementing an LDAP api might be complicated
12:40:26 <cris> mc: we can do horizontal extesion
12:40:37 <cris> ... breath first style
12:41:48 <cris> zoltan: some heuristic can be implemented on custom use cases
12:42:00 <cris> mc: we could have a discovery factory
12:42:00 <dape> s/breath/breadth
12:42:26 <cris> ... where client can choose the type of discovery that suite its needs
12:43:05 <cris> ... thing links are another issue
12:43:08 <cris> +q
12:43:12 <cris> ack z
12:43:53 <cris> ... I hope to have a final version for Wednesday
12:44:37 <zkis> chris: about ThingLinks of composed models, should we follow them automatically
12:44:53 <zkis> ... we have two options: flat and using links
12:44:56 <kaz> i/about/scribenick: zkis/
12:45:19 <kaz> s/chris:/cris:/
12:45:21 <kaz> q?
12:45:24 <kaz> ack c
12:45:59 <cris> mc: originally we had only ThingLinks, but now we have also Read-Only TDDs and mini directories
12:46:55 <cris> ... for an outlet strip should I get a mini-directory or a TD wiht links to sub-parts ?
12:48:23 <kaz> i/originally/scribenick: cris/
12:48:29 <cris> cris: I would say that a word on this in the spec might help implementers
12:48:39 <cris> mc: yeah but it really depends by the use case
12:49:32 <cris> dape: action point for the Scripting API task force is to re-read the spec and give feedback
12:50:43 <cris> topic: PRs
12:51:02 <cris> subtopic: PR 375
12:51:16 <cris> dape: are you ok for Scripting Api Use Case scenarios?
12:51:20 <cris> zoltan: ok
12:51:35 <cris> ... I'll update the PR
12:51:54 <cris> subtopic: introduce local again
12:52:05 <cris> jan: a little bit pre-mature
12:52:06 <dape> -> , https://github.com/w3c/wot-scripting-api/pull/381
12:52:16 <cris> zoltan: it was removed for a good reason
12:52:31 <cris> daniel: it touches what we discussed before
12:53:34 <cris> jan : we can revise later on
12:53:51 <cris> cris: I would wait for a definition of local from the discovery spec
12:53:59 <cris> zoltan: exactly
12:54:10 <cris> dape: sure
12:54:29 <cris> mc: local might be a particular a set of introduction mechanisms
12:54:36 <cris> topic: Issues
12:54:53 <dape> SUBTOPIC: Check alignments with Architecture
12:54:54 <cris> subtopic: Issue 376
12:55:00 <dape> -> https://github.com/w3c/wot-scripting-api/issues/376
12:55:23 <cris> ... we have to check the architecture document, it is still on my TODO list
12:55:58 <dape> SUPTOPIC: Consuming composited Thing Description
12:56:00 <cris> subtopic: 363
12:56:07 <dape> ->  https://github.com/w3c/wot-scripting-api/issues/363
12:56:33 <cris> dape: you can have composed TDs
12:56:43 <cris> ... what are the next steps?
12:56:58 <cris> ... IMHO scripting api should not handle the special use case
12:57:03 <kaz> s/... we have to/dape: we have to/
12:57:13 <cris> ... it is related with Thing Links
12:57:26 <kaz> s|376|376 Issue 376 - Check alignments with Architecture|
12:57:29 <cris> mc: yeah, but Thing Links does not have affordances
12:57:51 <cris> ... we are debating this
12:58:12 <kaz> s/363/363 Issue 363 - Consuming composited Thing Description/
12:58:37 <kaz> rrsagent, draft minutes
12:58:37 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
12:58:39 <cris> zoltan: it looks like a link level optimization
12:58:42 <cris> q+
12:59:28 <kaz> s/subtopic: 363/subtopic: Issue 363/
12:59:45 <kaz> s/SUBTOPIC: Check alignments with Architecture//
12:59:47 <kaz> rrsagent, draft minutes
12:59:47 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
12:59:59 <cris> dape: think link is something different
13:00:08 <kaz> s/SUPTOPIC: Consuming composited Thing Description//
13:00:09 <kaz> rrsagent, draft minutes
13:00:09 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
13:00:21 <cris> ... in my TD I want to mention that an aggregation of TDs
13:00:45 <cris> zoltan: you can't use Thing Links to describe composed Things
13:00:51 <cris> q?
13:01:49 <cris> dape: we are overtime
13:03:40 <cris> cris: just want to say that here the use case is different from Think Links. Composed TDs are a way to describe a set of related TDs
13:03:50 <cris> zoltan: is there any use case description about this?
13:04:18 <cris> adjourned
13:04:19 <kaz> [adjourned]
13:04:22 <kaz> rrsagent, draft minutes
13:04:22 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
13:05:23 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#14_February_2022
13:05:25 <kaz> rrsagent, draft minutes
13:05:25 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/14-wot-script-minutes.html kaz
14:49:12 <Mizushima> Mizushima has left #wot-script
14:50:29 <jkrhb_> jkrhb_ has joined #wot-script
15:02:00 <Zakim> Zakim has left #wot-script
17:04:20 <kaz> kaz has joined #wot-script