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 snapshot of the most mature and widely implemented Solid specification versions, collected to help developers and organisations identify a common baseline. It provides practical guidance for implementing the Solid specifications included in this collection.
+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. Solid26 collects the most mature and widely implemented specification versions into one coherent reference — a snapshot of the parts of the Solid platform that are most broadly supported by existing implementations.
+This document does not define new normative requirements, but rather identifies and collects the specifications needed to build interoperable Solid applications and servers.
+Specifications
+The Solid26 specification documents are as follows. All referenced specifications are W3C Solid Community Group Drafts.
+ +Solid Protocol
+The Solid Protocol (CG-DRAFT/FINAL, v0.11.0) is included with the following amendments:
+-
+
- Servers are not required to implement 5.3.1 Modifying Resources Using N3 Patches. +
- Servers MUST conform to Web Access Control (WAC). Clients are not required to conform to Access Control Policy (ACP). +
Solid-OIDC
+Solid-OIDC (CG-DRAFT/FINAL, v0.1.0) is included in the Solid26 release.
+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 (CG-DRAFT/FINAL, 2024-05-12) is included in this release. Solid26 requires servers to implement WAC as their access control mechanism.
+Note
+We would like to update the referenced WAC version and snapshot link to include the proposed changes in solid/web-access-control-spec#134, if they are merged in time.
+Note
+Servers that do not conform with this section can still interoperate with Solid26 clients that do not read or modify access controls.
+Implementation Guidance
+WebID
+Note
+Work in progress: the content from the WebID guidance document is to be integrated into this section.
+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/2024/wac-20240512 + + +