From 434deee0c5e8e911836766724de2078ee9324984 Mon Sep 17 00:00:00 2001 From: Th <133600193+thhck@users.noreply.github.com> Date: Wed, 27 May 2026 17:28:44 +0200 Subject: [PATCH] Create 2026-05-27 --- meetings/2026-05-27.md | 114 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) create mode 100644 meetings/2026-05-27.md diff --git a/meetings/2026-05-27.md b/meetings/2026-05-27.md new file mode 100644 index 00000000..3ee25ac1 --- /dev/null +++ b/meetings/2026-05-27.md @@ -0,0 +1,114 @@ +# W3C Solid Community Group: Weekly + +* Date: 2026-05-27T14:00:00Z +* Call: https://meet.jit.si/solid-cg +* Repository: https://github.com/solid/specification + +## Chair + +* Theo @thhck + +## Present + +* [Luke Dary](https://w3c.social/@lukedary) +* elf Pavlik +* Alain Bourgeois] +* Roberto S.K. Breitman, ODI +* Marc Haddle, Datasolids +* [Rui Zhao](https://me.ryey.icu) +* [Paul Worrall](https://interition.ai) +* [Jesse Wright](https://www.jeswr.org/#me) + +## Regrets + +* + +--- + +## Scribe + +* Legend + + +### 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 + +## Announcements +- SolidOS updated to v2.2.1 improved UI; following after meeting in London; WIP, most work done on profile + +## Topics + +### ODI Solid Demos and Use Cases +- Roberto: ODI keeping momentum from SoSy 26; gathering demos and use-cases +- [see matrix post](https://matrix.to/#/!ywIfjdAsxMggBTEMtI:matrix.org/$xf_pRb6jD9TwS1HWkaXoZNEa3ac1SyHfkKs0tyY4G2g?via=matrix.org&via=gitter.im&via=society.waag.org) +- eP: recommend keeping things in one place + +### Solid Hackathon +- Alain: have not seen hackathon results yet +- Roberto: discussing with winners to provide initial content for above demos and use-cases format; blocker is media rights at the moment +- Alain: small updates would be nice even before the full release +- Roberto: polishing of repo is still in progress +- eP: Callum tools? +- JW: Asked Roberto to follow-up with Callum + +### scope and relation between solid-CG and LWS +- eP: *garbled and cut out* CG and WG collaboration and alignment +- ..: Sent email to Ian to discuss relationship between LWS WG and Solid CG +- ..: Nothing to email list until chairs have a chance to discuss + +### Action review + + - eP to reach out to Jackson to set up time to talk about repository organization. + - ep: busy schedules, so will revisit for Open Source tools meeting + - Roberto: Help redefine scope of solid repo ( /solid /solid-contrib /odi ... ) as well as npm package + - still following up; getting advice; next step is to gather the stakeholders together in a meeting; 2-weeks+ + - eP: add roadmap to next week CG + + +### [Roadmap](https://github.com/w3c-cg/solid/issues/54) Review + +- eP: requesting people to post time dedication to items to estimate people working on it; would be good to have overview of capacity and work allocation +- Theo: test suite, hopefully finished soon. Talk next week on FedCM; ActivityPub after that +- eP: E2EE...lots of ideas, but we need a good idea of what can be worked on; nice to have some way to report on the work being done + +### vocab for AI + +Luke: I do a lot of AI related stuff. Can we add policy or vocab for AI ? +Paul: My domain. Create a few vocab. What do you mean by AI vocab ? +Luke: 2 realm: agent orchestrator, no onthology for that, might not be solid specific. Second, how ai agent can utilise solid, it would be nice to have [lower end models?] ( something better than the skillz/) +Jesse: Part of this is scope of Web Agent WG, they are more active on that topic. We need to work on WebId, auth specific to solid/LWS, delegating auth. More of this is experimental in solid. Open to write your own spec. +https://mlcommons.org/working-groups/data/croissant/ + +...:extend the capability of the solid server ( specially adding sparql endpoint ) could be in the scope of the CG to work on and could be helpful. +...: a few org presented AI related work at Sosy: +[tne.ai](https://tne.ai) +everbetter +[rewi.re](https://rewi.re) +https://sosy2026.eu/Sessions/Solid-development/ + +## Actions + +## Decisions + +## Links + + + + +