Create 2026-09-16.md

meetings/2026-09-16.md

@@ -0,0 +1,165 @@
+# W3C Solid Community Group: Weekly
+
+* Date: 2026-09-16T14:00:00Z
+* Call: https://meet.jit.si/solid-cg
+* Repository: https://github.com/solid/specification
+
+## Chair
+
+* [elf Pavlik](https://elf-pavlik.hackers4peace.net)
+
+## Present
+
+* Theo - @thhck
+* [Luke Dary](https://w3.social/@lukedary)
+* [Jesse Wright](https://jeswr.org/#me)
+* Alain Bourgeois
+* Roberto
+* Ross
+
+### Regrets
+
+* 
+
+## Scribe
+
+* Theo - @thhck
+
+---
+
+### 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
+
+### W3C Community Survey 2026
+URL: https://www.surveymonkey.com/r/FFGP6DL
+* eP: Yearly survey, takes 5min. Please consider contributing.
+
+
+
+### Mini-Workshop @ TPAC2026: Data Governance & Ownership
+https://github.com/w3c/strategy/issues/567
+
+* eP: please boost! https://w3c.social/@p20n/117257233743358870
+
+
+### OS Tools meeting - after this meeting!
+https://www.w3.org/events/meetings/ca82e473-771c-4484-ba60-ebf9a0ecbe1b/
+https://lists.w3.org/Archives/Public/public-solid/2026Sep/0003.html
+eP: Today's focus will be CSS.
+
+## Actions Review 
+
+
+## Topics
+
+### Demos
+
+#### Add Public Keys section
+
+URL: https://github.com/solid/webid-profile/pull/130
+
+* SC: ~~demo (for 10-15 minutes)~~
+* SC: Postpone topic to 2026-10-07 meeting
+
+#### Non-repudiation in Solid
+URL: https://github.com/biagioboi/DKGNonRepudiation
+
+* RH/BB: ~~Demo by Biagio / Ross~~
+* RH/BB:  Postponed to next week. 
+
+
+### TPAC Session for Solid CG
+
+https://github.com/w3c-cg/solid/issues/84
+https://github.com/w3c/tpac2026-meetings/issues/62
+https://www.w3.org/calendar/tpac2026/grid/
+
+* eP: Please keep in mind registration fee, including on-line participations. [Fee waivers available](https://www.w3.org/news-events/tpac/2026/registration/#registration-fee-waiver)
+* eP: no reply, so inferring that there is no interest from the group. My calculation is that nothing will happen. 
+* JW: if something spontaneous happens, that's great. Otherwise, it is no big deal.
+* eP: Who has registered yet ?
+* *none yet*
+
+#### Registered for remote
+
+* elf Pavlik
+
+#### Registered for in-person
+
+
+### CSS component that prefents making WebID unusable with the server it is hosted on
+URL: https://github.com/CommunitySolidServer/CommunitySolidServer/issues/2239
+
+* AB: it is a CSS component added to Jesse's CSS version hosted at solidcommunity.net ( based on Pivot)
+* ...: *loggin in to SC.net*
+* ...: *browsing SC.net with solidOs, clicking the delete button on the profile/card and nothing happen*
+* AB: *editing the profile/card , the `solid:oidcIssuer` tripple and gets an error*
+* eP: *wants to try from terminal to see HTTP requests.*
+* AB: *setting the profile/card publicly writtable so possible to test DELETE without loggin*
+* eP: *getting 401 on DELETE* this is weird, why 401 if publicly writtable ?
+* eP: *getting an error with PUT*
+* AB: weird, it's regular CSS, I haven't touched the PUT and DELETE methods. 
+* Th: [...]
+* JW: Since the PR was made with an AI agent, I propose to give the agent a matrix of all the CRUD methods tested against the CSS + component and compare it to what the response should have been according to the Solid spec. 
+* AB, Jesse: [... something about solid:oidcIssuer has a protected tipple.]
+* eP: according to Protocol webId Idp, storage are highly decoupled and can be stored at different places. 
+* JW: What you are describing is more a power-user use case. This PR target non-power-user to not delete their WebID. I believe what you are describing is a bit of an edge case that is out of scope here. 
+* AB: I want to protect user from breaking their solid account.
+* eP: I think this PR is improvement. Help users locking themself out of their own account. AB, there should be at least one `solid:oidcIssuer` in the WebID ?
+* AB: no, it should be the one of the account ( same host for IdP and WbId)
+* eP: seems like a reasonable gard to have . 
+* AB: in NSS it was impossible to delete profile. This component is easily removable since doesn't write anything in the Pod
+* eP: SC.net runned by ODI, what are trying to get from today's meeting ? 
+* AB: ODI is in charge, but it is a community server, so we have a regard on it. 
+* Th: If I want to make more complex use case, is it still possible?
+* AB: yes still possible, you can add as many issuer as you want.
+* AB: *proving it through the demo*
+* eP: plz if someone has a concern, raise it now so it can be added as feedback, otherwise I believe is a great add-on to SC.net
+* AB: wanted to raise and address this security issue about having user that can delete their own account. Open to other solution to resolve that. 
+* eP: security issue like https://github.com/elf-pavlik/mallory#cuckoo is still there
+* AB: cuckoo should be resolved by the ACL
+* eP: if user logs into cuckoo it will be able to add malicious issuer
+* eP: in my understanding SC.net decisions are not made here, but we can use the minute to show that no one here have a problem with your approach.
+
+### Extend minutes review time to one week
+https://github.com/w3c-cg/solid/pull/86
+
+* eP: chair could merge last week minutes during the first few minutes where people are still joining
+* Th: is there a difference between first PR and edit. We make a PR with current notes in next day or two days. Preferably, right after the meeting.
+* eP: PR should be the same day but we just add  more time. Some CG participants didn't know it's possible to have a markdown preview in GitHub, so historically CG participants wanted to have a quick MD preview. 
+
+### Ross: WAC 2 standard
+
+* RH: [... missed the begining ] From someone looking the spec, ACL client seems secondary but should be primary. Relatively small thing but would like people thoughts on this.
+* eP: Melvin did a fork of WAC that --from what I remember-- would prevent server from accepting policies which server can't enforce.
+[...missing a few sentences]
+* eP: Ross you should add this to the agenda another day
+* Jesse: it seems that there is a patch to WAC, the process should be that Ross should make a PR and we discuss it first.
+
+
+
+## Actions 
+
+Th: to handle PR 86
+
+## Decisions
+