Merge pull request #796 from solid/thhck-patch-1

Create 2026-06-24.md

Author: elf-pavlik

meetings/2026-06-24.md

@@ -0,0 +1,127 @@
+# W3C Solid Community Group: Weekly
+
+* Date: 2026-06-24T14:00:00Z
+* Call: https://meet.jit.si/solid-cg
+* Repository: https://github.com/solid/specification
+
+## Chair
+
+* Theo - @thhck
+
+## Present
+
+* Christoph Braun - [uvdsl](https://github.com/uvdsl)
+* [elf Pavlik](https://elf-pavlik.hackers4peace.net)
+* [Paul Worrall](https://interition.ai)
+* [Jesse Wright](https://jeswr.org/#me)
+* [Erich Bremer](https://ebremer.com)
+* [Marc Haddle] marc.haddle@datasolids.com
+
+## Regrets
+
+* 
+
+---
+
+## Scribe
+
+* None - Theo will try to add some bullets
+
+
+### 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
+*
+
+
+## Announcements
+
+## Actions Review
+
+- RB to look into the EU Social Stack 
+  - some emails sent, keep updated
+- eP ✅ to share few bullet points with CG and discuss them next week 
+
+## Topics
+
+### TPAC Session for Solid CG
+https://www.w3.org/events/tpac/2026/tpac-2026/
+
+ - JW: will go
+ - eP: wait to see if travel can be financed
+ - th: will probably go too
+
+ - th: an session planed ? Jesse you joined FedID ?
+ - JW: ... effort to bring different Auth together..
+ - eP: SAI project end soon. Will end being chair end of the year too. After, I'll be focusing on larger scope than Solid, try to have more visibility between different project in the interop space ( indie web, fediverse etc..)
+
+
+
+### CG Update @ ODI-Solid AC
+
+https://github.com/w3c-cg/solid/issues/82
+
+ - eP: only Melvin added Topic. CB noted lack of coordination. 
+ - th: we have a lot of duplicate tools. 
+ - eP: we have a effort on Solid open source tooling, to make sure we don't do double work. We need someone to take leadership for this group that is dying. 
+ - JW: should the ODI facilitate this ?
+ - JW: suggestion: every two CG meeting, we have an extra 1h open source tooling meeting
+ - eP: open to bring it back on how it was, chairs are responsible to stop in time. who should take responsibility for the meeting ?
+ - RB: happy to help with the organisation and facilitation of it. but I'll be out in July . 
+ - JW: happy to fill the gaps in July 
+
+## Solid CG and LWS WG
+
+https://github.com/w3c-cg/solid/blob/main/principles.md
+https://github.com/w3c-cg/solid/blob/main/framework-for-proposals.md
+
+* eP: I started an email thread between Solid CG chairs, LWS WG chairs and W3C staff. We can start discussing some take aways.
+* ...: Some examples of what IMO may need further incubation:
+* ...: https://w3c.github.io/lws-protocol/lws10-searchindex/
+* ...: https://github.com/w3c/lws-protocol/pull/162
+* CB: What is this topic about specifically?
+* ... I'd like a clear scope of what is to be discussed.
+* eP: some participants may want to work on items that align with / build on currentl LWS drafts. one example would be auth where I started exploring something comparable to Solid-OIDC 0.1 https://github.com/elf-pavlik/lws-auth Myself I already plan to switch my deployment from WebID to CID, possibly keeping minimal WebID support while deprecating it.
+* ...: I will also look into aligning notifications, and consider aligning SAI or archiving it and buliding something with equivalent features on LWS access requests and access grants.
+* eP: To discuss general role of W3C CGs I would like to propose [W3C CG Program CG](https://www.w3.org/groups/cg/council/)
+
+* eP: Solid-CG can't publish W3C standard, contrary to the WG. 
+* ...: Solid-CG has a broader scope than LWS, Solid-CG supersets LWS scope. Is there something in scope of LWS that is not in scope of Solid ?
+  * CB: Modeling Consent ? 
+  * JW: [...] LWS on using ODRL ?
+* eP: Who that have a work item in the CG roadmap wants to also align with LWS spec ?
+* Paul: [... interested in conforming to LWS ]
+* th: yes but what is the diff ?
+* JW: CRUD has diff in how container are defined, webID discussed, using OIDC ( 3 different way, include SAML, DID key, )
+
+
+* eP: CG should be an incubation space, not the place to reach consensus, this is the role of the WG - see links under this agenda topic.
+* JW: the ODI should not decide what is the role of WG and CG. It should be defined between them, and preferably discussed in the AC too
+* JW: would like to edit two document through CG: 1. query in Solid, would like to standardise it. 2. WebAuthn to login to Solid IdP
+* eP: Current editor of the Solid Protocol spec: sarven mostly, timbl and [...] . So mostly Sarven today. 
+* ...: The spec I'm editing should be LWS compatible
+* JW: LWS has breaking change with Solid protocol
+
+
+## Actions 
+
+ - JW to make a map of the different w3c group ( for TPAC ? )
+ - Roberto to send invite for open-source tooling meeting to Muze, inrupt, Samu ... and more
+ 
+## Decisions
+
+ - every two week open-source tooling start again, facilitated by RB ( JW for July ) starting in two weeks ( 8  July ), first subject: OIDC client