-
Notifications
You must be signed in to change notification settings - Fork 99
Create 2026-07-29.md #810
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.
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
Open
elf-pavlik
wants to merge
1
commit into
main
Choose a base branch
from
elf-pavlik-patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+111
−0
Open
Create 2026-07-29.md #810
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,111 @@ | ||
| # W3C Solid Community Group: Weekly | ||
|
|
||
| * Date: 2026-07-29T14:00:00Z | ||
| * Call: https://meet.jit.si/solid-cg | ||
| * Repository: https://github.com/solid/specification | ||
|
|
||
| ## Chair | ||
|
|
||
| * [elf Pavlik](https://elf-pavlik.hackers4peace.net) | ||
|
|
||
| ## Present | ||
|
|
||
| * Roberto S.K. Breitman (ODI) | ||
| * [Luke Dary](https://w3c.social/@lukedary) | ||
| * [Jesse Wright](https://jeswr.org/#me) | ||
| * Theo - @thhck | ||
| * 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 | ||
|
|
||
| * | ||
|
|
||
|
|
||
| ## 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 | ||
|
|
||
| ### Solid World - July 29th | ||
| * https://lists.w3.org/Archives/Public/public-solid/2026Jul/0013.html | ||
|
|
||
| ### OS Tools meeting - August 05th | ||
| - https://www.w3.org/events/meetings/a6b0a3dc-30fe-4f08-ac74-f51ba5418d07 | ||
| - https://lists.w3.org/Archives/Public/public-solid/2026Jul/0016.html | ||
|
|
||
| * eP: WASM, WASI, WIT, WAC, jco, Component Model | ||
|
|
||
| ## Actions Review | ||
|
|
||
| * Michal: to offer use case for application needs in LDO, regarding app capabilities | ||
| * Erich: to check SPARQL 1.2 and HTTP QUERY status | ||
|
|
||
|
|
||
| ## Topics | ||
|
|
||
| ### Demos | ||
|
|
||
| ### TPAC Session for Solid CG | ||
|
|
||
| https://github.com/w3c-cg/solid/issues/84 | ||
|
|
||
| * 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) | ||
|
|
||
| ### diff LWS Solid | ||
|
|
||
| https://github.com/w3c/lws-protocol/issues/66 | ||
|
|
||
| * eP: I offered help with 3 topics, collaboration is welcomed and there is a need to cover more topics! | ||
|
|
||
|
|
||
| ### New Work Item: Application Capability | ||
| * https://github.com/solid/specification/issues/806 | ||
| * CB: Just to point to that proposal here again. Do all meeting participants know that proposal yet? Go have a look and leave feedback! Or voice your opinion here! | ||
| * ... if Yvo is here: Did you see https://github.com/solid/specification/pull/798#discussion_r3613126582? | ||
|
|
||
| ### Formal vocab for Solid Protocol (and beyond, e.g., to LWS) | ||
|
|
||
| * RZ: Pavlik mentioned there is a formal vocab to describe terms in Solid Protocol. An attempt to rewrite protocol to use those terms. To have interoperable base that could also work in LWS. | ||
| * ...: It was new to me, I took a brief read. I had hasitation on how the vocab was intented to be used, markup, annotation, or Solid Protocol would be written as that vocab. | ||
| * ...: A - rewrite solid Protocol using RDF | ||
| * ...: B - keep in HTML and use those terms | ||
| * eP: talking about spec vocab and using in solid RDFa and JSON-LD in script tags | ||
| * JW: I would like to generate diagrams directly from the way the spec defines services and relationships between services. The threat model to be formally deifned in terms of identifiers of LWS services. | ||
| * ...: Some people may consider it overformalizing | ||
| * eP: I cant read this https://github.com/solid/specification/pull/807/files#diff-d28e1706bf82e98cbda64de615436823ef8b0b61f5c05b2327b35bb1d0863558R839 | ||
| * RZ: Exactly the issue. But unfortunately RDF is not sufficient; XML is ugly in this way. Sacrifice is needed somewhere anyway. | ||
| * Th: There is a markdown that is bit more readable that can compile to RDFa | ||
| * ...: Is there an editor plugin to make it more readable | ||
| * eP: There is no one editor everyone is using, maybe LSP? | ||
| * | ||
|
|
||
| ## Actions | ||
|
|
||
| * JW to setup ai diffing of the specs (Solid & LWS) | ||
|
|
||
| ## Decisions | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elf-pavlik dokieli ( https://dokie.li/ ) is an RDFa editor with a team who is very active in the Solid CG. We would appreciate your supporting our work as chair of the CG, and perhaps encouraging adoption of our own tools.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant code-editor. People are using VSCode (and all its forks), NeoVim, Zed, Emacs, Sublime, Webstorm, IntelliJ, Helix etc.
While I appreciate dokieli's team efforts, the big promise of Solid is that each user can use whatever app they like. When it comes to the specs we rely on git not solid, text files and build/ci steps to produce final documents. If dokieli can produce those files in a way that someone can make a PR, that's amazing! Nice to have another option to choose from 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dokieli already reads from and writes to git repositories (GitHub and Forgejo/Codeberg). Each save is a commit on a branch, so opening a PR from it is the normal forge flow. The "if dokieli can produce those files" framing doesn't apply: it can, and has been able to for some time. When the target is a .md file it serializes to Markdown, retaining the semantics as much as Markdown allows.
To be clear, I'm not interested in arguing this to death, and I agree nobody should be mandated a tool; author in whatever you like. It just struck me that "we rely on git, not Solid" is a missed opportunity: it would be nice if the CG could also say it relies on tools built on its own specs, at least as one option among the editors you listed.
Happy to demo the git workflow if that would help inform the discussion.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you demo Vim mode, Emacs mode, Helix mode, Kakoune mode, Sublime mode etc. ?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@VirginiaBalseiro you and all CG members can always do demos, please just add it to the https://hackmd.io/@solid/cg-weekly or even just show up and offer to do a demo.
My main point is - for editing spec that aim to go through W3C process, I consider https://github.com/speced as a baseline and currently Github de facto collab space.
I'm also happy to experiment with using Solid apps in CG interactions. A low-hanging fruit from my perspective would be simple 'mark yourself present' where various apps would allow anyone to do it with a simple tap, rather than type/paste name in hackmd. Bit higher hanging fruit, something like https://github.com/hackers4peace/sai-js/tree/main/examples/plenary or fixing calendars / scheduling / RSVPs in general.
Starting with using Solid to edit Solid spec, feels to me like starting a programming language with self-hosting and skipping bootstrap phase. I don't expect anyone to agree with me but personally I would be more interested in simple low-hanging fruit like 'mark yourself present' - one tap on mobile ✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, in "who does the job, calls the shots" spirit. I think scribe should decide on the tool they want to use. If someone who scribes wants to use dokieli or anything else that allows others to make real time corrections, I think that would be cool! In the end it just needs to end up in a PR like this one.