Merge pull request #766 from solid/meetings/2026-03-04

add meeting minutes

Author: uvdsl

meetings/2026-03-04.md

@@ -0,0 +1,171 @@
+# W3C Solid Community Group: Weekly
+
+* Date: 2026-03-04T14:00:00Z
+* Call: https://meet.jit.si/solid-cg
+* Repository: https://github.com/solid/specification
+
+## Chair
+
+* Christoph Braun - [uvdsl](https://github.com/uvdsl)
+
+## Present
+
+* [elf Pavlik](https://elf-pavlik.hackers4peace.net)
+* Theo [@thhck](https://github.com/thhck)
+* [Luke Dary](https://w3c.social/@lukedary)
+* [Matthias Evering](https://solidweb.me/testpro/)
+* [Roberto S.K. Breitman](https://github.com/Roberto-Breitman)
+* James Radley
+* Alain Bourgeois
+* [Samu Lang](https://github.com/langsamu)
+* [Jesse Wright](https://jeswr.org/)
+* [Jacqueline Boltik](https://github.com/jboltik)
+* [Precious Oritsedere](https://github.com/PreciousOritsedere)
+* [Ted Thibodeau Jr](https://www.linkedin.com/in/macted/) (he/him) (OpenLinkSw.com) // GitHub:[@TallTed](https://github.com/TallTed) // Mastodon:[@TallTed](https://mastodon.social/@TallTed)
+* [Rui Zhao](https://me.ryey.icu)
+* [Paul Worrall](https://interition.ai)
+
+## Regrets
+
+* 
+
+---
+
+## Scribe
+
+* Theo [@thhck](https://github.com/thhck)
+
+## Announcements
+
+### Meeting Guidelines
+
+* [W3C Solid Community Group Calendar](https://www.w3.org/groups/cg/solid/calendar).
+* [W3C Solid Community Group Meeting Guidelines](https://github.com/w3c-cg/solid/blob/main/meetings/README.md).
+* No audio or video recording, or automated transcripts without consent. Meetings are transcribed and made public. If consent is withheld by anyone, recording/retention must not occur.
+* Join queue to talk.
+* Topics can be proposed at the bottom of the agenda to be discussed as time allows. Make it known if a topic is urgent or cannot be postponed.
+
+### Participation and Code of Conduct
+* [Join the W3C Solid Community Group](https://www.w3.org/community/solid/join), [W3C Account Request](http://www.w3.org/accounts/request), [W3C Community Contributor License Agreement](https://www.w3.org/community/about/agreements/cla/)
+* [Solid Code of Conduct](https://github.com/solid/process/blob/main/code-of-conduct.md), [Positive Work Environment at W3C: Code of Conduct](https://www.w3.org/policies/code-of-conduct/)
+* Operating principle for effective participation is to allow access across disabilities, across country borders, and across time. Feedback on tooling and meeting timing is welcome.
+* If this is your first time, welcome! Please introduce yourself.
+
+---
+
+
+## Introductions
+
+ Jacqueline Boltik: integrate Solid into software to scrape online content and send content over email , here mostly just to learn 
+
+## Topics
+
+
+### Actions Review
+
+* eP ✅ invite Aaron for next meeting / async comment 
+* eP: done, pull request has been merge [which one ?]
+* CB: saw comment PR from Aaron, will do later
+
+### Solid-OIDC — add Christoph Braun to editors 
+https://github.com/solid/solid-oidc/pull/247
+
+* eP: suggest we should just merge it, unless someone object ( add CB has editor and Dimitri as former editor)
+* ( no objection from the room )
+* eP: need an aproval to merge it
+* JW: will make CB an editor so he can approve it
+
+
+
+### feat: add client credentials as a MUST
+https://github.com/solid/solid-oidc/pull/245
+* JW: Should add Samu as an editor too ? 
+* [...]
+* eP: to Samu : an strat ? 
+* Samu: will find the less contention solution possible
+* eP: 2026 roadmap: what should we publish ? should not do it last day 
+* JW: Should not use this call to work on the Solid-OIDC current situtation
+* CB: we have a demo from luke today, lets do the demo first, and if time left, let's discuss solid-oidc 
+
+### Luke demo 
+
+* Luke Dary: paa.pub goal is to deploy a cloudflare individual pod + activity pub solution
+* can log in with passkey and FedCM
+* very open to PR
+* basic editor profile, can add tripple easily
+* function to hack you own profile, a la myspace/geocity 
+* App permission feature, to update them
+* federation with AP works, can sends and receive follow
+
+#### Questions:
+
+ * eP: are you aware of solid test suite? did you use it? 
+ * LD:  most of the app is vibe coded, melvin did some tests. If I get a link to the tests suite would be happy to tests it
+ * chat: JW: For those vibe coding: we are starting to chuck some claude skills for Solid together in 
+https://github.com/solid/solid-llm-skills
+ * eP: can talk about tooling  next week after the meeting
+ * Alain Bourgeois: Got some issue fetching content ( got 404 )
+ * LD: some part vibe coded, some feature not implemented yet
+ * CB: if you think container is not a word very understandable for most, you (LD) can use "folder"
+ * LD: good point, the idea is to make it accessible to anyone
+ * eP: on naming, ppl should be able to use any naming they want, it important to keep in minds its important to have localisation and language
+ * AB: are you using ACP ?
+ * LD: had issue with changing permission and the external html profile stoped working. Because if permssion where too strict it didn't worked. To make some stuff accessible external, could not use ACP. I had issue with granularity. Now I have used permission, I can give feedback on it.
+  * eP: would love to have all those feedback you have from implementing this. Please keep you notes, its great resource for the community. 
+  * CB: perhaps create issue or discution for each feedback so we can reference them 
+
+### 2026 CG Roadmap (15+ min) ( next)
+
+* CB: https://github.com/w3c-cg/solid/issues/54
+* CB: I expect a lot of those work item being present at Solid Symposium 
+* JW: seems to have academic work being done on discovery, but not shared on the CG
+* CB: will like to draft a ruff spec, and there is a poster for the symposium 
+[...]
+* JW: Oli should be there at Solid Symposium 
+
+
+
+### Solid 2026 best practise documents ( next)
+
+* eP: we may want to review list of drafts and people compiled in Jan https://github.com/solid/specification/blob/main/meetings/2026-01-28.md#2026-odi-roadmap
+* eP: a list of item we can contribute, most of them assigned to ODI, wanted to check progress
+* JW: want to share and get feedback/PR
+* would like to have a consensus from CG on it
+* eP: would be nice to see the document and discuss them after
+* Rui: +1, can we get a link to the document ? 
+* CB: +1
+* JW: would add some text and share it later
+
+### WAC PR - Add Support for Client Identification and Issuer Identification ( NEXT WEEK )
+https://github.com/solid/web-access-control-spec/pull/133
+
+* eP: if Solid 26 includes WAC there will not be even basic App AuthZ unless this PR lands
+* CB: Would like to defer it to next week , in favor of taling of Solid-OIDC
+
+
+### Discussion of Solid-OIDC w.r.t. Solid'26
+
+
+
+CSS still implements 0.0.3 (not actually a version, this is what the core spec was approximately at when the snapshot was taken) where there is no snapshot,
+i.e. global DPoP-bound access token
+
+In 0.1 we use an Id token which is being exchanged with the resource server's AS for an access token. Relationship between AuthZ server and resource server is largely undefined by the current spec.
+
+ESS might implement 0.1 - we don't know
+Java client implements 0.1 - we think
+Javascript libraries (both Inrupts and Christophs) implement 0.0.3
+
+CB: It is severly underspecified how UMA would work with a Solid storage. As compared to rest of the Solid specs where it is extremely well defined what must be done. With UMA spec it just says "apply this to your Solid implementation and you figure out the details". This breaks the philosophy of the Solid specifications which are extremely strict in what they require.
+eP: We don't have much feedback on 0.1. Possible feedback is Wout's UMA work & Inrupt ESS.
+
+Notes to put with 0.0.3:
+ - We know we shouldn't be using global access tokens (OAuth intention)
+ - We will be adding AS as distinct server role
+ - The client should treat access token as Opaque
+ - Check if all implementations have an ID token
+
+## Actions
+
+( LD to create issue/discussion on his implementation feedback ? ( not sure if Action ))
+