13:49:04 <RRSAgent> RRSAgent has joined #lws
13:49:08 <RRSAgent> logging to https://www.w3.org/2025/09/15-lws-irc
13:49:08 <Zakim> RRSAgent, make logs Public
13:49:09 <Zakim> please title this meeting ("meeting: ..."), laurens
13:49:17 <laurens> meeting: Linked Web Storage WG -- 2025-09-15
13:49:24 <laurens> agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20250915T100000/
13:49:24 <agendabot> clear agenda
13:49:24 <agendabot> agenda+ Introductions & Announcements
13:49:24 <agendabot> agenda+ Action items
13:49:24 <agendabot> agenda+ Prioritization of use cases
13:49:24 <agendabot> agenda+ Face-to-face meeting agenda
13:49:46 <laurens> Chair: laurens
13:56:18 <acoburn> acoburn has joined #lws
13:56:58 <TallTed> regrets+
13:59:16 <acoburn> acoburn has changed the topic to: Linked Web Storage -- 2025-09-15: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20250915T100000/
13:59:27 <acoburn> zakim, start meeting
13:59:27 <Zakim> RRSAgent, make logs Public
13:59:29 <Zakim> please title this meeting ("meeting: ..."), acoburn
13:59:33 <acoburn> meeting: Linked Web Storage
13:59:42 <uvdsl> uvdsl has joined #lws
13:59:49 <acoburn> agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20250915T100000/#agenda
13:59:49 <agendabot> clear agenda
13:59:49 <agendabot> agenda+ Introductions & Announcements
13:59:49 <agendabot> agenda+ Action items
13:59:49 <agendabot> agenda+ Prioritization of use cases
13:59:49 <agendabot> agenda+ Face-to-face meeting agenda
14:00:57 <gibsonf1> gibsonf1 has joined #lws
14:00:58 <acoburn> present+
14:01:03 <gibsonf1> present+
14:01:47 <bendm> bendm has joined #lws
14:01:56 <eBremer> eBremer has joined #lws
14:02:05 <gibsonf1> scribe+
14:02:07 <eBremer> present+
14:02:12 <laurens> present+
14:02:12 <acoburn> RRSAgent, make minutes
14:02:13 <RRSAgent> I have made the request to generate https://www.w3.org/2025/09/15-lws-minutes.html acoburn
14:02:22 <uvdsl> present+
14:02:22 <bendm> present+
14:03:34 <bartb> bartb has joined #lws
14:03:52 <bartb> present+
14:04:09 <gibsonf1> laurens: Sent out information on f2f meeting and put items on W3C calendar - also indicate attendance there would be great
14:04:19 <acoburn> zakim, open agendum 1
14:04:19 <Zakim> agendum 1 -- Introductions & Announcements -- taken up [from agendabot]
14:05:09 <gibsonf1> pchampin: TPAC open to demos to all WGs - maybe someone has ideas
14:05:18 <pchampin> present+
14:05:34 <acoburn> zakim, open agendum 2
14:05:34 <Zakim> agendum 2 -- Action items -- taken up [from agendabot]
14:06:03 <dmitriz> dmitriz has joined #lws
14:06:27 <laurens> zakim, open agendum 3
14:06:27 <Zakim> agendum 3 -- Prioritization of use cases -- taken up [from agendabot]
14:06:37 <gibsonf1> laurens: closed action item for https://github.com/w3c/lws-ucs/issues/215#issuecomment-3292271222
14:06:37 <gb> https://github.com/w3c/lws-ucs/issues/215 -> Issue 215 [UC] Mechanism to access a resource identifier in a storage with identifier that points to a different storage (by gibsonf1) [triage] [usecase]
14:08:06 <gibsonf1> acoburn: LWS requirements survey.  Gives a sense of where people stand.  Want to set up a must have requirments bucket, and secondly a nice to have bucket, and finally, a set these aside for now bucket
14:08:26 <ryey> ryey has joined #lws
14:08:30 <ryey> present+
14:09:20 <bendm> q+ to ask about number 3 vs 5
14:10:19 <gibsonf1> ... This is just an initial cut to start focus on most important for f2f meeting next month.
14:10:53 <gibsonf1> bendm:  Was hard to decide on difference between 3 and 5 rating for survey.
14:11:48 <gibsonf1> acoburn: +1 = focus  -1 = out of scope
14:12:13 <gibsonf1> acoburn:  Globally unique identifiers
14:12:18 <gibsonf1> +1
14:12:28 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-globally-unique-identifiers Globally Unique IDs
14:12:38 <RazaN> RazaN has joined #lws
14:13:12 <bartb> +1
14:13:12 <bendm> +1
14:13:13 <eBremer> +1
14:13:13 <laurens> +1
14:13:14 <pchampin> +1
14:13:16 <gibsonf1> acoburn:  If you think spec should include Globally unique identifiers, please vote now
14:13:16 <acoburn> +1
14:13:19 <gibsonf1> +1
14:13:24 <ryey> +1
14:13:44 <dmitriz> +0.5
14:15:02 <gibsonf1> pchampin:  start with strawpoll:   for voting
14:15:52 <pchampin> s/acoburn:  Globally unique identifiers/STRAWPOLL: Globally unique identifiers
14:16:15 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-use-of-service-providers Use of Service Providers
14:16:19 <gibsonf1> STRAWPOLL: Use of Service Providers
14:16:35 <ryey> +1
14:16:37 <gibsonf1> +1
14:16:44 <bendm> +1
14:16:47 <eBremer> +1
14:16:49 <acoburn> +1
14:16:50 <dmitriz> -0 (I don't understand this requirement at all)
14:16:56 <laurens> +1
14:16:57 <bartb> +1
14:16:58 <RazaN> RazaN has joined #lws
14:18:29 <gibsonf1> acoburn:  has to do with trust relationships between different entities.  What normative text do we agree on in spec.  To focus on priorities
14:18:30 <pchampin> +0
14:18:38 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-control-of-storages Control of Storages
14:18:48 <gibsonf1> STRAWPOLL: Control of Storages
14:18:54 <gibsonf1> +1
14:19:03 <ryey> +1
14:19:05 <acoburn> +1
14:19:07 <bartb> +1
14:19:07 <eBremer> +1
14:19:09 <pchampin> +1
14:19:10 <bendm> +1
14:19:21 <dmitriz> -1 (for the 'Exactly 1 controller' part)
14:19:40 <dmitriz> but seems like a fine feature otherwise.
14:19:41 <RazaN> +1
14:19:55 <laurens> +1
14:20:06 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-delegation-of-control Delegation of Control
14:20:06 <gibsonf1> STRAWPOLL: Delegation of Control
14:20:18 <bendm> dmitriz it's mentioned that there could be a group of controllers too, so I'm giving it a benefit of a doubt :)
14:20:25 <dmitriz> +1
14:20:27 <pchampin> +1
14:20:29 <eBremer> +1
14:20:31 <gibsonf1> +1
14:20:32 <ryey> +1
14:20:33 <acoburn> +1
14:20:34 <bendm> -0
14:20:35 <bartb> +1
14:20:47 <laurens> +1
14:20:50 <RazaN> +1
14:21:04 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-transfer-of-control Transfer of Control
14:21:05 <gibsonf1> STRAWPOLL: Transfer of Control
14:21:10 <acoburn> +0
14:21:12 <ryey> +0
14:21:14 <laurens> -1
14:21:17 <dmitriz> +1
14:21:19 <bartb> +1
14:21:22 <eBremer> +1
14:21:24 <bendm> The difference between the two is very vague to me
14:21:24 <pchampin> +0
14:21:25 <bendm> -0
14:21:54 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-storage-portability Storage Portability
14:22:01 <gibsonf1> STRAWPOLL: Storage Portability
14:22:07 <dmitriz> +1
14:22:09 <gibsonf1> +1
14:22:10 <RazaN> +1
14:22:12 <eBremer> +1
14:22:15 <bartb> -1
14:22:15 <bendm> +1
14:22:18 <laurens> +1 (but needs proper scoping)
14:22:25 <acoburn> +1
14:22:28 <ryey> +1 (more scoping, but itself is needed)
14:22:49 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-adding-updating-deleting-resources-in-storage Adding Updating Deleting Resources in Storage
14:22:51 <gibsonf1> STRAWPOLL: Adding, Updating, Deleting Resources in Storage
14:22:53 <gibsonf1> +1
14:22:53 <eBremer> +1
14:22:56 <bendm> +1
14:22:58 <acoburn> +1
14:23:00 <bartb> +1
14:23:01 <RazaN> +1
14:23:03 <ryey> +1
14:23:03 <laurens> +1
14:23:05 <dmitriz> +1 (tho this seems like an odd one - maybe too obvious?)
14:23:19 <pchampin> +1
14:23:27 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-data-sharing Data Sharing
14:23:27 <gibsonf1> STRAWPOLL: Data Sharing
14:23:35 <acoburn> +1
14:23:37 <laurens> +1
14:23:37 <bendm> +1
14:23:37 <dmitriz> +1
14:23:38 <eBremer> +1
14:23:38 <ryey> +1
14:23:40 <bartb> +1
14:23:45 <pchampin> +1
14:23:53 <gibsonf1> +1
14:23:59 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-auditable-trail Auditable Trail
14:24:04 <gibsonf1> STRAWPOLL: Auditable Trail
14:24:06 <laurens> -1
14:24:08 <acoburn> +0
14:24:11 <pchampin> +0
14:24:11 <bendm> -1
14:24:12 <eBremer> +0
14:24:13 <bartb> -1
14:24:16 <gibsonf1> +1
14:24:19 <RazaN> -1
14:24:25 <dmitriz> +0 (I think the main spec needs to provide hook/affordance, but not specify)
14:24:25 <ryey> -1 (some part may be useful, but this thing as a whole is not for now)
14:25:13 <gibsonf1> STRAWPOLL: Serialization Format
14:25:13 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-serialization-format Serialization Format
14:25:17 <gibsonf1> +1
14:25:19 <laurens> +1
14:25:20 <bartb> +1
14:25:21 <acoburn> +1
14:25:24 <eBremer> +1
14:25:24 <RazaN> +1
14:25:28 <ryey> +1
14:25:30 <dmitriz> -0 (don't quite understand this one..)
14:25:35 <bendm> q+
14:25:45 <laurens> ack bendm
14:25:45 <Zakim> bendm, you wanted to ask about number 3 vs 5 and to
14:26:00 <gibsonf1> bendm: Not clear whether this implies content negotiation or just serialize data in any way
14:26:52 <gibsonf1> acoburn: doubtful that any data any way (too broad), but some clear expectation around how certain resources are serialized.  For example, containers require at least one required serialization format.
14:27:07 <pchampin> FTR, the discussion we had about this req https://www.w3.org/2025/08/11-lws-minutes.html#1c61
14:27:24 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-offline-access-and-synchronization Offline Access and Synchronization
14:27:24 <gibsonf1> STRAWPOLL: Offline Access and Synchronization
14:27:36 <gibsonf1> -0
14:27:36 <bartb> -1
14:27:44 <bendm> -1
14:27:45 <dmitriz> +0.5 (I think spec should provide hooks/affordance, but we likely won't get enough time to standardize this. but it IS important.)
14:27:57 <acoburn> -0
14:27:58 <ryey> +0 (good to have something prepared for that, but not as core spec)
14:27:58 <laurens> -1
14:28:04 <RazaN> +0
14:28:06 <eBremer> +0
14:28:11 <pchampin> -1
14:28:33 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-resumable-large-data-transfers Resumable Large Data Transfers
14:28:33 <gibsonf1> STRAWPOLL: Resumable Large Data Transfers
14:28:37 <gibsonf1> +1
14:28:37 <eBremer> +1
14:28:37 <bendm> -0
14:28:38 <ryey> +1
14:28:40 <pchampin> +0
14:28:44 <acoburn> +0
14:28:48 <bartb> -1
14:28:48 <laurens> +0
14:29:18 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-resource-versioning Resource Versioning
14:29:18 <gibsonf1> STRAWPOLL: Resource Versioning
14:29:21 <gibsonf1> +1
14:29:23 <RazaN> +1
14:29:26 <pchampin> +0
14:29:27 <eBremer> +0
14:29:31 <dmitriz> +0.5 (hooks/affordance)
14:29:31 <acoburn> -1 (memento already does this)
14:29:31 <bartb> +0
14:29:33 <bendm> -1
14:29:48 <laurens> -1
14:29:54 <ryey> -1 (good to have hooks; but not as a whole)
14:30:06 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-subscribing-to-resource-changes-notifications Subscribing to resource changes
14:30:07 <gibsonf1> STRAWPOLL: Subscribing to Resource Changes
14:30:12 <gibsonf1> +1
14:30:12 <pchampin> +1
14:30:16 <ryey> +1
14:30:17 <bartb> +1
14:30:17 <bendm> +1
14:30:17 <RazaN> +1
14:30:18 <laurens> +1
14:30:24 <eBremer> +0
14:30:25 <dmitriz> +1
14:30:31 <acoburn> +1
14:30:47 <laurens> q?
14:30:48 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-access-request-handling Access Request Handling
14:30:49 <gibsonf1> STRAWPOLL: Access Request Handling
14:30:50 <gibsonf1> +1
14:30:51 <eBremer> +1
14:30:57 <acoburn> +1
14:30:57 <RazaN> +1
14:31:01 <dmitriz> +0
14:31:03 <bendm> +0.5
14:31:06 <bartb> +0
14:31:07 <ryey> +0
14:31:09 <pchampin> +0.5
14:31:11 <laurens> +1
14:31:26 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-delegation-of-access-rights Delegation of Access Rights
14:31:26 <gibsonf1> STRAWPOLL: Delegation of Access Rights
14:31:29 <gibsonf1> +0
14:31:39 <eBremer> +1
14:31:42 <acoburn> +1
14:31:45 <dmitriz> +1 (though this is a repeat of earlier items)
14:31:46 <bartb> +1
14:31:52 <pchampin> +1
14:31:53 <ryey> +0
14:31:54 <RazaN> +1
14:32:02 <laurens> +1
14:32:16 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-contextual-access-control Contextual Access Control
14:32:17 <gibsonf1> STRAWPOLL: Contextual Access Control
14:32:19 <eBremer> -1
14:32:20 <gibsonf1> q+
14:32:29 <dmitriz> +1
14:32:34 <laurens> ack gibsonf1
14:33:26 <bendm> -0 (dynamic group access affordance might be sufficient for now)
14:33:27 <pchampin> ack g
14:33:41 <gibsonf1> +1
14:33:52 <acoburn> +1
14:33:52 <ryey> +1
14:33:57 <laurens>   -1
14:34:01 <bartb> +0
14:34:08 <RazaN> +1
14:34:19 <pchampin> +0
14:34:27 <gibsonf1> STRAWPOLL: Inbox (notifications)
14:34:31 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-inbox-notifications Inbox Notifications
14:34:32 <gibsonf1> +1
14:34:35 <acoburn> +0
14:34:41 <bendm> -1
14:34:43 <eBremer> +0
14:34:45 <bartb> -1
14:34:50 <laurens> -1
14:34:51 <dmitriz> -1 (seems like duplicating ActivityPub)
14:35:02 <ryey> +0.5 (either this, or some similar mechanisms)
14:35:09 <pchampin> +0.5
14:35:21 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-search-and-query Search and Query
14:35:21 <gibsonf1> STRAWPOLL: Search and Query
14:35:22 <gibsonf1> +1
14:35:28 <dmitriz> +1
14:35:33 <pchampin> +0
14:35:33 <bartb> +1
14:35:35 <acoburn> +1 (but we will need to scope this carefully)
14:35:37 <bendm> +0
14:35:48 <eBremer> +1 (agree with acoburn)
14:35:48 <ryey> +1 (needs more scoping, but yes in general)
14:35:55 <laurens> +0.5 (this could be very complex if not scoped well)
14:36:10 <RazaN> +1
14:36:12 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-self-descriptive-and-discoverable-apis Self-descriptive APIs
14:36:13 <gibsonf1> STRAWPOLL: Self-Descriptive and Discoverable APIs
14:36:16 <laurens> +1
14:36:16 <eBremer> +1
14:36:17 <bendm> +1
14:36:17 <gibsonf1> +1
14:36:18 <ryey> +1
14:36:23 <acoburn> +1
14:36:25 <dmitriz> -1
14:36:25 <bartb> +1
14:36:32 <RazaN> +1
14:36:44 <pchampin> +1
14:36:54 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-end-to-end-encryption-0 End-to-End Encryption
14:36:57 <gibsonf1> STRAWPOLL: End-to-end Encryption
14:37:00 <dmitriz> +1
14:37:01 <gibsonf1> +1
14:37:15 <bendm> -1
14:37:20 <bartb> +0
14:37:27 <ryey> +0 (too many details to consider; doesn't have to be server spec if proven difficult)
14:37:28 <acoburn> +0 (really important but not a core requirement)
14:37:28 <uvdsl> -1
14:37:36 <eBremer> +0
14:37:36 <pchampin> +0
14:37:37 <laurens> -1
14:37:43 <RazaN> +1
14:37:45 <ryey> s/doesn't have to be server spec if proven difficult/doesn't have to be core spec if proven difficult
14:38:00 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-data-integrity-verification Data Integrity Verification
14:38:01 <gibsonf1> STRAWPOLL: Data Integrity Verification
14:38:01 <dmitriz> the problem is, E2EE _affects_ the core spec
14:38:03 <gibsonf1> +1
14:38:24 <laurens> -1
14:38:25 <dmitriz> +1
14:38:29 <bendm> q+
14:38:30 <pchampin> +0
14:38:35 <ryey> q+
14:38:36 <bartb> +0
14:38:42 <RazaN> +1
14:38:49 <eBremer> +0 (perhaps digest headers minimally)
14:38:54 <laurens> q?
14:38:56 <laurens> ack bendm
14:39:04 <acoburn> +0 (Important but possibly handled by existing IETF specs)
14:39:14 <dmitriz> q+
14:39:22 <gibsonf1> bendm: more info on key management Dimitry please?
14:40:32 <gibsonf1> dmitriz: Pattern with Storage projects is leave out of scope because its hard, but need affordance for it in core spec so its not impossible down the road.
14:41:20 <laurens> q?
14:41:21 <gibsonf1> ... a flexible affordance like auxiliary resources  (read about encrypted data vaults) to keep in mind whats involved
14:41:26 <laurens> ack ryey
14:42:07 <eBremer> Encrypted Data Vaults : https://identity.foundation/edv-spec/
14:42:44 <gibsonf1> ryey: I see 2 interpretations:  1.  Verify data retrieved is same as one in storage (data transfer is correct), or 2. Verify data stored in storage is same as data originally stored in storage.  Which one?
14:43:32 <eBremer> Digest Fields (Headers): https://www.rfc-editor.org/rfc/rfc9530
14:44:24 <gibsonf1> acoburn: I think existing IETF specs around digest header which allows read and  write verification - using a checksum.  On read client can verify checksum matches server checksum for resource
14:45:42 <dmitriz> this is fairly easily solved by including the digest hash in the original URL, and passing to Charlie
14:46:00 <gibsonf1> ryey:  That answers 1, but for 2. - can I get a proof of this.  Alice stores data in Bob's storage, Charlie reads that data, Charlie needs proof that data was originally stored and is same as put in by Alice
14:47:19 <gibsonf1> ryey: Voting to include or make new invention on this?
14:47:50 <pchampin> q+
14:48:11 <gibsonf1> laurens: Its to incorporate existing work or not in the LWS spec, not new inventions
14:48:15 <laurens> ack dmitriz
14:48:25 <dmitriz> q-
14:48:27 <laurens> ack pchampin
14:49:19 <gibsonf1> pchampin: +1 is to require a requirement in LWS, not necessarily something new.  Providing affordances to make possible = +0
14:50:05 <gibsonf1> laurens:  It might be in the wording of requirement causing interpretation issues
14:50:32 <gibsonf1> pchampin: The work required by implentors is another dimension
14:50:35 <laurens> q?
14:50:46 <ryey> +1
14:50:46 <acoburn> ->  https://w3c.github.io/lws-ucs/spec/#dfn-consent-based-data-sharing Consent-based data sharing
14:50:48 <gibsonf1> STRAWPOLL: Consent-Based Data Sharing
14:50:49 <bendm> I was doing the same as pchampin
14:50:52 <acoburn> +1
14:51:02 <laurens> -1
14:51:03 <bartb> +1
14:51:06 <bendm> +0
14:51:08 <dmitriz> +0.5 (I suspect this is a layer above LWS, application-level)
14:51:08 <eBremer> +0
14:51:15 <gibsonf1> +1
14:51:16 <RazaN> +1
14:51:19 <pchampin> +0
14:51:36 <ryey> -0 (not necessarily, as consent can be a complicated legal thing; do in application.)
14:51:43 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-legal-basis-enforcement Legal Basis Enforcement
14:51:44 <gibsonf1> STRAWPOLL: Legal Basis Enforcement
14:51:47 <laurens> -1
14:51:49 <eBremer> -1
14:51:54 <bartb> -1
14:51:56 <dmitriz> -1
14:51:56 <gibsonf1> -1
14:51:56 <RazaN> -1
14:51:58 <ryey> -0 (similar to above)
14:52:05 <acoburn> -1 (Important implementation consideration, but out of scope for the spec)
14:52:05 <bendm> -1 (this kind of all depends on whether we do audit trail)
14:52:13 <pchampin> -1
14:52:30 <gibsonf1> STRAWPOLL: Authentication Mechanisms
14:52:31 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-authentication-mechanisms Authentication Mechanisms
14:52:32 <eBremer> +1
14:52:36 <acoburn> +1
14:52:37 <ryey> q+
14:52:38 <gibsonf1> +1
14:52:40 <laurens> +1
14:52:41 <bartb> +1
14:52:48 <dmitriz> +1
14:52:48 <pchampin> +1
14:52:54 <laurens> ack ryey
14:53:22 <gibsonf1> ryey: I would vote +1 but not sure exact requirement
14:53:23 <bendm> +1
14:53:53 <ryey> +1
14:53:56 <gibsonf1> acoburn:  Actual text in requirement we can debate and decide and scope - whether self-soverign is part we can all agree later
14:54:20 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-trusted-identity-providers Trusted Identity Providers
14:54:21 <gibsonf1> STRAWPOLL: Trusted Identity Providers
14:54:24 <acoburn> +0
14:54:24 <gibsonf1> +1
14:54:30 <bartb> +0
14:54:35 <eBremer> +0
14:54:36 <RazaN> +0
14:54:42 <bendm> +0 (we should enable, but not work on that imo)
14:54:52 <pchampin> +1
14:54:57 <ryey> +0.5 ("transitive" part may need further thoughts, but it should be included)
14:55:00 <laurens> +0
14:55:04 <acoburn> -> https://w3c.github.io/lws-ucs/spec/#dfn-loose-coupling-of-underlying-protocols Loose Coupling of Underlying Protocols
14:55:04 <gibsonf1> STRAWPOLL: Loose Coupling of Underlying Protocols
14:55:21 <dmitriz> +1 (seems reasonable)
14:55:22 <ryey> +1
14:55:24 <laurens> -1
14:55:31 <gibsonf1> +0
14:55:32 <pchampin> +0
14:55:34 <RazaN> +1
14:55:38 <acoburn> -1
14:55:39 <bartb> -1
14:55:42 <eBremer> +0
14:55:44 <bendm> +0.5 (to see which we can focus on)
14:56:31 <gibsonf1> acoburn: That as far as we can get to today - pretty far.  A lot of good material for establishing focus.
14:56:37 <laurens> zakim, open agendum 4
14:56:37 <Zakim> agendum 4 -- Face-to-face meeting agenda -- taken up [from agendabot]
14:57:42 <gibsonf1> laurens: Call to action to everyone on how to approach f2f meeting.  WHere do we see disagreements etc, lets include this again next week.  LWS mailing list - please confirm attendance W3C calendar
14:58:10 <pchampin> RRSAgent, make minutes
14:58:11 <RRSAgent> I have made the request to generate https://www.w3.org/2025/09/15-lws-minutes.html pchampin
14:59:09 <acoburn> acoburn has left #lws