15:00:00 RRSAgent has joined #wot-discovery 15:00:00 logging to https://www.w3.org/2021/12/13-wot-discovery-irc 15:00:06 meeting: WoT Discovery 15:00:19 present+ Kaz_Ashimura, Michael_McCool 15:00:22 chair: McCool 15:00:48 present+ Farshid_Tavakolizadeh 15:01:57 present+ Kunihiko_Toumura 15:01:59 ktoumura has joined #wot-discovery 15:03:24 present+ Christian_Glomb 15:05:06 acimmino has joined #wot-discovery 15:05:06 present+ Andrea_Cimmino 15:05:36 present+ Tomoaki_Mizushima 15:06:28 scribenick: kaz 15:07:15 topic: Minutes 15:07:25 -> https://www.w3.org/2021/12/06-wot-discovery-minutes.html Dec-6 15:07:45 mm: OK with the minutes 15:07:53 ... any corrections? objection? 15:07:57 (none; approved) 15:08:03 topic: Logistics 15:08:28 mm: turns out that there will be a conflict on Jan 10... 15:09:11 ... so can't attend myself 15:09:23 ft: can chair the meeting for you 15:09:26 mm: ok 15:09:58 ... (Farshid will chair the Discovery call on Jan 10) 15:10:03 cris_ has joined #wot-discovery 15:10:06 present+ Cristiano_Aguzzi 15:10:24 topic: PRs 15:10:31 -> https://github.com/w3c/wot-discovery/pulls PRs 15:10:44 subtopic: PR 243 15:10:59 -> https://github.com/w3c/wot-discovery/pull/243 PR 243 - Add slight wording changes 15:11:20 mm: Christian's PR 15:11:42 ... (goes through the PR) 15:11:55 ft: two other comments there 15:12:26 ... you can commit it 15:12:47 mm: let's figure it out 15:14:31 ... people agree with the proposed change here? 15:14:54 -> https://github.com/w3c/wot-discovery/pull/243/files#r767711848 Farshid's proposed change 15:16:38 -> https://pr-preview.s3.amazonaws.com/w3c/wot-discovery/243/d33a840...wiresio:0182e2c.html#exploration-directory-api-registration-listing diff - section 6.2.2.1.5 Listing 15:17:09 mm: I'm fine with the proposed change 15:17:32 q+ 15:17:35 q? 15:18:54 kaz: just to make sure, you mean we'd like to remove the second assertion cused by "particularly, it MUST include the same limit argument". Right? 15:18:58 mm: yes 15:19:44 ... (applies the change) 15:20:04 ... and what about the change on "pagenation"? 15:20:12 s/pagenation/pagination/ 15:20:20 ft: around there 15:20:22 mm: ok 15:21:18 (merged) 15:21:22 topic: PR 248 15:21:44 -> https://github.com/w3c/wot-discovery/pull/248 PR 248 - Change XPath response to allow all responses 15:22:00 mm: (goes through the PR) 15:22:27 ... still have a question what the data schema should be 15:23:09 ... would like to read through the spec 15:23:26 ... anyway, need to do is having a sentence 15:23:40 ... could do that later, but can add one now 15:23:46 ft: looked at the TD spec 15:23:55 ... need some change there as well 15:23:59 mm: right 15:24:09 ... the description within TD is also wrong at the moment 15:25:10 -> https://github.com/w3c/wot-discovery/issues/86 Issue 86 - "Thing description" for Directory should be a "Thing Model" 15:26:19 mm: note the data schema for query responses needs some consideration 15:26:42 ... e.g., the return data schema for XPath 3.1 may not include objects 15:26:48 ... since it is converted from XML 15:27:03 ... see https://github.com/w3c/wot-discovery/pull/248 15:27:39 -> https://github.com/w3c/wot-discovery/issues/86#issuecomment-992591898 McCool's comments for Issue 86 15:28:37 mm: (visits section "8.1 Directory API Thing Model" from WoT Discovery ED) 15:28:54 -> https://w3c.github.io/wot-discovery/#directory-thing-model 8.1 Directory API Thing Model 15:29:22 mm: would like to get this done sooner than later 15:29:31 ... Farshid, can you work on that? 15:29:38 ft: yes, I can 15:30:12 topic: Issue 247 15:30:27 -> https://github.com/w3c/wot-discovery/issues/247 Issue 247 - XPath response data model 15:30:35 mm: would like to close this Issue 15:30:50 ft: can be closed by merging PR 248 15:31:16 -> https://github.com/w3c/wot-discovery/pull/248 PR 248 - Change XPath response to allow all responses 15:32:43 mm: (sees the section 6.2.2.4.2 from the diff) 15:32:52 -> https://pr-preview.s3.amazonaws.com/w3c/wot-discovery/248/40267a2...farshidtz:e5aefe2.html#xpath-semantic diff - 6.2.2.4.2 Syntactic search: XPath 15:33:00 mm: any objection to merge this PR? 15:33:02 (none) 15:33:08 https://github.com/w3c/wot-discovery/issues/249 15:33:20 i/249/merged/ 15:33:40 i/249/topic: Issue 249/ 15:33:54 i/https/-> https/ 15:34:10 s/-> https// 15:34:18 s/https/-> https/ 15:34:30 s/249/249 Issue 249 - Multiple Responses from Peer-to-Peer Discovery/ 15:34:44 q+ 15:34:48 ack k 15:34:58 mm: one possibility is listing APIs 15:35:47 ft: data type is not TD any more 15:35:55 ... array is not a Thing 15:36:02 ack c 15:36:26 ca: wondering if we could refer to the core link format 15:36:35 mm: (adds comments) 15:36:46 ...could also return one TD that links to other TDs 15:37:03 ... if we return an array in DNS service type, is it a Thing or a Directory? 15:37:20 ... maybe we should use CoRE-RD format for .well-known? 15:37:36 ... we have to change the definition 15:37:48 ft: what would be the content type? 15:38:07 mm: we already have an IANA content type for TDs 15:38:17 ... but not for "collections of TDs" 15:38:55 ... so what would the content type of the .well-known end point be? 15:39:37 ft: what would happen for a gateway? 15:39:51 ... thinking out of box 15:42:01 mm: could also return one TD that links to other TDs This gives a TD similar functionality of CoRE-RD but without bringing in another spec 15:42:13 FarshidT has joined #wot-discovery 15:42:17 ThingLink: https://w3c.github.io/wot-discovery/#exploration-mech 15:42:45 ft: Exploration Mechanisms 15:43:09 mm: ThingLink type 15:44:33 ca: in node-wot, servient exposes itself using a TD 15:44:47 mm: we have 2 choices 15:45:18 ... but can a Thing expose a second TD? 15:45:47 ... multiple Things in the same script? 15:46:01 ca: yes, that's possible 15:46:18 s/a sec/the sec/ 15:46:55 mm: this would lead to different cases for one and multiple TDs 15:47:07 ... do we switch between them? 15:47:22 ... my preference is always using Thing Links 15:48:23 ... the disadvantage is that we need to fetch two TDs 15:48:58 ft: if you refer to the spec, there are three use cases 15:49:26 ... and maybe we might need the fourth one 15:50:35 -> https://w3c.github.io/wot-discovery/#example-td-link-type example 2 15:51:41 mm: if we return the TD itself for "singleton" Things then we avoid this problem for the simple case (=one Thing for a given IP) 15:52:25 (some more discussion on possible solutions) 15:52:37 mm: pushing down node for tree 15:52:55 ca: can try to implement that 15:53:37 -> https://github.com/w3c/wot-discovery/issues/249#issuecomment-992615299 McCool's comments on several possible options 15:54:26 -> https://github.com/w3c/wot-discovery/issues/249#issuecomment-992615859 leaning towards [[Using a ThinkLink TD, but only when there are multiple Things at a given IP address.]] 15:55:02 mm: We could ALLOW people to use a ThingLink even if they have only one TD. 15:55:18 topic: Other Issues 15:55:26 subtopic: Issue 24 15:55:30 s/24/245 15:55:48 -> https://github.com/w3c/wot-discovery/issues/245 Issue 245 - Disallow SPARQL UPDATE operations 15:56:01 mm: UPDATE might be dangerous 15:56:44 ac: SPARQL 1.1 already implements UPDATE 15:57:03 mm: SPARQL system has differet endpoints for UPDATE 15:57:20 ... so we could simply not support the UPDATE endpoint 15:57:31 ... Andrea, can you check the status? 15:57:46 ac: will do 15:58:09 subtopic: Issue 246 15:58:23 -> https://github.com/w3c/wot-discovery/issues/246 Issue 246 - TDD Handle extra parameters when publishing/extensibility of the creation endpoint 15:58:34 mm: revisit next time 15:59:09 subtopic: Issue 216 15:59:22 -> https://github.com/w3c/wot-discovery/issues/216 Issue 216 - Define role of "Discoverer/Registerer" 16:00:54 mm: would propose changing definition slightly to say "generates, fetches, or instantiates" 16:01:02 ... let's continue the discussion next time 16:01:06 [adjourned] 16:01:12 rrsagent, make log public 16:01:16 rrsagent, draft minutes 16:01:16 I have made the request to generate https://www.w3.org/2021/12/13-wot-discovery-minutes.html kaz 17:36:48 Zakim has left #wot-discovery