Meeting minutes
Introduction and announcements
acoburn: F2F meeting M,Tue next week
… props to jesse and ODI
… remote attendance possible; see invites in W3C calendar
… Jesse sent email asking for RSVPs
… ODI is behind a reception desk so receptionist will need your name in advance
… said email includes location. please aim to be a bit early 'cause we have a packed agenda
Notifications feature #129: open discussion
acoburn: the repo has PRs for activity-stream-based notifications
… required reading for the F2F
laurens: we have bindings for webhooks, websocks and @@@1
… all are considered optional
<elf-pavlik> https://
laurens: new terms:
… .. subscription: recieve notifications
… .. subscriber:
… .. inbox: POST-able recipient of notifications (server-based instead of websockets)
… .. capablility: -- looking for a better term because this term is used elsewhere in LWS for other purposes
… discovery: advertise support for notifications
… notification envelope inspired by activity streams
… the optiona phase may drop out
… activity data model eincludes action taxonomy as well as actor, target, origin
… servers may dispatch multiple notification in a single envelope
<gibsonf1> +1
laurens: subscription types: ServerSet, WebSocket, Webhook
… suggest we postpone phases (i.e. anything other than when a resource has been committed to a server)
… subscriptions are transitive over containership hierarchies
… auth enforced at delivery time (just-in-time for acceptance or denial)
… open Q: should termination apply up the hierarchy? if so, how?
<Zakim> acoburn, you wanted to ask about named subscription types
acoburn: given WebSockets, ServerSet, WebHooks; are these the right three?
… i think we want 1+ that is synchronous and antother 1+ that is async
<pchampin> LGTM
laurens: [continuing with subscription types]
… WebSocket subscrption section defines the the response with the capability URL
… ServerSent events follow a similar pattern
… includes response requirements, e.g. content type
… WebHook notifications (async) is the most elaborate
… subscriber supplies inbox URL and expires datetime
looking for feedback from WG on subscription management
… looking for feedback from WG on subscription management
… so far, only requres a GET operation
… for authn:WebHooks requires standard verification conventions
… [ signature details]
acoburn: tx laurens
… there's a lot there. required reading. add comments to the PR or jot down notes for the F2F meeting
… this is the last of the three big proposals we mentioned needing during the last F2F
… where possible, please add coments BEFORE next week
<gibsonf1> Great work!
Container features and proposals
acoburn: we currently have a container definition
… (kudos to laurens)
… there are alternate proposals, large and small
… the group needs to align on a way to handle containers
… we'll confugse people if we go in tow many directiosn in the spec
… so we need consensus on a core
… we have an open PR for polyhierarchies
… (multi-containment)
… propose an hour set aside during the F2F. folks pitch on their favorite PR
… again, need to find consensus
<pchampin> +1 to have prior art
acoburn: feel free to propose, but make sure it's well-defined. prefer prior art
Preparation for face-to-face meeting
acoburn: jesse, any logitics?
jeswr: pls respond to survey so we can manage food prefs and to get past armed receptionist
acoburn: i don't believe ODI will foot the bill, but we can have make a reservation for the WG
acoburn: i'm removing inconsistency and open issues from agenda
… this terminology section will be a good time to talk about containers
… after lunch, but before terminology
any comments on the agenda?