13:55:37 <RRSAgent> RRSAgent has joined #lws
13:55:42 <RRSAgent> logging to https://www.w3.org/2026/06/29-lws-irc
13:55:42 <Zakim> RRSAgent, make logs Public
13:55:43 <acoburn> acoburn has joined #lws
13:55:43 <Zakim> please title this meeting ("meeting: ..."), laurens
13:55:46 <laurens> meeting: LWS WG Meeting - June 29th, 2026
13:55:47 <agendabot> agenda+ Review Project Spreadsheet
13:56:15 <laurens> chair: laurens
13:57:56 <termontwouter> termontwouter has joined #lws
13:58:23 <elf-pavlik> elf-pavlik has joined #lws
13:59:18 <acoburn> present+
13:59:31 <acoburn> rrsagent, make minutes
13:59:32 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/29-lws-minutes.html acoburn
13:59:52 <eBremer> eBremer has joined #lws
14:00:04 <eBremer> present+
14:00:16 <acoburn> previous meeting: https://www.w3.org/2026/06/22-lws-minutes.html
14:00:24 <jeremycaine> jeremycaine has joined #lws
14:00:33 <acoburn> next meeting: https://www.w3.org/2026/07/06-lws-minutes.html
14:00:44 <elf-pavlik> present+
14:01:23 <gibsonf1> gibsonf1 has joined #lws
14:01:32 <gibsonf1> present+
14:01:51 <pchampin> present+
14:01:57 <acoburn> scribenick: acoburn
14:03:13 <jeremycaine> present+
14:03:16 <acoburn> zakim, open agendum 1
14:03:16 <Zakim> agendum 1 -- Introductions & Announcements -- taken up [from agendabot]
14:03:39 <acoburn> laurens: we will discuss several open PRs
14:03:48 <acoburn> ... update on the notification PR
14:03:58 <acoburn> ... and the storage description resource
14:04:10 <TallTed> TallTed has joined #lws
14:04:17 <acoburn> zakim, open agendum 2
14:04:17 <Zakim> agendum 2 -- Auxiliary Resources (PR -> https://github.com/w3c/lws-protocol/pull/165 https://github.com/w3c/lws-protocol/pull/165 ) -- taken up [from agendabot]
14:04:40 <termontwouter> present+
14:04:57 <rbreitman> rbreitman has joined #lws
14:05:06 <laurens> https://github.com/w3c/lws-protocol/pull/180
14:05:07 <gb> https://github.com/w3c/lws-protocol/pull/180 -> Pull Request 180 Link set profile (by termontwouter)
14:05:11 <acoburn> laurens: a new PR has been opened #180
14:05:12 <gb> https://github.com/w3c/lws-protocol/pull/180 -> Pull Request 180 Link set profile (by termontwouter)
14:05:18 <rbreitman> #present
14:05:32 <acoburn> termontwouter: we merged PA's PR from last week
14:05:53 <rbreitman> present+
14:05:55 <acoburn> ... this is a minor change, introducing a profile parameter
14:06:13 <acoburn> ... this distinguishes a linkset resource from a dataset resource
14:06:37 <elf-pavlik> q+ to ask what were the CORS issues with profile param
14:06:43 <acoburn> laurens: this is a draft PR, so folks are invited to add comments there
14:06:48 <acoburn> ack next
14:06:49 <Zakim> elf-pavlik, you wanted to ask what were the CORS issues with profile param
14:07:02 <acoburn> elf-pavlik: are the CORS issues still relevant in this case?
14:07:12 <Luke> Luke has joined #lws
14:07:18 <dmitriz> dmitriz has joined #lws
14:07:23 <Luke> present+
14:07:26 <acoburn> termontwouter: we use a non-URI
14:07:26 <TallTed> q+
14:07:32 <laurens> ack TallTed
14:07:36 <acoburn> acoburn: the string selected will not run afoul of CORS
14:08:05 <acoburn> TallTed: the new PR was just opened, what are we reviewing right now?
14:08:53 <acoburn> laurens: the PR from pchampin made #165 obsolete
14:08:53 <gb> https://github.com/w3c/lws-protocol/pull/165 -> CLOSED Pull Request 165 Define aux & meta in terms of representations (by termontwouter)
14:09:27 <termontwouter> q+
14:09:50 <acoburn> laurens: the goal is to introduce this pr this week and discuss further next week
14:09:53 <laurens> ack termontwouter
14:10:21 <acoburn> termontwouter: I realize this was last-minute, but left in draft mode before moving to a vote
14:10:41 <acoburn> laurens: next week we can proceed to a vote if there are no significat changes
14:10:51 <acoburn> s/significat/significant/
14:10:58 <acoburn> zakim, open agendum 3
14:10:58 <Zakim> agendum 3 -- Replace GET/POST with new HTTP QUERY RFC10008 (PR -> https://github.com/w3c/lws-protocol/pull/179 https://github.com/w3c/lws-protocol/pull/179 ) -- taken up [from
14:11:01 <Zakim> ... agendabot]
14:11:24 <acoburn> laurens: this PR was opened by eBremer to replace GET/POST with the QUERY verb
14:11:52 <acoburn> eBremer: the QUERY RFC was advanced as an IETF proposed standard only a few days ago
14:12:14 <acoburn> ... this PR adjusts the type index from GET/POST to only the QUERY operation
14:12:52 <acoburn> ... this RFC (QUERY: RFC 10008) seems to be gaining a lot of support very quickly
14:13:17 <acoburn> laurens: one question is whether we want to give implementers the option of GET/POST *and* QUERY
14:13:26 <pchampin> +1 to allow a fallback to POST
14:13:26 <TallTed> q+
14:13:27 <jeswr> jeswr has joined #lws
14:13:32 <laurens> ack TallTed
14:13:33 <acoburn> ... would like to hear from the rest of the working group on this
14:13:37 <jeswr> present+
14:13:49 <acoburn> TallTed: clients can ask servers what methods they support
14:14:09 <acoburn> ... I don't expect QUERY will have full support in the near future, but we should be able to talk about
14:14:18 <acoburn> ... I don't think we should *require* QUERY at this point
14:14:22 <dmitriz> dmitriz has joined #lws
14:14:41 <acoburn> laurens: at present, the type index is optional, so we would not be imposing QUERY on anyone
14:14:56 <acoburn> ... please continue discussion on the GH pull request
14:14:57 <laurens> q?
14:15:07 <acoburn> zakim, open agendum 4
14:15:07 <Zakim> agendum 4 -- Notifications (PR -> https://github.com/w3c/lws-protocol/pull/162 https://github.com/w3c/lws-protocol/pull/162 ) and integration into the core specification -- taken
14:15:10 <Zakim> ... up [from agendabot]
14:15:38 <acoburn> laurens: I hope to open a PR this week to integrate notifications into the core protocol
14:15:59 <acoburn> ... in addition, we still have PR #162 open (additional notification channels)
14:16:00 <gb> https://github.com/w3c/lws-protocol/pull/162 -> Pull Request 162 feat(notifications): Add WebSocket and Server-Sent Event channels (by laurensdeb)
14:16:16 <acoburn> ... at present, only webhooks are defined
14:16:24 <laurens> q?
14:16:26 <acoburn> ... over the next few days, a PR will follow
14:16:48 <acoburn> zakim, open agendum 5
14:16:48 <Zakim> agendum 5 -- Storage Description resource as a CID (PR -> https://github.com/w3c/lws-protocol/pull/183 https://github.com/w3c/lws-protocol/pull/183 ) -- taken up [from agendabot]
14:17:05 <laurens> scribe+
14:17:19 <laurens> acoburn: This is the result of conversation at the F2F meeting
14:17:30 <ericP> ericP has joined #lws
14:17:31 <laurens> ... The storage description resource looks a lot like a CID.
14:17:38 <laurens> ... So the question is, should this be a CID?
14:17:57 <laurens> ... My intention here is to just introduce this.
14:18:13 <laurens> ... The PR contains three notable changes.
14:18:39 <laurens> ... Firstly, the media type application/lws+cid indicates this is a specialization of a CID.
14:18:57 <laurens> ... Secondly, there are now two required contexts.
14:19:11 <laurens> ... The core CID context, and a specialized LWS context.
14:19:23 <laurens> ... This avoids us copying things in the LWS context.
14:19:33 <laurens> ... The JSON itself however looks exactly the same.
14:19:48 <ericP> q+ to ask about tools that can work with CIDs
14:19:52 <laurens> ... We can continue the discussion now or in the PR.
14:20:01 <laurens> ack ericP
14:20:01 <Zakim> ericP, you wanted to ask about tools that can work with CIDs
14:20:25 <laurens> ericP: Are there tooling and libraries that work generically with CID that we can re-use?
14:20:34 <laurens> acoburn: I don't know in particular.
14:20:44 <laurens> ... I would imagine a lot of libraries rely on JSON parsing.
14:20:50 <laurens> ... As a CID is a JSON document.
14:20:59 <laurens> ... pchampin might know more.
14:21:06 <pchampin> I'm affraid I'm not
14:21:13 <pchampin> but will look into it
14:21:19 <laurens> scribe-
14:21:27 <pchampin> s/affraid/afraid
14:21:41 <acoburn> zakim, open agendum 6
14:21:41 <Zakim> agendum 6 -- Review Project Spreadsheet -- taken up [from agendabot]
14:21:50 <acoburn> rrsagent, make minutes
14:21:52 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/29-lws-minutes.html acoburn
14:22:16 <acoburn> laurens: (sharing screen)
14:22:37 <acoburn> ... related to test suite, do we have updates from ericP?
14:23:23 <acoburn> ericP: no significant updates yet, haven't run the suite against a live environment
14:23:58 <elf-pavlik> elf-pavlik has joined #lws
14:24:08 <acoburn> laurens: we will have an update from Samu on the third Monday (July 20)
14:24:34 <acoburn> ... what is the status of the system diagrams jeremycaine?
14:24:58 <acoburn> jeremycaine: there are some debates on terminology, e.g. virtual resources #150
14:24:59 <gb> https://github.com/w3c/lws-protocol/issues/150 -> Issue 150 Define Virtual Resource (by renyuneyun)
14:25:26 <acoburn> laurens: we discussed virtual resources a few weeks ago
14:25:43 <acoburn> q+ to mention virtual resources
14:25:59 <acoburn> laurens: we could put this item on the agenda for next week
14:25:59 <elf-pavlik> q+ to invite jeremycaine coordinating on diagrams
14:26:41 <acoburn> ... we need to make decision on what to do with virtual resources
14:27:07 <acoburn> ... consensus seemed to be that we shouldn't preclude virtual resources but won't include them in spec
14:27:15 <laurens> q?
14:27:19 <laurens> ack acoburn
14:27:19 <Zakim> acoburn, you wanted to mention virtual resources
14:27:23 <jeremycaine> q+
14:27:41 <laurens> acoburn: I also recall it this way, we should not proclude virtual resources.
14:27:58 <acoburn> s/proclude/preclude
14:28:02 <laurens> ... If diagrams mention virtual resources, these should be reworked so they are not mentioned.
14:28:33 <acoburn> jeremycaine: my assertion is that virtual resources are not clearly defined
14:28:37 <jeremycaine> q-
14:28:50 <acoburn> laurens: let's pick up the topic of virtual resources next week
14:29:32 <elf-pavlik> #177
14:29:32 <gb> https://github.com/w3c/lws-protocol/issues/177 -> Issue 177 Create Threat Model Note (by elf-pavlik)
14:29:33 <acoburn> ... for existing PRs that mention virtual resources, they will likely not be merged for now
14:29:33 <laurens> ack elf-pavlik
14:29:33 <Zakim> elf-pavlik, you wanted to invite jeremycaine coordinating on diagrams
14:29:59 <acoburn> elf-pavlik: in the issue for the threat model, I would like to invite jeremycaine to work on the diagrams
14:30:13 <acoburn> ... I used the threat modeling language from the W3C guide
14:30:18 <jeremycaine> yes elf-pavlik
14:30:19 <laurens> q?
14:30:54 <acoburn> laurens: add introduction and diagram discussion for next week
14:31:26 <acoburn> laurens: I have a TODO for containment (parent relationship), will address after working on notifications
14:32:05 <elf-pavlik> q+ to ask about #89
14:32:06 <acoburn> termontwouter: related to clarifying text for auxiliary resources, this is largely done and can be marked as such
14:32:15 <laurens> ack elf-pavlik
14:32:15 <Zakim> elf-pavlik, you wanted to ask about #89
14:32:36 <acoburn> elf-pavlik: related to aux resources/metadata, I picked up issue #89
14:33:06 <acoburn> ... would like to get some feedback, especially on some metadata items, such as size and content type
14:33:16 <termontwouter> will do!
14:33:22 <elf-pavlik> also #92
14:33:22 <gb> https://github.com/w3c/lws-protocol/issues/92 -> Issue 92 Reconsider optional metadata of resources such as media-type and size (by laurensdeb) [needs-discussion]
14:34:23 <acoburn> laurens: issue #116 is still in TODO, any progress termontwouter?
14:34:24 <gb> https://github.com/w3c/lws-protocol/issues/116 -> Issue 116 Abstract 'containers' as Link Set representations of arbitrary relational metadata (by termontwouter)
14:34:50 <acoburn> termontwouter: this is an issue that touches on many aspects of LWS. I think most of this has been addressed, and the issue can be closed
14:35:06 <acoburn> ... I will open a more targeted issue for remaining areas
14:35:45 <acoburn> acoburn: Access Request and Notification integration still on my TODO list
14:36:04 <acoburn> laurens: metadata/aux resources status?
14:36:17 <acoburn> termontwouter: this has already been resolved as part of pchampin's PR
14:36:28 <acoburn> laurens: ok, will mark as done
14:36:36 <pchampin> I would consider that there is still work to be done on metadata, but yes, my PR on the terminology touches it
14:36:55 <TallTed> could a link to this spreadsheet be put in the agenda and minutes?
14:37:13 <acoburn> Spreadsheet -> https://docs.google.com/spreadsheets/d/1wiAg8UtF0i73bdMD3TBhC9nFdYLYkobBCbCGSF6XXn0/edit?gid=0#gid=0
14:37:20 <elf-pavlik> q+ to comment on grants & indexes
14:37:40 <TallTed> tnx
14:37:51 <laurens> q?
14:37:55 <laurens> ack elf-pavlik
14:37:55 <Zakim> elf-pavlik, you wanted to comment on grants & indexes
14:38:04 <acoburn> laurens: issue #141 merging DID/CID authn suites
14:38:05 <gb> https://github.com/w3c/lws-protocol/issues/141 -> Issue 141 Does LWS10-AUTHN-SSI-CID already include LWS10-AUTHN-SSI-DID-KEY? (by uvdsl)
14:38:29 <acoburn> acoburn: made a comment a while ago, but no real traction on that direction. Would like to get more feedback
14:39:09 <acoburn> laurens: what about clarifying relationship between Access Requests and type index
14:39:27 <acoburn> elf-pavlik: yes, will look into this with eBremer
14:39:50 <acoburn> laurens: pchampin status of reaching out to IETF OAuth WG?
14:40:22 <acoburn> pchampin: this is in progress
14:40:54 <elf-pavlik> q+
14:40:55 <acoburn> laurens: for threat modeling, Rui was primary, what is the status?
14:41:00 <laurens> ack elf-pavlik
14:41:18 <acoburn> elf-pavlik: I have commented on issue and created an initial diagram as a starting point
14:41:24 <laurens> https://github.com/w3c/lws-protocol/issues/177
14:41:25 <gb> https://github.com/w3c/lws-protocol/issues/177 -> Issue 177 Create Threat Model Note (by elf-pavlik)
14:41:37 <acoburn> ... would like to coordinate with Rui and will follow-up
14:41:55 <acoburn> ... hopefully by next week we will have a PR. If you are interested, please chime in
14:42:23 <acoburn> ... related to the RDF WG, we can have a C4 model (higher level) to provide different views
14:43:09 <acoburn> ... folks are encouraged to comment on issue. the focus in on end-user being different than the resource owner
14:43:47 <acoburn> s/the focus in/the focus is/
14:44:13 <acoburn> laurens: I will look at the issue clarifying semantics of delete
14:44:34 <acoburn> ... what is the status of publication of JSON-LD context
14:44:54 <acoburn> pchampin: asked for transition request for vocabularies as a WG note
14:45:09 <ericP> present+
14:45:33 <acoburn> laurens: with that, we made it through the entire spreadsheet
14:45:38 <elf-pavlik> q+ to ask about query
14:45:43 <laurens> ack elf-pavlik
14:45:43 <Zakim> elf-pavlik, you wanted to ask about query
14:45:50 <jeremycaine> q+ triage meeting
14:46:15 <acoburn> elf-pavlik: since eBremer made PR for type index, there is also a possibility for using QUERY on notifications or aux resources
14:46:25 <acoburn> ... should we look at QUERY more generally?
14:46:48 <acoburn> ... should we invite Raul to a meeting to share expertise with IETF?
14:47:14 <acoburn> laurens: let's open a broader issue about the use of QUERY in LWS
14:47:14 <jeswr> q+ to ask what features of HTTP QUERY are of benefit to notifications and aux resources
14:47:17 <eBremer> q+
14:47:20 <acoburn> elf-pavlik: I will open that issue
14:47:23 <laurens> ack jeswr
14:47:23 <Zakim> jeswr, you wanted to ask what features of HTTP QUERY are of benefit to notifications and aux resources
14:47:48 <acoburn> jeswr: what are the features of QUERY that are of benefit to notifications/aux resources?
14:47:58 <jeremycaine> q+ to ask about triage meeting
14:48:08 <jeremycaine> q- triage meeting
14:48:09 <acoburn> elf-pavlik: there are some existing discussions in the various issues
14:48:21 <acoburn> ... I will link to the comments
14:48:28 <laurens> ack eBremer
14:49:09 <acoburn> eBremer: I am working on a document that describes "if you are going to implement SPARQL, here's what you should consider"
14:49:21 <laurens> ack jeremycaine
14:49:21 <Zakim> jeremycaine, you wanted to ask about triage meeting
14:49:29 <acoburn> ... this will inform us about affordances that may be needed now
14:49:50 <laurens> https://www.w3.org/events/meetings/41133143-8a1f-4f4a-bf69-44daec340f79/
14:50:04 <laurens> q?
14:50:06 <acoburn> jeremycaine: are the triage meetings continuing?
14:50:12 <acoburn> acoburn: yes, every friday
14:50:15 <jeremycaine> q+
14:50:19 <laurens> ack jeremycaine
14:51:33 <acoburn> rrsagent, make minutes
14:51:35 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/29-lws-minutes.html acoburn
14:51:53 <TallTed> present+
14:52:01 <acoburn> present+ TallTed
14:52:08 <acoburn> present+ laurens
14:52:13 <acoburn> rrsagent, make minutes
14:52:14 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/29-lws-minutes.html acoburn
14:57:25 <TallTed> s/we should be able to talk about/we should be able to talk about it
14:57:32 <RRSAgent> I have made the request to generate https://www.w3.org/2026/06/29-lws-minutes.html TallTed
21:59:40 <gb> gb has joined #lws