13:01:28 RRSAgent has joined #wot-discovery 13:01:33 logging to https://www.w3.org/2024/02/26-wot-discovery-irc 13:01:34 meeting: WoT Discovery 13:01:41 chair: McCool 13:02:00 present+ Kaz_Ashimura, Michael_McCool, Jan_Romann 13:02:06 scribenick: JKRhb 13:03:08 ktoumura has joined #wot-discovery 13:03:41 present+ Kunihiko_Toumura 13:05:28 Mizushima has joined #wot-discovery 13:06:01 topic: Minutes Review 13:06:14 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#26_February_2024 13:06:27 mm: Been a while, probably good to scan through 13:06:31 q+ 13:06:34 ... meeting schedule should get organized 13:06:41 ... PRs were merged 13:06:55 kaz: The link is actually wrong in the wiki 13:07:10 mm: Right, need to change that. Thank you for catching that 13:07:14 i|Been|-> https://www.w3.org/2024/02/19-wot-discovery-minutes.html Feb-19| 13:07:15 ... (changes the link in the wiki) 13:07:37 ... (goes over the correct minutes now) 13:07:52 ... had a long discussion about versions 13:08:35 present+ Tomoaki_Mizushima 13:08:47 ... one PR is still open, one got merged 13:08:57 ... if we still have time, we should look at the calendar 13:09:05 ... any objections to approving the minutes? 13:09:09 None, minutes are approved 13:09:16 topic: Calendar 13:09:40 mm: So, we have some upcoming holidays 13:10:06 ... I wonder what we should do about holidays around easter 13:10:29 ... Easter Monday is a holiday in Canada, in Germany as well I suppose 13:10:34 q+ 13:10:37 jr: Exactly 13:10:46 mm: So we should cancel April 1 13:11:17 ack k 13:11:19 mm: Due to golden week, we should also cancel April 29 13:11:31 ... (updates the Wiki) 13:11:54 tm: On April 8 and 9, there are AC meetings 13:11:59 q+ 13:12:10 mm: Is a direct conflict? 13:12:28 ack m 13:12:29 ack k 13:12:40 kaz: Will be held in Hiroshima and there is going to be a after-party 13:12:50 mm: So April 8 is going to be cancelled as well 13:13:12 ... May 6 is also going to be a Monday, so it also going to be cancelled 13:13:38 ... that's half our meetings cancelled for upcoming weeks, but can't do anything about it. Same is probably true for security 13:13:43 topic: Resources 13:15:08 subtopic: PR 537 13:15:26 mm: So last time there were some problems which you tried to resolve 13:15:43 ... and I guess we decided to change the version number to say a1 13:16:06 ... but I think we agreed to use 1.0 to not get things out of order 13:16:24 ... there was also the idea of creating a draft directory 13:16:44 ... but then again, the discovery repo can be seen as a draft repo 13:16:51 ... any objections to yet? 13:16:57 jr: No, sounds good to me 13:17:30 mm: I see you also updated the meta data 13:18:48 rrsagent, make log public 13:18:51 ... but the first version is now saying 0.1.2 13:19:02 rrsagent, draft minutes 13:19:03 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:19:13 ... in the changelog 13:19:52 jr: That comes from a previous version 13:20:03 s/537/537 and 536/ 13:20:24 i|So last|-> https://github.com/w3c/wot-discovery/pull/537 PR 537 - Expand rdfs:comments in Discovery ontology| 13:20:31 mm: As we have a published version with 0.1.2 we could also consider using 0.1.3 for the new version 13:20:56 i|So last|-> https://github.com/w3c/wot-discovery/pull/536 PR 536 - Render changelog in discovery ontology from RDF| 13:21:00 rrsagent, draft minutes 13:21:01 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:21:08 jr: Or maybe use 0.2.0, as we've added some new "features" with the updated descriptions 13:21:18 mm: Yeah, we made some larger changes 13:22:45 suggest 0.2.0-a1 13:23:17 jr: Updated and pushed now 13:24:30 mm: Looks good, I will merge it now 13:24:35 ... any objections? 13:24:37 None, merged 13:24:52 mm: Please synchronize with the TD guys to get a consistent output 13:26:07 topic: Discovery PRs 13:26:21 subtopic: PR 538 13:26:53 jr: This reflects a discussion we had in node-wot regarding the discovery API 13:26:58 .. using TDDs 13:27:35 ... so Cristiano opened this PR 13:28:30 mm: This mostly updates the JSON Schema and the TM of the TDD 13:28:36 ... so I am fine with merging this 13:28:52 ... did you have any chance to test this yet? 13:29:22 ... we need to discuss testing in general, creating issues, regarding pagination and no pagination 13:29:26 .. for example 13:29:31 i|This ref|-> https://github.com/w3c/wot-discovery/pull/538 PR 538 - Introduce DataSchema for property 'things'| 13:29:59 jr: I think there have not been any tests yet, but I don't know if Cristiano maybe updated his implementation already (probably not) 13:30:14 q+ 13:30:47 mm: I'll generate an issue for the testing of the things property, if we already have a test then we can mark it as completed immediately 13:31:17 ack k 13:31:19 kaz: Merging this PR itself is okay in general, in general I am wondering about the relationship between the specification test and the schema 13:31:25 ... is the specification clear enough? 13:31:41 mm: The TM of the TDD is in the spec 13:31:55 ... not sure if it is normative or not at the moment 13:32:10 ... it is also a TD and not a JSON Schema, right? 13:32:34 ... it's in the API specification, so it is actually normative then 13:32:45 ... but it is not the only source 13:32:54 s/okay in general, in general/fine if everybody is ok with this change, but/ 13:33:00 ... so we need to make source that it is consistent with the specification 13:33:23 s/is the specification/is the specification text/ 13:33:25 ... and we have a listing endpoint, which should actually be "things" 13:33:59 ... so Cristiano is actually adding a schema definition that is describing the return values mentioned in the specification 13:34:20 q? 13:34:39 kaz: There two levels of questions here, one also related to the question what should be tested (schema vs specification) 13:34:58 mm: Generally, we should organize testing better 13:35:18 https://github.com/w3c/wot-discovery/issues/543 13:35:24 ... for the moment, we can merge this PR 13:35:30 ... any objections? 13:35:37 None, merged 13:35:54 subtopic: PR 542 13:36:27 mm: So this PR just replaces the two informative references of the JSONPath I-D with the RFC 13:36:42 s/There two levels of questions here, one also related to the question what should be tested (schema vs specification)/What to be tested is the text within the specification, so I asked if the spec text is clear enough. On the other hand, Schema can be used to make the test easier. So there are two levels of questions here./ 13:36:46 ... we need to check the RFC and investigate its features 13:36:49 rrsagent, draft minutes 13:36:50 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:36:57 ... I will create an issue for that 13:37:05 ... any objections to merging? 13:37:09 None, merged 13:37:21 s|https://github.com/w3c/wot-discovery/issues/543|(McCool creates a new issue: https://github.com/w3c/wot-discovery/issues/543)| 13:37:48 jr: There are already a couple of issues related to JSONPath 13:37:54 i|So this PR|-> https://github.com/w3c/wot-discovery/pull/542 PR 542 - Replace custom JSONPath reference with RFC 9353| 13:38:10 mm: Yeah, so we can simply add a comment to an existing one 13:38:24 ... (adds a coment to issue 387) 13:38:34 s/coment/comment/ 13:38:38 -> https://github.com/w3c/wot-discovery/issues/387 Issue 387 - JSONPath queries filtering on semantic annotations| 13:38:43 rrsagent, draft minutes 13:38:44 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:39:04 https://github.com/w3c/wot-discovery/issues/387 13:39:49 mm: The other issue that has been brought up is that JSONPath does not deal with JSON-LD very well 13:40:10 ... Cristiano also mentions this in a comment in the issue 13:40:24 ... this is especially related to expanding 13:40:54 ... but we will deal with that next time. For now we are done with PRs 13:41:07 topic: DID Registration 13:41:20 mm: We now have a referencable URI 13:41:35 ... I updated the PR against the did-spec-registries repository 13:41:54 ... has been reviewed, should now be ready to be merged, but is still pending 13:42:11 ... we need to get back to it next week, by then it will hopefully be merged 13:42:29 ... so far, I have added some more explanatory test 13:42:33 s/test/text/ 13:43:02 ... explaining the two terms and references the Discovery specification 13:43:31 ... can you also check again if the PR references the correct terms/URIs from the discovery ontology? 13:43:35 jr: Sure, will do 13:44:02 i|We now|-> https://github.com/w3c/did-spec-registries/pull/486 did-spec-registries PR 486 - Add WotThing and WotDirectory service types 13:44:05 topic: Planning 13:44:09 rrsagent, draft minutes 13:44:10 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:44:47 subtopic: Main Calendar 13:44:47 mm: Let's look at the schedule 13:44:47 ... we have some dates here which are the worst case scenarios 13:44:49 ... there is a bit of padding here 13:45:08 ... we should probably aim for a earlier due date 13:45:16 ... FPWD is in about a year 13:45:28 ... we are mostly doing incremental changes 13:45:46 ... we probably do not have enough time for a complete overhaul 13:46:00 ... so probably it will rather be Discovery 1.1 instead of 2.0 13:46:03 -> https://github.com/w3c/wot/blob/main/planning/schedule.md schedule.md 13:46:20 ... and hopefully we will not have breaking changes 13:46:43 q+ 13:46:54 ... a good target will probably be end of this year, so we should have a first version of a finished document mid December 13:47:10 ... (starts updating the schedule) 13:47:32 kaz: Any date is fine if it's feasible 13:47:36 ... as an initial target 13:47:42 ... and we need to think how to get there 13:48:03 ... and especially for the TD 2.0, we need to think how to get feedback from developers and the industry 13:48:14 ... that is also true for discovery, right? 13:48:35 mm: Ideally we should have our requirements by then 13:48:54 kaz: @@@ 13:49:23 mm: Let's look at the charter draft 13:49:46 s/@@@/my point is that the proposed date (end of 2024) is fine for FPWD as the initial target, and then we need to clarify the sub steps to get there as the next step :)/ 13:49:49 rrsagent, draft minutes 13:49:50 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:50:12 ... (opens the rendered document) 13:50:45 ... looking at the timeline, we should have the use cases and requirements by Q3 13:50:52 ... so September 13:51:14 ... let me put use case and requirements and testing somewhere in our schedule 13:51:18 ... (updates schedule.md) 13:51:53 ... so I guess this would be a Note update (regarding use cases and requirments) 13:52:32 ... so by September we probably want to have an updated Use Cases and Requirements document 13:52:59 ... and then after the FPWD, we want to do testing in June 2025 13:54:11 ... all of these deadlines are worst-case scenarios and include some padding 13:54:26 ... I will not merge this but create a PR which we can discuss in the main call 13:55:21 ... (commits the changes and opens a PR) 13:55:40 https://github.com/w3c/wot/pull/1184 13:55:54 mm: we are out of time for today but we made some progress 13:56:12 ... for the next time, I think it would be nice to align our work items with the requirements 13:56:31 ... I think we should pick a work item to work on in the meantime 13:56:56 ... next time, we should look at the issue tracker and align with the things happening in the use cases task force 13:58:21 ... we should probably go through the many issues, clean some up and change the "defer" label to "current" 13:58:26 rrsagent, draft minutes 13:58:27 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 13:58:47 topic: Task Force Lead 13:59:31 mm: Would you consider becoming TF lead, Jan? 13:59:46 jr: I would consider it, but I would need some support 14:00:05 mm: We need more people joining the calls 14:00:13 ... let's discuss this topic next week 14:00:18 [adjourned] 14:00:33 rrsagent, draft minutes 14:00:34 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 14:01:42 chair: McCool 14:01:43 rrsagent, draft minutes 14:01:44 I have made the request to generate https://www.w3.org/2024/02/26-wot-discovery-minutes.html kaz 14:31:32 Mizushima has left #wot-discovery 16:02:48 Zakim has left #wot-discovery