Solid26: Implementation Guide
+Draft Community Group Report,
+More details about this document
+-
+
- This version +
- https://solidproject.org/TR/solid26 +
-
+
- Latest published version +
- https://solidproject.org/TR/solid26 +
-
+
- Editors +
- Jesse Wright (University of Oxford) +
- Christoph Braun (Karlsruhe Institute of Technology) +
-
+
- Published + +
-
+
- Modified + +
-
+
- Feedback +
- GitHub solid/specification (pull requests, new issue, open issues) +
-
+
- Language +
- English +
-
+
- Document Type +
- Implementation Guide +
Copyright © 2026 the Contributors to Solid26: Implementation Guide, under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available.
++
Abstract
+This document is an implementation guide for Solid26 — a curated collection of Solid specification versions intended to give developers, organisations, and communities a stable target to build against. It provides practical guidance for implementing the Solid specifications included in this release.
+Status of This Document
+This document was published by the W3C Solid Community Group as an implementation guide. It is not a W3C Standard nor is it on the W3C Standards Track.
+This document is intended to provide implementation guidance for the Solid specifications collected in the Solid26 release. The content of this guide is informative and non-normative. It may be updated, replaced, or obsoleted by other documents at any time.
+Comments regarding this document are welcome. Please file issues on GitHub.
+Introduction
+The Solid Specification defines multiple sub-specification documents with differing levels of maturity. This, the Solid26 release, curates those sub-specifications with fixed versions of the most critical and stable documents required to build functional Solid servers and applications.
+This document serves as an implementation guide — it does not define new normative requirements, but rather collects and explains the specifications needed to build interoperable Solid applications and servers as part of the Solid26 release.
+ +What is Solid26?
+Solid has been evolving since it was developed by Sir Tim Berners-Lee and his team at MIT. Decades 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 aims to change that. It brings together core Solid specification versions into one coherent collection. 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.
+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.
+Note
+Solid26 does not change or remove existing parts of the Solid Specification in any way. It adds to the existing set of resources in the Solid community, and aims to make Solid more accessible.
+Specifications
+The Solid26 specification documents are as follows:
+ +Solid Protocol
+The Solid Protocol (v0.11.0) is included with the following amendments. Servers are not required to implement the following:
+ +The Solid Protocol document is stable.
+Solid-OIDC
+Solid-OIDC (v0.1.0) is included in the Solid26 release.
+Solid-OIDC is subject to change as best practices for authentication evolve.
+Editor's Note
+Solid-OIDC v0.1.0 is not a widely implemented version. A document that accurately reflects current implementations is being drafted by Christoph Braun. This PR is waiting for that document to be available and ready to reference before merging.
+Web Access Control
+Web Access Control (Editor's Draft, 2024-06-03) is included in this release.
+The Web Access Control specification is likely to become one of many access control language profiles which are supported in future releases. Note that most clients should not need to manage access controls — and hence should not be affected by a change in the access control language that a server uses.
+Stability Expectations
+The following table summarises the stability expectations for each specification included in this release:
+| Specification | +Version | +Stability | +
|---|---|---|
| Solid Protocol | +v0.11.0 | +Stable | +
| Solid-OIDC | +v0.1.0 | +Subject to change | +
| Web Access Control | +ED 2024-06-03 | +May become one of many profiles | +
Implementation Requirements
+This section describes the expected requirements for applications and servers targeting the Solid26 release.
+ +Server Conformance
+Servers conforming to Solid26 are expected to implement all parts of the Solid Protocol (v0.11.0) with the exceptions noted in that section, along with Solid-OIDC and Web Access Control.
+References
+-
+
- [SOLID-PROTOCOL] +
- Solid Protocol. Sarven Capadisli; Tim Berners-Lee; Kjetil Kjernsmo. W3C Solid Community Group. URL: https://solidproject.org/TR/protocol + +
- [SOLID-OIDC] +
- Solid-OIDC. W3C Solid Community Group. URL: https://solidproject.org/TR/oidc + +
- [WAC] +
- Web Access Control. W3C Solid Community Group. URL: https://solidproject.org/TR/wac + + +
Acknowledgements
+The content of Solid26 has been proposed by members of the W3C Solid Community Group, including the Open Data Institute, and is subject to the group's processes.
+The Open Data Institute stewards the Solid Project and is coordinating the development of supporting materials for Solid26 in collaboration with the global Solid community.
+