14:58:26 <RRSAgent> RRSAgent has joined #wot-discovery
14:58:26 <RRSAgent> logging to https://www.w3.org/2022/01/24-wot-discovery-irc
14:58:30 <JKRhb> JKRhb has joined #wot-discovery
14:58:54 <kaz> meeting: WoT Discovery
14:59:05 <kaz> present+ Kaz_Ashimura
15:01:44 <cperey> cperey has joined #wot-discovery
15:02:28 <kaz> present+ Christian_Glomb, Christine_Perey
15:02:29 <ktoumura> ktoumura has joined #wot-discovery
15:02:34 <Mizushima> Mizushima has joined #wot-discovery
15:02:35 <kaz> present+ Kunihiko_Toumura
15:02:37 <cperey> Hello
15:03:10 <FarshidT> FarshidT has joined #wot-discovery
15:03:20 <acimmino> acimmino has joined #wot-discovery
15:03:27 <kaz> present+ Andrea_Cimmino
15:03:38 <kaz> present+ Farshid_Tavakolizadeh
15:03:46 <kaz> present+ Tomoaki_Mizushima
15:03:50 <McCool> McCool has joined #wot-discovery
15:05:33 <kaz> rrsagent, make log public
15:05:37 <kaz> rrsagent, draft minutes
15:05:37 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
15:06:07 <kaz> chair: McCool
15:06:29 <kaz> present+ Jan_Romann
15:06:51 <kaz> present+ Michael_McCool
15:06:54 <kaz> rrsagent, draft minutes
15:06:54 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
15:07:29 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#24_January_2022
15:07:32 <FarshidT> topic: minutes review
15:08:25 <FarshidT> https://www.w3.org/2022/01/17-wot-discovery-minutes.html
15:09:31 <FarshidT> no objections to publishing
15:09:38 <FarshidT> topic: PRs
15:11:10 <FarshidT> subtopic: PR264 - Update Security and Privacy Considerations
15:11:14 <FarshidT> https://github.com/w3c/wot-discovery/pull/264 still a draft
15:11:38 <FarshidT> subtopic: PR251 - Refactor event affordance and event type naming
15:12:14 <FarshidT> https://github.com/w3c/wot-discovery/pull/251
15:13:36 <FarshidT> ft: much clearer now, affordance names and event types are consistent
15:14:01 <FarshidT> ft: this PR closes two issues
15:14:31 <FarshidT> mmc: we can go ahead with merging if Ben is happy with the updates
15:14:41 <jkrhb_> jkrhb_ has joined #wot-discovery
15:15:05 <FarshidT> no objections
15:15:14 <FarshidT> PR merged
15:15:14 <cperey> To provide feedback on the draft GeoPose specification, please create issues here https://github.com/opengeospatial/GeoPose/issues
15:15:16 <kaz> rrsagent, draft minutes
15:15:16 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
15:15:28 <FarshidT> subtopic: PR259 - Explicitly disallow SPARQL Update queries
15:15:31 <cperey> just heads up, I have to sign off in 15 min (10:30 AM Eastern)
15:15:37 <FarshidT> https://github.com/w3c/wot-discovery/pull/259
15:15:50 <kaz> i/minutes review/scribenick: FarshidT/
15:16:10 <FarshidT> ac: the assertions are split
15:16:56 <FarshidT> ... three assertions for separation of concern
15:17:32 <FarshidT> ... still discussing if the error code for disallowing UPDATE should be 501 or something else
15:18:00 <jkrhb__> jkrhb__ has joined #wot-discovery
15:18:12 <kaz> rrsagent, draft minutes
15:18:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
15:18:26 <kaz> s/Hello//
15:18:27 <kaz> rrsagent, draft minutes
15:18:27 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
15:18:35 <FarshidT> mmc: 501 is usually about errors related to the server
15:19:13 <FarshidT> ... the assertion about request should clarify that 200 is only for successful requests.
15:21:02 <FarshidT> ... what if an UPDATE request has syntax error. Do we check the syntax first or authorization?
15:24:21 <FarshidT> cg: what about using 400 for both?
15:27:19 <FarshidT> mmc: using 400 is also beneficial because we don't have to worry about the order of syntax checking vs security.
15:27:48 <FarshidT> mmc: let's go with 400 for the disallowed query response.
15:31:05 <FarshidT> ac: applied the requested changes
15:31:09 <FarshidT> PR merged
15:31:27 <FarshidT> subtopic: PR261 - Update discovery-context.jsonld
15:31:34 <FarshidT> https://github.com/w3c/wot-discovery/pull/261
15:32:30 <FarshidT> ac: the existing context is not valid. It fails the JSON-LD playground validations.
15:33:22 <FarshidT> ... this PR doesn't fix the issue, but rather removes them to make the context valid again for the time being
15:34:07 <FarshidT> s/removes them/removes the recently added parts/
15:35:11 <FarshidT> mmc: let's make sure the context reflects the existing spec, without changing the spec
15:35:45 <FarshidT> cg: let's do the partial fix and I'll take it from there
15:36:43 <FarshidT> ac: related issue: https://github.com/w3c/wot-discovery/issues/262
15:37:35 <FarshidT> mmc: the issue remains open for follow-up work on this fix
15:38:50 <FarshidT> PR merged
15:39:48 <FarshidT> subtopic: back to PR264 - Update Security and Privacy Considerations
15:40:30 <FarshidT> mmc: The PR is addressing issues discussed under https://github.com/w3c/wot-discovery/issues/254
15:41:00 <jkrhb__> jkrhb__ has joined #wot-discovery
15:41:38 <FarshidT> ... (going through the comments on the issue)
15:44:38 <kaz> (McCool quickly skims newly created issue 263 https://github.com/w3c/wot-discovery/issues/263 - Profile needs a simple self descriptive mechanism without huge implementation demands)
15:44:54 <FarshidT> ... should we make HTTPS mandatory for self-description over HTTP? It is currently recommended.
15:45:05 <kaz> s/... should/mmc: should/
15:46:56 <FarshidT> mmc: added three new considerations
15:47:09 <FarshidT> ... will update the PR to include them.
15:48:53 <FarshidT> ... recommendations include those for self-discovery on LANs
15:49:39 <FarshidT> ... an external onboarding process is needed to define keys
15:50:56 <FarshidT> ... the access control for self-description should also become a MUST
15:51:36 <FarshidT> ft: this was kept flexible on purpose to cover local/demo/staging environments as well as production environments
15:51:47 <FarshidT> ac: what if HTTPS is provided via a proxy?
15:53:05 <kaz> rrsagent, draft minutes
15:53:05 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
15:53:33 <FarshidT> ft: we can reword to be more explicit that public endpoint MUST use HTTPS, and not necessarily those local and behind a proxy
15:55:52 <FarshidT> mmc: Created issue to address HTTPS for self-description: https://github.com/w3c/wot-discovery/issues/265
15:56:05 <FarshidT> ft: relevant existing issue: https://github.com/w3c/wot-discovery/issues/139
15:57:32 <FarshidT> topic: schedule
15:58:16 <FarshidT> WG extension schedule: https://github.com/w3c/wot/pull/1010
15:58:26 <FarshidT> proposed feature-freeze for discovery
15:59:24 <FarshidT> mmc: we need to update any remaining assertions by next week
15:59:58 <FarshidT> ... another pressing open issue is for self-describing devices that expose more than one TD
16:01:31 <FarshidT> ft: we also discussed the possiblity of using a ThingLink to reference more than one TD from one
16:01:37 <FarshidT> mmc: will capture that
16:01:54 <kaz> [adjourned]
16:02:20 <kaz> rrsagent, draft minutes
16:02:20 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/24-wot-discovery-minutes.html kaz
16:14:19 <jkrhb_> jkrhb_ has joined #wot-discovery
17:12:22 <Zakim> Zakim has left #wot-discovery