diff --git a/meetings/2026-07-29.md b/meetings/2026-07-29.md
new file mode 100644
index 00000000..f5ea4c11
--- /dev/null
+++ b/meetings/2026-07-29.md
@@ -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
+
+