13:55:03 <RRSAgent> RRSAgent has joined #lws
13:55:08 <RRSAgent> logging to https://www.w3.org/2026/08/10-lws-irc
13:55:08 <Zakim> Zakim has joined #lws
13:55:50 <acoburn> acoburn has changed the topic to: Linked Web Storage - 2026-08-10 - https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20260810T100000/
13:55:56 <acoburn> zakim, start meeting
13:55:56 <Zakim> RRSAgent, make logs Public
13:55:58 <Zakim> please title this meeting ("meeting: ..."), acoburn
13:56:10 <acoburn> agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20260810T100000/#agenda
13:56:10 <agendabot> clear agenda
13:56:10 <agendabot> agenda+ Introduction & Announcements
13:56:10 <agendabot> agenda+ TPAC Agenda -> Issue#176 https://github.com/w3c/lws-protocol/issues/176
13:56:10 <agendabot> agenda+ FPWD for notification-webhook & LWS index
13:56:10 <agendabot> agenda+ Discussion: Remove AS dependency for container data model -> PR#219 https://github.com/w3c/lws-protocol/pull/219
13:56:14 <agendabot> agenda+ Discussion: lws:StorageResource terminology -> Issue#220 https://github.com/w3c/lws-protocol/issues/220
13:56:17 <agendabot> agenda+ Status of WebSocket / SSE / Streaming Fetch for notifications -> PR#162 https://github.com/w3c/lws-protocol/pull/162
13:56:20 <agendabot> agenda+ Volunteers for ETag & Slug header text changes
13:56:23 <acoburn> meeting: Linked Web Storage
13:56:43 <acoburn> rrsagent, make minutes
13:56:44 <RRSAgent> I have made the request to generate https://www.w3.org/2026/08/10-lws-minutes.html acoburn
13:57:10 <acoburn> previous meeting: https://www.w3.org/2026/08/03-lws-minutes.html
13:57:17 <acoburn> next meeting: https://www.w3.org/2026/08/17-lws-minutes.html
13:57:22 <acoburn> rrsagent, make minutes
13:57:23 <RRSAgent> I have made the request to generate https://www.w3.org/2026/08/10-lws-minutes.html acoburn
13:57:30 <acoburn> chair: acoburn
13:57:32 <acoburn> present+
13:59:41 <eBremer> eBremer has joined #lws
14:00:10 <gibsonf1> gibsonf1 has joined #lws
14:00:41 <eBremer> present+
14:01:03 <gibsonf1> present+
14:01:07 <termontwouter> termontwouter has joined #lws
14:02:14 <termontwouter> present+
14:03:28 <jeremycaine> jeremycaine has joined #lws
14:03:34 <elf-pavlik> elf-pavlik has joined #lws
14:03:34 <jeremycaine> present+
14:03:47 <elf-pavlik> present+
14:04:02 <acoburn> scribe: jeremycaine
14:04:05 <jeremycaine> scribe+
14:04:38 <acoburn> zakim, next agendum
14:04:38 <Zakim> agendum 1 -- Introduction & Announcements -- taken up [from agendabot]
14:05:04 <jeremycaine> TPAC is 2.5 mo away
14:05:11 <jeremycaine> early sign up has passed
14:05:31 <jeremycaine> remote option will be available
14:05:41 <elf-pavlik> https://www.w3.org/news-events/tpac/2026/registration/#registration
14:06:23 <acoburn> zakim, next agendum
14:06:23 <Zakim> agendum 2 -- TPAC Agenda -> Issue#176 https://github.com/w3c/lws-protocol/issues/176 -- taken up [from agendabot]
14:06:40 <Rbreitman> Rbreitman has joined #lws
14:06:47 <Rbreitman> present+
14:06:52 <jeremycaine> acoburn: we have number of slots, but don't need to figure out agenda today
14:07:29 <elf-pavlik> #176
14:07:36 <jeremycaine> ... issue 176, general thoughts for the agenda e.g. what are things we need to do
14:07:42 <jeremycaine> ... to get to CR status
14:08:09 <jeremycaine> ... e.g. test suite; call for implementors
14:08:14 <elf-pavlik> q+ to ask about the est suite
14:08:23 <acoburn> ack next
14:08:24 <Zakim> elf-pavlik, you wanted to ask about the est suite
14:08:43 <laurens> laurens has joined #lws
14:08:44 <Rbreitman> q+
14:08:47 <laurens> present+
14:08:48 <jeremycaine> elf-pavlik: Jesse was suggest new task force around test suite
14:08:53 <acoburn> ack next
14:09:10 <jeremycaine> Rbreitman: not heard from Jesse; will ask for status
14:09:39 <jeremycaine> acoburn: generally get test suite every 3rd week - next is 17th aug - ideally Shamu would attend
14:09:55 <elf-pavlik> we should coordinate with https://github.com/lws-contrib/lws-test-suite/
14:10:15 <jeremycaine> ... we are pretty far along (the spec) so we need to move on testing
14:10:39 <jeremycaine> ... (tpac) are we feature complete? it's harder after CR status
14:11:04 <jeremycaine> ... adding entirely new features is harder
14:11:37 <jeremycaine> ... what options do we have for deliverables
14:11:57 <jeremycaine> ... REC -e.g protocol spec ; authn suites etc
14:12:17 <jeremycaine> ... WG note: does not have normative status e.g. like threat model, use case docs
14:12:52 <jeremycaine> ... docs whose intention is not REC track, but is normative
14:13:05 <ericP> ericP has joined #lws
14:13:16 <jeremycaine> ... permanent Candidate Recommendation
14:13:50 <jeremycaine> ... REC vs CR - where does web hook, notifications and so on go
14:14:10 <elf-pavlik> q+ to ask how does it fit with admin extension and later recharter
14:14:12 <jeremycaine> ... WG Note is not viable for those normative statements
14:14:18 <acoburn> ack next
14:14:19 <Zakim> elf-pavlik, you wanted to ask how does it fit with admin extension and later recharter
14:14:42 <jeremycaine> elf-pavlik: do we do CR during timeline extensions
14:14:48 <jeremycaine> acoburn: this is in flux
14:15:11 <jeremycaine> ... we will ask for administrative extensions - about 4 mo
14:15:27 <jeremycaine> ... give us WG time, after Sep 2026
14:15:46 <jeremycaine> ... extension ends when new charter starts
14:16:07 <jeremycaine> ... could start Nov 2026, maybe more likely Jan/Feb 2027
14:16:15 <jeremycaine> ... CR would be in the new charter
14:16:41 <jeremycaine> ... relative date is charter start plus one month
14:16:55 <ericP> present+
14:17:03 <jeremycaine> ... e.g. if new charter starts Jan, then CR starts Feb
14:18:07 <acoburn> zakim, next agendum
14:18:07 <Zakim> agendum 3 -- FPWD for notification-webhook & LWS index -- taken up [from agendabot]
14:18:40 <jeremycaine> acoburn: notification and index are not on w3c website
14:19:01 <jeremycaine> ... for a first public working draft needs a vote - target 17th aug -
14:19:39 <acoburn> zakim, next agendum
14:19:39 <Zakim> agendum 4 -- Discussion: Remove AS dependency for container data model -> PR#219 https://github.com/w3c/lws-protocol/pull/219 -- taken up [from agendabot]
14:20:15 <jeremycaine> acoburn: hoping to vote on this next week 17th
14:21:19 <jeremycaine> ... this PR remaps activity streams vocab to new vocab
14:21:56 <jeremycaine> ... we already have an lws vocab
14:22:54 <elf-pavlik> q+ to suggest raising an issue with Social WG
14:23:07 <acoburn> ack next
14:23:08 <Zakim> elf-pavlik, you wanted to suggest raising an issue with Social WG
14:23:27 <jeremycaine> elf-pavlik: raise an issue and why we can't reuse these terms
14:23:59 <jeremycaine> s/and why/as to why/
14:24:54 <elf-pavlik> q+ to comment on domain/range
14:25:14 <acoburn> ack next
14:25:15 <Zakim> elf-pavlik, you wanted to comment on domain/range
14:25:39 <eBremer> q+
14:25:40 <jeremycaine> elf-pavlik: mostly affects people who run listeners
14:26:57 <acoburn> ack next
14:27:00 <jeremycaine> acoburn: there are other vocabs too
14:27:20 <jeremycaine> eBremer: dcterms ?
14:27:43 <jeremycaine> acoburn: yes - will fix in PR - dct = dcterms
14:28:51 <jeremycaine> elf-pavlik: can reach out to Social WG, but would prefer help
14:29:23 <acoburn> zakim, next agendum
14:29:23 <Zakim> agendum 5 -- Discussion: lws:StorageResource terminology -> Issue#220 https://github.com/w3c/lws-protocol/issues/220 -- taken up [from agendabot]
14:29:50 <jeremycaine> acoburn: another gap in feature set
14:30:10 <jeremycaine> ... LWS Storage Resource not defined in LWS vocab
14:32:05 <jeremycaine> ... 3 options with pro/cons
14:32:23 <jeremycaine> ... no PR, but get sense from group via issue
14:32:28 <elf-pavlik> q+ to ask how access request is using it
14:32:39 <acoburn> ack next
14:32:40 <Zakim> elf-pavlik, you wanted to ask how access request is using it
14:32:41 <gibsonf1> option 4 - include LWS in the term so there is no jsonLd conflict
14:32:50 <jeremycaine> elf-pavlik: access request target defn
14:33:04 <jeremycaine> ... (example 15)
14:33:29 <gibsonf1> q+
14:33:34 <jeremycaine> acoburn: need to specify target in an access request (example 15)
14:34:17 <jeremycaine> elf-pavlik: diff between data resource vs container resource
14:34:26 <jeremycaine> elf-pavlik: type could be an array
14:34:27 <termontwouter> q+
14:34:40 <jeremycaine> acoburn: type could be an array
14:35:56 <jeremycaine> ... currently it allows for access for any type
14:36:20 <acoburn> ack next
14:37:20 <jeremycaine> gibsonf1: simplest term is LWSResource
14:37:28 <jeremycaine> ... little chance of conflict
14:37:51 <jeremycaine> ... as a 4th option
14:37:55 <acoburn> ack next
14:38:04 <elf-pavlik> my main point is that we need to clarify semantics first before finalizing the name
14:38:28 <jeremycaine> termontwouter: prefer something before Resource
14:39:12 <jeremycaine> ... could we just add to terminology section that LWS Storage Resource is shortened to LWS Resource?
14:42:06 <jeremycaine> ... key concern is its a feature hole
14:42:23 <jeremycaine> ... next step, team please comment so we can take forward
14:42:34 <acoburn> zakim, next agendum
14:42:34 <Zakim> agendum 6 -- Status of WebSocket / SSE / Streaming Fetch for notifications -> PR#162 https://github.com/w3c/lws-protocol/pull/162 -- taken up [from agendabot]
14:43:05 <jeremycaine> acoburn: old PR, what is status laurens?
14:43:22 <jeremycaine> laurens: probably needs to be closed
14:43:24 <elf-pavlik> q+
14:43:43 <acoburn> ack next
14:43:43 <jeremycaine> ... end of august, goal for new PR to resolve and close #162
14:43:44 <gb> https://github.com/w3c/lws-protocol/pull/162 -> PR 162 feat(notifications): Add WebSocket and Server-Sent Event channels (by laurensdeb) [notifications]
14:43:59 <jeremycaine> elf-pavlik: i'm looking at RDF messages
14:44:14 <jeremycaine> ... RDF could be optional
14:45:36 <jeremycaine> ... what is motivation, several topics to be discussed
14:46:24 <jeremycaine> acoburn: how long to resolve this? ... next month or into Fall
14:47:05 <laurens> q+
14:47:23 <acoburn> ack next
14:47:29 <jeremycaine> laurens: are the solid issues in the PR?
14:48:04 <elf-pavlik> https://github.com/w3c/lws-protocol/issues/66
14:48:05 <gb> https://github.com/w3c/lws-protocol/issues/66 -> Issue 66 Solid Compatibility / Migration Work Item (by acoburn) [needs-discussion] [work-item]
14:49:14 <acoburn> https://github.com/jeswr/lws-solid-diff/blob/main/DIFF.md
14:49:48 <jeremycaine> laurens: choices made in past meeting in Ghent
14:50:08 <jeremycaine> ... I'll check and get back to this
14:50:50 <jeremycaine> ... many ideas in Solid protocol have not been implemented
14:51:43 <acoburn> zakim, next agendum
14:51:43 <Zakim> agendum 7 -- Volunteers for ETag & Slug header text changes -- taken up [from agendabot]
14:52:36 <jeremycaine> laurens: created action item
14:52:59 <jeremycaine> acoburn: open a PR and then vote next week 17th
14:53:36 <jeremycaine> ... AOB?
14:53:51 <gibsonf1> q+  to ask about Read operation
14:53:53 <jeremycaine> ... US hol 7th Sep - Labor Day
14:54:07 <jeremycaine> ... can we cancel that day?
14:55:23 <acoburn> ack next
14:55:24 <Zakim> gibsonf, you wanted to ask about Read operation
14:55:42 <jeremycaine> gibsonf1: current spec, have begun implementation
14:56:42 <jeremycaine> acoburn: needs a discussion on media types
14:57:15 <jeremycaine> ... start at storage resource, then root container, what are media types in the container
14:58:10 <jeremycaine> ... alt. if you have URL but cannot find parent, do a HEAD requests, see type ... use that to proceed with content neg
14:58:46 <elf-pavlik> q+ to mention optimisations
14:58:50 <jeremycaine> gibsonf1: at scale, there will be a lot of requests
15:00:22 <elf-pavlik> https://github.com/w3c/lws-protocol/issues/188#issuecomment-5158897912
15:00:23 <gb> https://github.com/w3c/lws-protocol/issues/188 -> Issue 188 Create reference explaining consistent use of HTTP content-type, profile, prefer etc. (by elf-pavlik) [editorial]
15:00:43 <elf-pavlik> q-
15:03:34 <jeremycaine> acoburn: can continue gibsonf1 implementation discussion
15:03:37 <elf-pavlik> ericP: https://github.com/w3c/lws-protocol/pull/113#issuecomment-5010415759 ?
15:03:38 <gb> https://github.com/w3c/lws-protocol/pull/113 -> PR 113 Support for auxiliary resources and manifest (#67) (by damooo) [metadata]
15:03:41 <acoburn> rrsagent, make minutes
15:03:42 <RRSAgent> I have made the request to generate https://www.w3.org/2026/08/10-lws-minutes.html acoburn