13:12:34 <RRSAgent> RRSAgent has joined #wot-pf
13:12:34 <RRSAgent> logging to https://www.w3.org/2022/07/06-wot-pf-irc
13:12:38 <kaz> topic: minutes
13:12:43 <kaz> mc: not too much
13:13:15 <cris> ... still some issues with some assertions
13:13:20 <cris> ... minutes looks good
13:13:22 <kaz> i|not|-> https://www.w3.org/2022/06/29-wot-pf-minutes.html June-29|
13:13:24 <cris> ... any objections?
13:13:28 <cris> ... ok minutes accepted
13:13:29 <kaz> i/still/scribenick: cris/
13:13:33 <cris> topic: PRs
13:13:35 <kaz> i/not too/scribenick: kaz/
13:13:36 <Mizushima> Mizushima has joined #wot-pf
13:13:42 <kaz> meeting: WoT Plugfest/Testing
13:13:47 <kaz> chair: McCool
13:13:48 <cris> subtopic: PR 349
13:14:08 <cris> mc: a bunch of TM models from sdf-wot-converter
13:14:13 <kaz> present+ Kaz_Ashimura, Michael_McCool, Fady_Salama, Cristiano_Aguzi, Ege_Korkan, Kunihiko_Toumura, Tomoaki_Mizushima
13:14:15 <cris> ... but there is an issue
13:14:20 <cris> ege: is a validation issue
13:14:37 <cris> ... regarding format keyword
13:15:04 <cris> fady: I'm not sure where is the problem, but if it is written in the TD/TM schema
13:15:06 <kaz> i|bunch of|-> https://github.com/w3c/wot-testing/pull/349 PR 349 - Add TMs and manual.csv for sdf-wot-converter|
13:15:14 <cris> ... there is the possibility that it might be wrong there
13:15:17 <kaz> rrsagent, make log public
13:15:21 <kaz> rrsagent, draft minutes
13:15:21 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/06-wot-pf-minutes.html kaz
13:16:13 <cris> mc: json pointer is meant to be used as fragment identifiers
13:16:36 <cris> fady: practically is ajv problem
13:16:51 <cris> ... they are using two different keywords for describing JSONPointers
13:16:59 <cris> ... one for the fragment part
13:17:34 <kaz> i|json pointer|-> https://datatracker.ietf.org/doc/html/rfc6901 RFC 6901 - JSON Pointer|
13:17:40 <kaz> rrsagent, draft minutes
13:17:40 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/06-wot-pf-minutes.html kaz
13:17:47 <cris> s/fragment part/full path/
13:17:55 <cris> ... and the other for relative part
13:18:08 <McCool_> https://ajv.js.org/packages/ajv-formats.html
13:18:22 <kaz> s/https/-> https/
13:18:28 <cris> ege: I checked two different JSONSchema validator implementations and one accept it and the other not
13:18:43 <cris> ... there might be a inconsistency problem
13:18:59 <cris> mc: the RFC clearly states that a JSON Pointer is not an URL
13:19:10 <kaz> s/html/html ajv-formats/
13:19:33 <cris> ... putting this aside I think we should merge the PR and fix the problem about JSONPointer somewhere else
13:19:36 <cris> kaz: I agree
13:19:42 <kaz> q?
13:20:59 <cris> ege: basically # is not allowed
13:21:22 <cris> ... the submission is wrong (it contains #)
13:21:40 <cris> fady: beware that the TD spec uses # everywhere.
13:21:55 <cris> mc: checking examples in a minute
13:22:16 <cris> ... actions: review the TD spec,
13:23:15 <kaz> q+
13:23:54 <cris> kaz: we should discuss about these details in the TD call
13:24:01 <cris> mc: I agree
13:24:02 <kaz> s/about //
13:24:07 <kaz> ack k
13:24:41 <cris> mc: bottom line, we can't merge this PR because it contains pointers with #
13:25:50 <cris> subtopic: PR 356
13:25:58 <cris> fady: tool problem
13:26:01 <cris> ... TDs are correct
13:26:14 <cris> ... but the tool is behaving wrongly
13:26:29 <cris> ... PR inflight
13:26:53 <kaz> i|tool|-> https://github.com/w3c/wot-testing/pull/356 PR 356 - Add ComboSecurityScheme with descriptions|
13:26:55 <cris> ege: the official JSON Schema does not included the URI
13:26:59 <cris> ... but still the tool fails
13:27:08 <cris> fady: we have to discuss about it
13:27:18 <cris> mc: ok about the PR we can proceed
13:27:26 <cris> ... since is not a problem with the TDs
13:27:34 <cris> fady: I agree
13:28:38 <McCool_> https://github.com/w3c/wot-thing-description/issues/1557
13:28:42 <kaz> s/https/-> https/
13:28:49 <McCool_> merged, overriding validation check failure
13:28:52 <kaz> s/1557/1557 related TD issue 1557/
13:29:11 <cris> topic: logistics
13:29:32 <cris> mc: July testfest
13:29:36 <kaz> s/logistics/testfest logistics/
13:29:37 <cris> ... dates are set
13:30:11 <cris> ege: we know a bunch of people from University of Turin
13:30:11 <kaz> i|July|-> https://github.com/w3c/wot-testing/tree/main/events/2022.07.Online 2022.07.Online|
13:30:17 <cris> ... can we ask them to join
13:30:21 <kaz> q+
13:30:27 <cris> s/join/join?/
13:30:41 <cris> mc: it sounds that they are better fit for August (plugFest)
13:30:56 <cris> q+
13:31:13 <cris> ege: they do not have a new application
13:31:24 <cris> mc: if that's so we can invite them as guests
13:31:55 <cris> kaz: if you want invite implementers to verify implementability of some feature we should do that in Septmber
13:32:04 <cris> ... if the implementation is old
13:32:21 <cris> ... we can use it for implementation report
13:32:23 <cris> q+
13:32:26 <kaz> ack k
13:33:30 <cris> cris: they are also developing experimental features
13:33:36 <cris> ... we should clarify the scope
13:33:52 <cris> ... but I ok to invite them
13:34:01 <cris> s/I ok/I am ok/
13:34:12 <cris> mc: I've updated the readme
13:34:15 <kaz> ack k
13:34:17 <kaz> ack c
13:35:59 <kaz> s/If you want invite implementers to verify implementability of some feature we should do that in Septmber/if they can provide implementation report for the July testfest, we can invite them. On the other hand, if they want to show their implementations to us or see connectivity with the other implementations, we should rather invite them to a Plugfest, e.g., the one during TPAC in September./
13:36:09 <cris> ege: I won't be able to participate in the August PF
13:36:37 <kaz> s/use it for/use it as part of our/
13:36:46 <cris> mc: about logistics I'd like to propose to use the same time
13:37:03 <cris> ege: links are dead in the readme
13:37:54 <cris> cris: I can't join too
13:39:02 <cris> mc: let's do it anyway we don't have any other good slots for it
13:39:30 <cris> topic: implementation reports
13:39:54 <cris> mc: I have still to re-run the tests
13:40:20 <cris> ege: there is also some problem with node-wot
13:40:29 <cris> ... I opened the issue
13:40:34 <cris> ... I will investigate
13:40:52 <cris> ... going back to invite
13:40:56 <cris> ... can I do it
13:41:00 <cris> ... ?
13:41:16 <cris> mc: regarding PF I am ok for you to invite people
13:41:34 <cris> ... just be sure that they know the IP policy
13:41:44 <cris> ege: testfest too?
13:42:00 <cris> mc: both, but it is technically an IG activity.
13:42:03 <kaz> q+
13:42:47 <cris> kaz: I agree about open invitations
13:42:56 <cris> ... but I would be more careful
13:43:14 <cris> mc: yeah we may define a policy
13:43:43 <cris> ... however the event is under IG so people must obey to IG policy
13:43:56 <cris> ... I ok with giving the power to editors
13:44:02 <cris> ... to extend invitations
13:44:24 <cris> kaz: not clearly defined
13:44:41 <cris> ... we should specify "why"
13:44:50 <cris> mc: I agree a kind of rationale
13:45:19 <kaz> s/I agree about open invitations/I basically agree with your position, Michael./
13:45:59 <kaz> s/but I would be more careful/but would suggest we should be a bit more careful about who to invite to which events./
13:46:00 <cris> mc: bug report might fell under CG activity
13:46:11 <cris> ege: I agree
13:46:35 <cris> kaz: if there is an invite we should get something in exchange
13:46:55 <kaz> s/not clearly/how to deal with CG is not clearly/
13:48:03 <kaz> s/we should specify "why"/we should consider "why we need to invite who to which events or meetings"./
13:48:11 <cris> mc: let's discuss this in the main call
13:48:31 <cris> ... but it is a little late
13:48:44 <cris> ... can I ask directly a description
13:48:48 <cris> ... and a motivation
13:48:57 <cris> ... so that we can decide by email
13:49:20 <kaz> s/if there is an invite we should get something in exchange/if we invite somebody to our meetings or events, we should clarify why we need to invite them and what would be their potential contributions./
13:49:35 <kaz> rrsagent, draft minutes
13:49:35 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/06-wot-pf-minutes.html kaz
13:51:57 <kaz> scribenick: kaz
13:52:24 <kaz> kaz: yes, we need to see who to be invited to which events or meetings for what purpose./
13:52:30 <kaz> s|./|.|
13:52:33 <kaz> [adjourned]
13:52:39 <kaz> rrsagent, draft minutes
13:52:39 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/06-wot-pf-minutes.html kaz
13:59:47 <Mizushima> Mizushima has left #wot-pf
16:21:17 <Zakim> Zakim has left #wot-pf