13:56:58 <RRSAgent> RRSAgent has joined #lws
13:57:03 <RRSAgent> logging to https://www.w3.org/2026/04/20-lws-irc
13:57:48 <acoburn> agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20260420T100000/#agenda
13:57:49 <agendabot> clear agenda
13:57:49 <agendabot> agenda+ Introduction and announcements
13:57:49 <agendabot> agenda+ Notifications feature #129: open discussion
13:57:49 <agendabot> agenda+ Container features and proposals
13:57:49 <agendabot> agenda+ Preparation for face-to-face meeting
13:58:04 <acoburn> zakim, start meeting
13:58:04 <Zakim> RRSAgent, make logs Public
13:58:06 <Zakim> please title this meeting ("meeting: ..."), acoburn
13:58:22 <acoburn> meeting: Linked Web Storage
13:58:32 <acoburn> rrsagent, make meeting
13:58:32 <RRSAgent> I'm logging. I don't understand 'make meeting', acoburn.  Try /msg RRSAgent help
13:58:47 <acoburn> rrsagent, make minutes
13:58:49 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/20-lws-minutes.html acoburn
13:58:56 <acoburn> s/rrsagent, make meeting//
13:59:37 <acoburn> previous meeting: https://www.w3.org/2026/04/13-lws-minutes.html
13:59:49 <eBremer> eBremer has joined #lws
13:59:51 <acoburn> next meeting: https://www.w3.org/2026/04/27-lws-minutes.html
14:00:25 <TallTed> TallTed has joined #lws
14:00:33 <acoburn> chair: acoburn
14:00:39 <acoburn> present+
14:01:14 <gibsonf1> gibsonf1 has joined #lws
14:01:21 <gibsonf1> present+
14:01:52 <pchampin> present+
14:01:55 <laurens> laurens has joined #lws
14:01:55 <ericP> ericP has joined #lws
14:01:59 <laurens> present+
14:02:03 <Luke> Luke has joined #lws
14:02:26 <ericP> scribe: ericP
14:02:31 <eBremer> present+
14:02:35 <Luke> present+
14:02:36 <ericP> present+
14:03:20 <RazaN> RazaN has joined #lws
14:03:41 <TallTed> present+
14:03:57 <acoburn> zakim, open agendum 1
14:03:57 <Zakim> agendum 1 -- Introduction and announcements -- taken up [from agendabot]
14:04:51 <ericP> acoburn: F2F meeting M,Tue next week
14:04:56 <RazaN> present+
14:05:06 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/20-lws-minutes.html TallTed
14:05:12 <ericP> ... props to jesse and ODI
14:05:29 <ericP> ... remote attendance possible; see invites in W3C calendar
14:05:54 <ericP> ... Jesse sent email asking for RSVPs
14:06:18 <ericP> ... ODI is behind a reception desk so receptionist will need your name in advance
14:07:05 <ryey> ryey has joined #lws
14:07:07 <ryey> present+
14:07:12 <jeswr> jeswr has joined #lws
14:07:15 <ericP> ... said email includes location. please aim to be a bit early 'cause we have a packed agenda
14:07:16 <jeswr> present+
14:07:30 <acoburn> zakim, open agendum 2
14:07:30 <Zakim> agendum 2 -- Notifications feature #129: open discussion -- taken up [from agendabot]
14:08:24 <ericP> acoburn: the repo has PRs for activity-stream-based notifications
14:08:39 <ericP> ... required reading for the F2F
14:09:58 <ericP> laurens: we have bindings for webhooks, websocks and @@@1
14:10:12 <ericP> ... all are considered optional
14:10:17 <elf-pavlik> https://raw.githack.com/w3c/lws-protocol/notifications-spec/lws10-notifications/index.html
14:10:52 <ericP> ... new terms:
14:11:12 <ericP> ... .. subscription: recieve notifications
14:11:24 <ericP> ... .. subscriber:
14:11:55 <ericP> ... .. inbox: POST-able recipient of notifications (server-based instead of websockets)
14:12:51 <ericP> ... .. capablility: -- looking for a better term because this term is used elsewhere in LWS for other purposes
14:13:11 <ericP> ... discovery: advertise support for notifications
14:14:42 <ericP> ... notification envelope inspired by activity streams
14:15:07 <ericP> ... the optiona phase may drop out
14:17:07 <ericP> ... activity data model eincludes action taxonomy as well as actor, target, origin
14:17:35 <ericP> ... servers may dispatch multiple notification in a single envelope
14:17:46 <gibsonf1> +1
14:19:19 <ericP> ... subscription types: ServerSet, WebSocket, Webhook
14:20:11 <ericP> ... suggest we postpone phases (i.e. anything other than when a resource has been committed to a server)
14:20:49 <ericP> ... subscriptions are transitive over containership hierarchies
14:21:23 <ericP> ... auth enforced at delivery time (just-in-time for acceptance or denial)
14:22:24 <ericP> ... open Q: should termination apply up the hierarchy? if so, how?
14:22:52 <acoburn> q+ to ask about named subscription types
14:23:03 <acoburn> ack next
14:23:04 <Zakim> acoburn, you wanted to ask about named subscription types
14:23:35 <ericP> acoburn: given WebSockets, ServerSet, WebHooks; are these the right three?
14:24:06 <ericP> ... i think we want 1+ that is synchronous and antother 1+ that is async
14:24:41 <pchampin> LGTM
14:24:44 <ericP> laurens: [continuing with subscription types]
14:25:14 <ericP> ... WebSocket subscrption section defines the the response with the capability URL
14:25:52 <ericP> ... ServerSent events follow a similar pattern
14:26:27 <ericP> ... includes response requirements, e.g. content type
14:26:43 <ericP> ... WebHook notifications (async) is the most elaborate
14:27:34 <ericP> ... subscriber supplies inbox URL and expires datetime
14:28:08 <ericP> looking for feedback from WG on subscription management
14:28:19 <ericP> ... looking for feedback from WG on subscription management
14:28:32 <ericP> ... so far, only requres a GET operation
14:29:29 <ericP> ... for authn:WebHooks requires standard verification conventions
14:29:58 <ericP> ... [ signature details]
14:30:58 <ericP> acoburn: tx laurens
14:31:26 <ericP> ... there's a lot there. required reading. add comments to the PR or jot down notes for the F2F meeting
14:32:11 <ericP> ... this is the last of the three big proposals we mentioned needing during the last F2F
14:32:41 <ericP> ... where possible, please add coments BEFORE next week
14:32:50 <acoburn> q?
14:32:52 <gibsonf1> Great work!
14:33:05 <acoburn> zakim, open agendum 3
14:33:05 <Zakim> agendum 3 -- Container features and proposals -- taken up [from agendabot]
14:33:27 <ericP> acoburn: we currently have a container definition
14:33:44 <ericP> ... (kudos to laurens)
14:34:05 <ericP> ... there are alternate proposals, large and small
14:34:18 <ericP> ... the group needs to align on a way to handle containers
14:34:44 <ericP> ... we'll confugse people if we go in tow many directiosn in the spec
14:34:52 <ericP> ... so we need consensus on a core
14:35:18 <ericP> ... we have an open PR for polyhierarchies
14:35:29 <ericP> ... (multi-containment)
14:36:21 <ericP> ... propose an hour set aside during the F2F. folks pitch on their favorite PR
14:36:31 <ericP> ... again, need to find consensus
14:37:25 <pchampin> +1 to have prior art
14:37:31 <ericP> ... feel free to propose, but make sure it's well-defined. prefer prior art
14:39:36 <acoburn> zakim, open agendum 4
14:39:36 <Zakim> agendum 4 -- Preparation for face-to-face meeting -- taken up [from agendabot]
14:40:04 <ericP> acoburn: jesse, any logitics?
14:40:51 <ericP> jeswr: pls respond to survey so we can manage food prefs and to get past armed receptionist
14:41:33 <ericP> acoburn: i don't believe ODI will foot the bill, but we can have make a reservation for the WG
14:42:48 <ericP> acoburn: i'm removing inconsistency and open issues from agenda
14:43:04 <ericP> ... this terminology section will be a good time to talk about containers
14:43:17 <ericP> ... after lunch, but before terminology
14:44:06 <ericP> any comments on the agenda?
14:45:20 <ericP> RRSAgent, please draft minutes
14:45:21 <RRSAgent> I have made the request to generate https://www.w3.org/2026/04/20-lws-minutes.html ericP
14:45:35 <ericP> RRSAgent, please make log public
14:46:12 <ericP> ericP has left #lws
14:47:24 <acoburn> acoburn has left #lws