Skip to content

Create 2026-03-18.md #768

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
elf-pavlik merged 1 commit into from
Mar 21, 2026
Merged

Create 2026-03-18.md #768

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
159 changes: 159 additions & 0 deletions meetings/2026-03-18.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,159 @@
# W3C Solid Community Group: Weekly

* Date: 2026-03-18T14:00:00Z
* Call: https://meet.jit.si/solid-cg
* Repository: https://github.com/solid/specification

## Chair

* Theo @thhck

## Present

* [elf Pavlik](https://elf-pavlik.hackers4peace.net)
* Alain Bourgeois
* [Roberto S.K Breitman] (The ODI)
* [Luke Dary](https://w3c.social/@lukedary)
* [Precious Oritsedere](precious.oritsedere@theodi.org)
* [Michal](https://id.mrkvon.org)
* Jesse Wright
* Theo @thhck
* Marc Haddle
* Rui Zhao
* [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)


## Regrets

* Christoph

---

## Scribe

* Luke

### 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

* None needed

## Announcements


### ODI grant for test suite ( move to next week )
https://www.w3.org/2026/03/09-lws-minutes.html#a338
https://github.com/w3c/lws-protocol/issues/102

* JW: There is a grant from NLNet
* JW: That has been granted to ODI for a test suite.
* JW: That will be worked on.
* JW: Moved to next week
* JW: Samu will work on https://nlnet.nl/project/LinkedWebStorage-testsuite/
* JW: 1 of 8 grants that ODI submitted; first time grant recipients only allowed to accept a single grant
* JW: Will also include work on reference implementation of LWS
* JW: Discussion about the scope of the work ( should also include update on solid test suite )

## Topics


### Action review

- Deferred: ( report next week, CB not here..)
- WAC PR - Add Support for Client Identification and Issuer Identification
- WebID or WebID-Profile

### CG meeting during Solid Week on 29th April
https://www.w3.org/events/meetings/9d3965a2-f4a0-4346-8ca6-8eadee10051c/20260429T140000/

* eP: I propose to cancel this CG meeting and focus on Solid Week
* Objections: none raised

### WAC PR - Add Support for Client Identification and Issuer Identification

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
* eP: .. reporting to next week
* Alignment on spec is slowly emerging, but no implementation
* Rui: aware of the PR, but hasn't read it, when should this have consensus?
* eP: no deadline, but for Solid 26 there would be urgency
* jeswr: Solid 26 suggestion to create spreadsheet with server implementers and applications and WAC/ACP compatibility
* ..: message to CG about spreadsheet and that survey will help determine Solid 26, survey due next Friday: 27 March
* eP: would be nice to have tests for both to be able to validate (currently no ACP test suite)
* Rui: recalls a proposal about adding group access control into WAC
* eP: https://github.com/w3c/lws-protocol/pull/31


### 2026 CG Roadmap (15+ min)

* CB: https://github.com/w3c-cg/solid/issues/54
* CB: any updates?
* eP: suggest skip due to upcoming Solid Symposium ( let's talk about it after Symposium )


### Solid 2026 best practice documents

* eP: we may want to review list of drafts and people compiled in January 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
* JW: my current draft on the Solid 2026 document: https://docs.google.com/document/d/1da2J-NsU3K-4kWEFOvhzIdrvy_KftewXdlxfu401kY0/edit?tab=t.0
* JW: Walking through document
* FedID in Solid
* ODRL in Solid (requires changes to servers)
* eP: [PR to WAC](https://github.com/solid/web-access-control-spec/pull/133) convo drifted into Link Header topic as well
* RZ: significant server changes in handling ODRL
* eP: policy connected to access grants
* RZ: need to specify _who_ the policy is for
* JW: currently writing LWS Access Grants/Request using ODRL to have sufficient coverage
* eP: interest in LWS plans
* JW: LWS isn't defining a single, or any, access control language; most applications won't/shouldn't be managing access controls; most just need a consistent language to communicate access grants/requests
* JW: proposed "profiles", WAC/ACP statements, AC said, "No", ODRL was suggested and adopted for LWS Access Request/Grants proposal
* RZ: has question about using ODRL as the Access Request; ODRL is also working on Access Requests;
* https://github.com/w3c/odrl/issues/118
* https://github.com/w3c/odrl/pull/130
* RZ: (chat) Clarification: by "not using ODRL", I meant not using ODRL as is (i.e. ODRL 2.2 Core Vocabulary); these discussions are aimed at improving situations (esp. for a unified reasoner), and may be eventually considered part of a new ODRL version -- but until then, it's not official ODRL spec.


#### WebID or WebID-Profile

* eP: WebID-Profile isn't part of Solid Protocol 0.11. Does anyone know how much of it was implemented, and where?
* eP: AFAIK nothing implements, for example, 'protected triples' https://solid.github.io/webid-profile/#protected-properties
* eP: It seems to require WebID-Profile to be hosted on Solid Server while many WebIDs are hosted outside (for good reasons) https://solid.github.io/webid-profile/#Server
* eP: issues with profile, should use very minimal webid-spec
* JW: going to draft a much more minimal spec (OIDC issuer, PIM storage)
* eP: questions whether PIM storage should be required
* JW: Solid storage discoverable by PIM storage
* Michal: Others, who are not here, may have input they want to give on this

### Solid 2026 WebID discussion ( next week )

* eP: webId , extended profile, CID


## Actions
- Theo: tell peolpe about the canceled meeting
- Theo: set meeting to discuss IA scribing
- JW: list of Solid Servers on a spreadsheet to see who implements WAC vs ACP
- JW: will try to draft a on Solid-WebID and .. by next week so people have time to review


## Decisions

- Cancel CG meeting during Solid Week on 29th April