From 6b17ae037579a262497c94a31d166f0f370cd607 Mon Sep 17 00:00:00 2001 From: elf Pavlik Date: Wed, 26 Aug 2026 14:30:06 -0600 Subject: [PATCH] Create 2026-08-26.md --- meetings/2026-08-26.md | 151 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 meetings/2026-08-26.md diff --git a/meetings/2026-08-26.md b/meetings/2026-08-26.md new file mode 100644 index 00000000..39d089f3 --- /dev/null +++ b/meetings/2026-08-26.md @@ -0,0 +1,151 @@ +# W3C Solid Community Group: Weekly + +* Date: 2026-08-26T14:00:00Z +* Call: https://meet.jit.si/solid-cg +* Repository: https://github.com/solid/specification + +## Chair + +* [elf Pavlik](https://elf-pavlik.hackers4peace.net) + +## Present + +* Alain Bourgeois +* [Luke Dary](https://w3c.social/@lukedary) +* [Jesse Wright](https://jeswr.org/#me) +* Paul Worrall +* Roberto S.K.B +* [Erich Bremer](https://ebremer.com) + +### Regrets + +* + +## 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 + + +## Announcements + +### OS Tools meeting - next weeek! +https://www.w3.org/groups/cg/solid/calendar/ + +* Offline first, Roberto is working on quorum +* Plan B from eP: SPARQL shenanigans +* Try to get announced in two days + +## Actions Review + +* eP posted to mailing list about survey results + +## Topics + +### Demos + +* Next week, eP show context switching +* PW, demo mid-September + +### Impressions from LinkML monthly meetings +https://linkml.io/ + +* eP: recording will be available at https://www.youtube.com/@LinkML-org/videos +* LD: is it producing lock in? even if it's not proprietary, I'm hesitant for syntaxt that are outside of standards. If it becomes less active one may be left with that problem. +* eP: encourage people to take a look + +### 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) + + +### ODI Solid Tooling Research - Summary Findings + +https://solidproject.solidcommunity.net/2026/Tooling%20research%20-%20summary%20findings.pdf + +* eP: Last week we commited to reading full results and discussing them this week +* eP: 18 responses with multiple years of Solid, so a little lacking on the "fresh blood" or getting to know Solid +* ...: wonder if people who are familiar imagine people coming to Solid, or were they speaking from their experience +* PW: What was the selection process? Maybe no others are using it, so the results reflect the population +* eP: maybe we need to look for different channels, to get a better representation +* PW: feels like issues from 2020, that have been there since then; finding out what is happening in the space. Key is the commercial pod provider issue. Seems as though the whole Solid ecosystem relies on the provision of Pods. +* ...: using AI hides a lot of the issues; the audience maybe isn't there to seek; the issues are good points for this group +* EB: interesting that AI agents do the coding; questions have changed, and the specification is critical so AI can adhere to it +* PW: pointing to the spec was how he started with agents making things, and hasn't really thought about it; tests are where agents aren't as trusted +* eP: testing client can come from a taskforce or LWS WG; how easy can you expect something to be? Maybe there are complexities that we can't avoid, and provide more guidance (primers, etc.) +* LD: From the adoption stand point, it's hard as a developer. Creating someone to create pod is very unlike what people are used to. When I explain flow feels very unlike the current norm. The knowledge transfer to both developer and end user is a channange. There is not a single place to create an account. The friction I get is from the nature of Solid itself. It would be good to direct them in a single place. +* eP: good point; potential improvements: custom domains, curated directory of providers; reduce the criteria, but it is a decision requiring responsible thought; switching cost should be minimized +* PW: can someone speak as the Solid 2026 relationship to these results +* RB: these results were wrapped into the efforts +* eP: results were delayed, so it doesn't necessarily represent the latest state, but we should track and address the issues brought up; if not, how do we prioritize? +* PW: confused on the efforts for Solid 2026 having an outcome on where priorities would be +* JW: there were release issues, but there is work being done on the ODI side to address the challenges; there is a packet on auth: https://github.com/solid-contrib/reactive-authentication +* ...: implements a design pattern that has been used by other long-term Solid practitioners; as far as object models, there is a wrapper package: https://github.com/rdfjs/wrapper +* ...: on ontology and schema discovery, there has been work, but it has gone quiet; could use efforts there or at least analysis of whether to continue +* ...: server consistency is as much a spec challenge versus a tooling issue; same for fragmentation; additional https://github.com/solid/object +* eP: spec, but also an issue with the status quo despite there being better solutions; LWS is a different situation because they have to publish a spec; lots of discussion between expectations between LWS and Solid and WG v. CG +* PW: just want something concrete; options are a detriment and a hindrance +* eP: my perspective, LWS for stability +* AB: LWS is not yet usable, solidcommunity.net needs to be improved; auth from SolidOS hasn't been ported; it disconnects often which needs to be looked at; issues in CSS that haven't been addressed; seems urgent to improve the running example, but maybe we're not putting enough investment into that +* JW: actively working on the issues against the community server and back to the codebase; there is a memory leak somewhere in the CSS code, which seems to be causing outages, but ODI is actively working on the code and will have updates later +* AB: there are already things that could be done and not in a few weeks; recent Cloudflare issues +* JW: encourage to post to support or forums; sounds like two issues: Inrupt client issues and Cloudflare issues +* eP: https://github.com/solid/odi-governance#solid-operations-advisory-group-formerly-solid-team +* JW: gone quiet as a group; tried to introduce complexity that proved to be hard to extend given the other channels of communication; RB let the members know +* eP: Plug for ODI office hours +* RB: can use the office hours for lots of things +* eP: OS Tools could be used for additional topics as well +* AB: new auth library available and ready to be implemented on solidcommunity.net +* eP: maybe use the office hours and see if that could be used to advance +* AB: Will be there +* JW: haven't deployed the latest mashlib update so there are hotfixes on the server that may be overridden +* Meeting closed but discussion continued afterwards about solidcommunity.net auth updates + +### SPARQL + +https://github.com/solid/specification/issues/804 + +* eP: Could we prioritize / extract endpoint discovery and build it on LWS Storage Description (CID)? +* ...: https://jeswr.github.io/solid-specs/specs/access-controlled-query/#discovery +* ...: Can we also have SHOULD HTTP QUERY - it's read only anyways + +### mashlib v2.3.3 with UVDSL + +* Alain: update of https://solidcommunity.net +* Cloudflare is a pain even on simple things like login + adding/editing a SolidOS meeting + +### Open PRs + +https://github.com/solid/specification/pulls + +* eP: we should do some cleanup + +## Actions + + +## Decisions + +