From 4ceab2c47d93ce0f47e4a63f81d9739047ccca28 Mon Sep 17 00:00:00 2001 From: Christoph Braun Date: Wed, 10 Jun 2026 17:30:32 +0200 Subject: [PATCH] create 2026-06-10.md --- meetings/2026-06-10.md | 129 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 meetings/2026-06-10.md diff --git a/meetings/2026-06-10.md b/meetings/2026-06-10.md new file mode 100644 index 00000000..f7c78d74 --- /dev/null +++ b/meetings/2026-06-10.md @@ -0,0 +1,129 @@ +# W3C Solid Community Group: Weekly + +* Date: 2026-06-10T14: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) +* [Paul Worrall](https://interition.ai) +* [Rui Zhao](https://me.ryey.icu) +* [Luke Dary](https://w3c.social/@lukedary) (late) + +## Regrets + +* + +--- + +## Scribe +* + + +### 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 + +* Trip Report - Concienc.ia Hackathon (Roberto, elf-Pavlik): + * https://hackathon.youngaileaders.info/#/ + * ODI (Roberto,Matthieu) and eP gave a session (keynote) on Solid for the hackthon participants + * Most of the hackathon teams did not actually use Solid (because they only had 4hs of coding) but the 4 finalists had Solid in the diagrams, communication continues + * Also communication between the ODI and the digital ministry of the City of Mexico + * Good conncetion established: https://futurociudades.tec.mx/es + + +## Topics + +### The European Social Stack +- Solid involvment in https://european.social/ +- AB: I saw that, some members asked if that would be interesting to Solid CG, given the current development in the EU. +- ... would be interested to see if anyone else is interested or if ODI is interested in participating there? +- JW: Who asked if Solid / Solid CG would be interested in participating in the EU Social Stack. +- eP: https://matrix.to/#/!ywIfjdAsxMggBTEMtI:matrix.org/$eKOrXxdWie_O8UOYYZTRB8C53Wia3u6237Bhr0z7b-s?via=matrix.org&via=gitter.im&via=society.waag.org +- CB: It looks interesting, I didn't read too deep into it. I don't know if there is any more additional material attached. It looks like a mission statement. Rather than a technical stack (in the stack sense). +- eP: I like the idea because it is broader than just one project. I'd like to participate to not be caught in a bubble. +- CG: Does ODI know about this? +- JW: Not that I know of. RB could engage with Damon and come back to the CG. +- eP: It woudl be good to keep track on those actions. +- CB: I don't know if it is worth keeping track on that. If people actually follow through on that they can report back. It is not a spec thing. If Roberto has time that would be great. I don't see it as technical to the CG. +- eP: I think we should keep it somewhere. Maybe office hour next week? +- JW: Keep it simple, maybe? ODI (internally) is trying to track a bunch of things, ongoing work. +- RB: I will look into EU Social Stack. I would like to make sure that if we engage in such a project, it is worth the effort. +- eP: Maybe look also for some low hanging fruit that we could get into. Eg. basic social profiles working across. +- RB: It might also be a question, how the Solid project engages with other projects. So, not just particular to this other project. + +### TPAC Session for Solid CG +- https://www.w3.org/events/tpac/2026/tpac-2026/ + +- CB: Jesse you had action last week to send out email. +- JW: Will get that out today. +- ...: Should we also do an LWS/Solid session? Could write an email to solid and lws email lists + +### Demo: Agentic Skills for Claude on Solid + +- JW: leading up to the hackathon, I pulled together some agentic skills for claude on solid +- ...: also, around that time, IBM release a tool called "Bob", an extension for VS code. +- ...: So, I came up with a very opinionated set of skills (that is why they live in my namespace): https://github.com/jeswr/solid-ai-coding +- ... opinionated on how to build Solid: picks a particular stack of libraries (see [AGENTS.md](https://github.com/jeswr/solid-ai-coding/blob/main/AGENTS.md)) +- ... one of the apps that I have built with the skills is https://github.com/jeswr/solid-issues - it was built from 3 instructions in claude code (mix of Opus 4.8 and Fable) "install https://github.com/jeswr/solid-ai-coding/," "create an issue tracking application, " and "/goal keep iterating on the app until it has feature parity with similar tools such as Jira and Monday.com do not stop until it has feature parity and the same level of quality as those applications" +- eP: IBM Bob YT https://www.youtube.com/@ibm-bob +- JW: .... Questions? +- eP: is there a way to use well-known? +- https://likec4.dev/tooling/ai-tools/#install-into-any-project +- eP: I dont think we should have an official set of skills for Solid +- ... it might be good have different flavours of skill sets (ODI,LDO,...) +- ... also, now we have yet another authentication library +- ... maybe we should have a group to join forces? +- ... if I was a new developer, then I had no idea what to use or the tradeoffs +- PW: Thanks, Jesse - I liked the demo. I played around with that also alot. The interesting thing to me really is sharing data between agents. I completely ditched UI in favour of voice. I wonder what your take is on sharing data in this context. +- JW: I don't manually write these skills - rather, Claude takes my codebases and extracts what I do into skills. So, there were some notions of how I do data sharing in my apps but there is no particular approach to recommend. +- PW: How did it do with data schemas? I found it to be quite good at re-using what is already out there. +- JW: Yes, it was asked to try to re-use what is out there in the Solid Ecosystem already. +- CB: Really interesting, I think it's great that there is another authn library. Why new one was created, was there a particular pain, what it solves that other libs don't. +- JW: First is related to underlying lib, oauth for web. It has formal security certification, state of the art library, handles dpop etc. In order to do DPoP this is code to do it (showing screen). You have a lot of methods to reuse. Avoids hand rolling a lot of your own authn code. It is certified which should make it more secure, less bugs. It has 1k stars and is sponsored by Okta. +- ...: Second reason is related to the design style. The principle is that if application has concept of session. There isn't concept of single session with resource server. You may do that with AuthZ token issued by oidc provider. You can do it with tokens issued by multiple providers. Samu has been working with Auth for over a decade. Devs shouldn't think about session as an abstraction. One can have fetch function, either patched or service worker which intercepts the call. Then have series of callbacks to figure out how to authenticate. +- eP: https://www.youtube.com/watch?v=IXzdH1JqcOA&list=PLXBho_YohPB09B_ecOsABoI8Dc67v1H4O&index=1 +- eP: https://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SWAT0 + + +### PR: Add Issuer Trust to Security Considerations (Solid-OIDC) +- https://github.com/solid/solid-oidc/pull/254 + +### Discussion: How to make Solid easier for new devs + +## Actions +- RB to look into the EU Social Stack +- JW to write an email to the Fediverse Groups - deadline June 17th for session proposal +- JW to write an email to LWS and Solid groups - deadline June 17th for + +## Decisions + +## Links + + + + +