Add development status note, document goals, and fix overstated CG claims (#6)

Copilot · jeswr · web-flow · commit d3065b970cf4 · 2026-03-21T15:38:08.000Z
* Initial plan * Address clarifications: add development status note, document goals, fix overstated claims - Add prominent note that Solid26 is under development and not yet through CG process - Explicitly state the two goals of the document - Change 'first annual release of the Solid specification' to 'planned collection' - Remove language implying W3C Solid CG endorsement - Fix stewardship language to distinguish CG and ODI roles - Use proposed/planned/draft language throughout - Mark Solid26 Primer as draft Co-authored-by: jeswr <63333554+jeswr@users.noreply.github.com> Agent-Logs-Url: https://github.com/solid/solid26/sessions/da9fc89f-c00e-4e10-bf2c-5ca4e0d75397 * Clarify ODI stewards the Solid Project and contents proposed by CG members including ODI Co-authored-by: jeswr <63333554+jeswr@users.noreply.github.com> Agent-Logs-Url: https://github.com/solid/solid26/sessions/b5123891-3fc6-4d3e-bcf1-9c74f5023326 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jeswr <63333554+jeswr@users.noreply.github.com>
diff --git a/content.md b/content.md
@@ -2,29 +2,40 @@
 
 ## A stable foundation to build on
 
-Solid26 is the first annual release of the Solid specification — a curated, tested collection of standards, best practices, and documentation that gives developers, organisations, and communities a stable target to build against.
+> **Note:** Solid26 is currently under development. The primer and some specification documents referenced here have not yet been put through the W3C Solid Community Group process. We are working to have this done by the end of April 2026.
 
-Whether you're a developer building your first Solid app, an enterprise evaluating the technology, or a researcher exploring new data architectures — Solid26 is your starting point.
+### Goals of this document
+
+This page serves two purposes:
+
+1. To capture and communicate the goals and planned contents of Solid26, based on discussions in W3C Solid Community Group calls — providing a written reference for what has so far been discussed verbally.
+2. To serve as an announcement and landing page once the documents included in Solid26 have been finalised through the Community Group process.
+
+---
+
+Solid26 is a planned collection of Solid specification versions, best practices, and documentation intended to give developers, organisations, and communities a stable target to build against. The current contents have been proposed by members of the [W3C Solid Community Group](https://www.w3.org/community/solid/), including the [Open Data Institute](https://theodi.org), and will be subject to the group's processes before release.
+
+Whether you're a developer building your first Solid app, an enterprise evaluating the technology, or a researcher exploring new data architectures — Solid26 aims to be your starting point.
 
 ---
 
 ## What is Solid26?
 
-Solid has been evolving since its creation by Sir Tim Berners-Lee at MIT in 2014. Over a decade of development has produced a rich set of specifications, tools, and community knowledge — but until now, there has been no single, clearly defined version that says: *this is ready to build on*.
+Solid has been evolving since its creation by Sir Tim Berners-Lee at MIT in 2014. Over a decade of development has produced a rich set of specifications, tools, and community knowledge — but there is not yet a single, clearly defined collection that says: *this is ready to build on*.
 
-Solid26 changes that. It brings together the core Solid specifications alongside new best practice documents, developer guidance, and sector-specific materials into one coherent release. Think of it as a stable snapshot of the Solid platform — a known-good baseline that application developers and server implementers can target with confidence.
+Solid26 aims to change that. It proposes to bring together core Solid specification versions alongside new best practice documents, developer guidance, and sector-specific materials into one coherent collection. Think of it as a planned stable snapshot of the Solid platform — a known-good baseline that application developers and server implementers could target with confidence.
 
-The name "Solid26" signals that Solid is a living, rolling standard. Like modern browsers and platforms, it will continue to evolve — with the Community Group making annual releases that build on real-world feedback and adoption.
+The name "Solid26" reflects the aspiration for Solid to adopt a rolling release model. Like modern browsers and platforms, the Solid ecosystem would continue to evolve — with annual collections that build on real-world feedback and adoption. Whether this model is adopted is subject to discussion within the W3C Solid Community Group.
 
 ---
 
 ## What's included
 
 **Core specifications**
 
-The Solid26 release curates fixed versions of the most critical and stable specification documents required to build functional Solid servers and applications. These include the [Solid Protocol](https://solidproject.org/TR/protocol) (v0.11.0), [Solid WebID Profile](https://solid.github.io/webid-profile/) (v1.0.0), [Solid-OIDC](https://solidproject.org/TR/oidc) (v0.1.0), and one of [Web Access Control (WAC)](https://solidproject.org/TR/wac) or [Access Control Policy (ACP)](https://solidproject.org/TR/acp) for access control (see [discussion thread](https://lists.w3.org/Archives/Public/public-solid/2026Mar/0019.html)) — alongside specifications for notifications, access requests, and client authentication for scripts. The release document clearly signposts where there may be breaking changes in future releases, so developers can plan accordingly.
+Solid26 proposes to collect fixed versions of the most critical and stable specification documents needed to build functional Solid servers and applications. The planned specifications include the [Solid Protocol](https://solidproject.org/TR/protocol) (v0.11.0), [Solid WebID Profile](https://solid.github.io/webid-profile/) (v1.0.0), [Solid-OIDC](https://solidproject.org/TR/oidc) (v0.1.0), and one of [Web Access Control (WAC)](https://solidproject.org/TR/wac) or [Access Control Policy (ACP)](https://solidproject.org/TR/acp) for access control (see [discussion thread](https://lists.w3.org/Archives/Public/public-solid/2026Mar/0019.html)) — alongside specifications for notifications, access requests, and client authentication for scripts. The included specifications and their versions are subject to confirmation through the W3C Solid Community Group process. The collection will clearly signpost where there may be breaking changes in future versions, so developers can plan accordingly.
 
-Full technical details, including specific version pinning and amendment notes, are available in the [Solid26 Primer](https://docs.google.com/document/d/1da2J-NsU3K-4kWEFOvhzIdrvy_KftewXdlxfu401kY0/edit).
+Full technical details, including proposed version pinning and amendment notes, are available in the [Solid26 Primer](https://docs.google.com/document/d/1da2J-NsU3K-4kWEFOvhzIdrvy_KftewXdlxfu401kY0/edit) (draft).
 
 **Best practice documents**
 
@@ -83,4 +94,4 @@ Following the launch, sector-specific working groups will form to test Solid26 i
 
 Solid26 is the beginning, not the destination. We are actively tracking the [barriers to adoption](https://docs.google.com/spreadsheets/d/1F0_TRi3p2caS5oaktYjvnZy5jbElenkIBMkXNA3MCME/edit?gid=0#gid=0) that the community has identified, and feedback from developers, organisations, and working groups will feed directly into the Solid Community Group — informing priorities for the specification and tooling throughout 2026 and beyond.
 
-The Open Data Institute, as steward of the Solid Project with support from Google.org, is coordinating this work in collaboration with the global Solid community. [Learn more about how the project is governed](/community) or [explore the developer documentation](https://dev.solidproject.org) to start building today.
+The [Open Data Institute](https://theodi.org) [stewards the Solid Project](https://theodi.org/insights/projects/odi-and-solid-building-a-future-where-data-works-for-everyone/) and is coordinating the development of supporting materials for Solid26 in collaboration with the global Solid community. [Learn more about how the project is governed](/community) or [explore the developer documentation](https://dev.solidproject.org) to start building today.
diff --git a/index.html b/index.html
@@ -4,7 +4,7 @@
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   <title>Solid26 — A stable foundation to build on</title>
-  <meta name="description" content="Solid26 is the first annual release of the Solid specification — a curated, tested collection of standards, best practices, and documentation.">
+  <meta name="description" content="Solid26 is a planned collection of Solid specification versions, best practices, and documentation intended to give developers a stable target to build against.">
   <style>
     :root {
       --solid-royal-lavender: #7C4DFF;
@@ -270,24 +270,29 @@ <h1>Solid26</h1>
 
   <main>
 
+    <section style="background: #fff3cd; border: 1px solid #ffc107; border-radius: 8px; padding: 1.5rem; margin-bottom: 2rem;">
+      <p style="color: #664d03; margin-bottom: 0.75rem;"><strong>Note:</strong> Solid26 is currently under development. The primer and some specification documents referenced here have not yet been put through the W3C Solid Community Group process. We are working to have this done by the end of April 2026.</p>
+      <p style="color: #664d03; margin-bottom: 0;"><strong>Goals of this page:</strong> (1) To capture and communicate the goals and planned contents of Solid26, based on discussions in W3C Solid Community Group calls — providing a written reference for what has so far been discussed verbally. (2) To serve as an announcement and landing page once the documents included in Solid26 have been finalised through the Community Group process.</p>
+    </section>
+
     <section>
-      <p>Solid26 is the first annual release of the Solid specification — a curated, tested collection of standards, best practices, and documentation that gives developers, organisations, and communities a stable target to build against. It will be officially released at the <a href="https://sosy2026.eu/">Solid Symposium</a> (April 30 – May 1, 2026).</p>
-      <p>Whether you're a developer building your first Solid app, an enterprise evaluating the technology, or a researcher exploring new data architectures — Solid26 is your starting point.</p>
+      <p>Solid26 is a planned collection of Solid specification versions, best practices, and documentation intended to give developers, organisations, and communities a stable target to build against. The current contents have been proposed by members of the <a href="https://www.w3.org/community/solid/">W3C Solid Community Group</a>, including the <a href="https://theodi.org">Open Data Institute</a>, and will be subject to the group's processes before release. It will be officially released at the <a href="https://sosy2026.eu/">Solid Symposium</a> (April 30 – May 1, 2026).</p>
+      <p>Whether you're a developer building your first Solid app, an enterprise evaluating the technology, or a researcher exploring new data architectures — Solid26 aims to be your starting point.</p>
     </section>
 
     <section>
       <h2>What is Solid26?</h2>
-      <p>Solid has been evolving since its creation by Sir Tim Berners-Lee at MIT in 2014. Over a decade of development has produced a rich set of specifications, tools, and community knowledge — but until now, there has been no single, clearly defined version that says: <em>this is ready to build on</em>.</p>
-      <p>Solid26 changes that. It brings together the core Solid specifications alongside new best practice documents, developer guidance, and sector-specific materials into one coherent release. Think of it as a stable snapshot of the Solid platform — a known-good baseline that application developers and server implementers can target with confidence.</p>
-      <p>The name "Solid26" signals that Solid is a living, rolling standard. Like modern browsers and platforms, it will continue to evolve — with the Community Group making annual releases that build on real-world feedback and adoption.</p>
+      <p>Solid has been evolving since its creation by Sir Tim Berners-Lee at MIT in 2014. Over a decade of development has produced a rich set of specifications, tools, and community knowledge — but there is not yet a single, clearly defined collection that says: <em>this is ready to build on</em>.</p>
+      <p>Solid26 aims to change that. It proposes to bring together core Solid specification versions alongside new best practice documents, developer guidance, and sector-specific materials into one coherent collection. Think of it as a planned stable snapshot of the Solid platform — a known-good baseline that application developers and server implementers could target with confidence.</p>
+      <p>The name "Solid26" reflects the aspiration for Solid to adopt a rolling release model. Like modern browsers and platforms, the Solid ecosystem would continue to evolve — with annual collections that build on real-world feedback and adoption. Whether this model is adopted is subject to discussion within the W3C Solid Community Group.</p>
     </section>
 
     <section>
       <h2>What's included</h2>
 
       <h3>Core specifications</h3>
-      <p>The Solid26 release curates fixed versions of the most critical and stable specification documents required to build functional Solid servers and applications. These include the <a href="https://solidproject.org/TR/protocol">Solid Protocol</a> (v0.11.0), <a href="https://solid.github.io/webid-profile/">Solid WebID Profile</a> (v1.0.0), <a href="https://solidproject.org/TR/oidc">Solid-OIDC</a> (v0.1.0), and either <a href="https://solidproject.org/TR/wac">Web Access Control (WAC)</a> or <a href="https://solidproject.org/TR/acp">Access Control Policy (ACP)</a> for access control (<a href="https://lists.w3.org/Archives/Public/public-solid/2026Mar/0019.html">discussion</a>) — alongside specifications for notifications, access requests, and client authentication for scripts. The included specifications are subject to confirmation. The release document clearly signposts where there may be breaking changes in future releases, so developers can plan accordingly.</p>
-      <p>Full technical details, including specific version pinning and amendment notes, are available in the <a href="https://docs.google.com/document/d/1da2J-NsU3K-4kWEFOvhzIdrvy_KftewXdlxfu401kY0/edit">Solid26 Primer</a>.</p>
+      <p>Solid26 proposes to collect fixed versions of the most critical and stable specification documents needed to build functional Solid servers and applications. The planned specifications include the <a href="https://solidproject.org/TR/protocol">Solid Protocol</a> (v0.11.0), <a href="https://solid.github.io/webid-profile/">Solid WebID Profile</a> (v1.0.0), <a href="https://solidproject.org/TR/oidc">Solid-OIDC</a> (v0.1.0), and either <a href="https://solidproject.org/TR/wac">Web Access Control (WAC)</a> or <a href="https://solidproject.org/TR/acp">Access Control Policy (ACP)</a> for access control (<a href="https://lists.w3.org/Archives/Public/public-solid/2026Mar/0019.html">discussion</a>) — alongside specifications for notifications, access requests, and client authentication for scripts. The included specifications and their versions are subject to confirmation through the W3C Solid Community Group process. The collection will clearly signpost where there may be breaking changes in future versions, so developers can plan accordingly.</p>
+      <p>Full technical details, including proposed version pinning and amendment notes, are available in the <a href="https://docs.google.com/document/d/1da2J-NsU3K-4kWEFOvhzIdrvy_KftewXdlxfu401kY0/edit">Solid26 Primer</a> (draft).</p>
 
       <h3>Best practice documents</h3>
       <p>New guidance covering practical topics that developers and organisations need, including:</p>
@@ -355,14 +360,14 @@ <h2>Get involved</h2>
     <section class="cta-section">
       <h2>Help shape what comes next</h2>
       <p>Solid26 is the beginning, not the destination. We are actively tracking the <a href="https://docs.google.com/spreadsheets/d/1F0_TRi3p2caS5oaktYjvnZy5jbElenkIBMkXNA3MCME/edit?gid=0#gid=0">barriers to adoption</a> that the community has identified, and feedback from developers, organisations, and working groups will feed directly into the Solid Community Group — informing priorities for the specification and tooling throughout 2026 and beyond.</p>
-      <p>The <a href="https://www.w3.org/community/solid/">Solid Community Group</a> is coordinating this work in collaboration with the global Solid community, stewarded by the <a href="https://theodi.org">Open Data Institute</a>.</p>
+      <p>The <a href="https://theodi.org">Open Data Institute</a> <a href="https://theodi.org/insights/projects/odi-and-solid-building-a-future-where-data-works-for-everyone/">stewards the Solid Project</a> and is coordinating the development of supporting materials for Solid26 in collaboration with the global Solid community.</p>
       <a href="https://dev.solidproject.org" class="btn-primary">Start building with Solid</a>
     </section>
 
   </main>
 
   <footer>
-    <p>Solid26 — A release by the <a href="https://www.w3.org/community/solid/">Solid Community Group</a>, stewarded by the <a href="https://theodi.org">Open Data Institute</a></p>
+    <p>Solid26 — Proposed by members of the <a href="https://www.w3.org/community/solid/">Solid Community Group</a>. The <a href="https://theodi.org">Open Data Institute</a> <a href="https://theodi.org/insights/projects/odi-and-solid-building-a-future-where-data-works-for-everyone/">stewards the Solid Project</a>.</p>
     <p style="margin-top: 0.5rem;"><a href="https://solidproject.org">solidproject.org</a> · <a href="https://dev.solidproject.org">Developer docs</a> · <a href="https://github.com/solid">GitHub</a></p>
   </footer>
 
