You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>This document is the Solid26 Implementors Guide — 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.</p>
272
+
<p>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.</p>
<p>This document was published by the <ahref="https://www.w3.org/groups/cg/solid/">W3C Solid Community Group</a>. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the <ahref="https://www.w3.org/community/about/agreements/cla/">W3C Community Contributor License Agreement (CLA)</a> there is a limited opt-out and other conditions apply. Learn more about <ahref="https://www.w3.org/community/">W3C Community and Business Groups</a>.</p>
279
-
<p>This document is intended to provide implementation guidance for the Solid specifications collected in the Solid26 Implementors Guide. The content of this guide is informative and non-normative. It may be updated, replaced, or obsoleted by other documents at any time.</p>
279
+
<p>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.</p>
280
280
<p>Comments regarding this document are welcome. Please file issues on <ahref="https://github.com/solid/specification/issues">GitHub</a>.</p>
The <ahref="https://solidproject.org/TR/">Solid Technical Reports</a> comprise multiple specification documents with differing levels of maturity.
326
326
The <ahref="https://solidproject.org/TR/protocol">Solid Protocol</a> bundles the <ahref="https://solidproject.org/TR/protocol#abstract">specifications that, together, provide applications with secure and permissioned access to externally stored data in an interoperable way</a>.
327
-
The Solid26 Implementors Guide points implementers to fixed versions of the <ahref="https://solidproject.org/TR/protocol">Solid Protocol</a> and its sub-specifications, a stable snapshot of the specifications to build against today.
328
-
The Solid26 Implementors Guide selects for the most widely implemented specification versions at the time of this documents publication.
327
+
Solid26 points implementers to fixed versions of the <ahref="https://solidproject.org/TR/protocol">Solid Protocol</a> and its sub-specifications, a stable snapshot of the specifications to build against today.
328
+
Solid26 selects for the most widely implemented specification versions at the time of this documents publication.
329
329
</p>
330
330
<p>This document does not define new normative requirements, but rather identifies and collects the specifications needed to build interoperable Solid applications and servers.</p>
<p><ahref="https://solidproject.org/TR/2022/oidc-20220328">Solid-OIDC</a> (v0.1.0, 2022-03-28) is included with the following comments:</p>
410
410
<ul>
411
411
<li>
412
-
<p>Despite the Solid26 Implementors Guide including Solid-OIDC v0.1.0, it is not widely implemented. In particular, the Solid-OIDC recommended flow of User-Managed Access (UMA) is not supported by any open source Solid Server implementation. Current implementations rely on the access token issued by the OpenID Provider of the user to authenticate the user at a Solid Storage.</p>
412
+
<p>Despite Solid26 including Solid-OIDC v0.1.0, it is not widely implemented. In particular, the Solid-OIDC recommended flow of User-Managed Access (UMA) is not supported by any open source Solid Server implementation. Current implementations rely on the access token issued by the OpenID Provider of the user to authenticate the user at a Solid Storage.</p>
<p><ahref="https://www.w3.org/2005/Incubator/webid/spec/identity/">WebID 1.0</a> (W3C Editor's Draft, 5 March 2014) is included with the following comments:</p>
439
+
<p><ahref="https://www.w3.org/2005/Incubator/webid/spec/identity/">WebID 1.0</a> (W3C Editor's Draft, 5 March 2014) is included.</p>
440
440
<divclass="note">
441
441
<h4><span>Note</span></h4>
442
442
<p>Throughout this document, references to "the WebID specification" or [<cite><aclass="bibref" href="#ref-webid">WEBID</a></cite>] refer to WebID 1.0 as pinned here. WebID 1.0 has the status of a W3C Editor's Draft from the (now closed) W3C WebID Incubator Group; it has not progressed to a W3C Recommendation. The Solid Protocol and Solid-OIDC normatively reference WebID 1.0 for the definition of the term <em>WebID</em>.</p>
<p>This section gives implementation guidance for WebID in the context of the Solid26 Implementors Guide. It is organized into requirements derivable from the pinned specifications (<ahref="#webid-normative">§ 3.1.1</a>) and common assumptions not required by them (<ahref="#webid-non-normative">§ 3.1.2</a>) (see <ahref="#specifications">§ 2 Specifications</a>), and a recommended profile assembly algorithm (<ahref="#webid-algorithms">§ 3.1.3</a>). Guidance for client implementors is given in <ahref="#client-guidance">§ 4 Guidance for clients</a>.</p>
470
+
<p>This section gives implementation guidance for WebID in the context of the Solid26 Implementation Guide. It is organized into requirements derivable from the respective specifications (<ahref="#webid-normative">§ 3.1.1</a>) and common assumptions not required by them (<ahref="#webid-non-normative">§ 3.1.2</a>) (see <ahref="#specifications">§ 2 Specifications</a>), and a recommended profile assembly algorithm (<ahref="#webid-algorithms">§ 3.1.3</a>). Guidance for client implementers is given in <ahref="#client-guidance">§ 4 Guidance for clients</a>.</p>
471
471
472
472
<p>For the purposes of this section, the following terms are used:</p>
<dd>A private Web resource, linked from the agent's <ahref="#dfn-webid-profile">WebID Profile</a>, that holds settings and pointers to private data. Generally accessible only to the user (or a delegated agent).</dd>
<dd>The RDF graph [<cite><aclass="bibref" href="#ref-rdf11-concepts">RDF11-CONCEPTS</a></cite>] formed by the union of the <ahref="#dfn-webid-profile-document">WebID Profile Document</a> with any <ahref="#dfn-extended-profile-document">Extended Profile Documents</a>, assembled per <ahref="#webid-non-normative">§ 3.1.2 Common assumptions not required by Solid26 Implementors Guide specifications</a>.</dd>
483
+
<dd>The RDF graph [<cite><aclass="bibref" href="#ref-rdf11-concepts">RDF11-CONCEPTS</a></cite>] formed by the union of the <ahref="#dfn-webid-profile-document">WebID Profile Document</a> with any <ahref="#dfn-extended-profile-document">Extended Profile Documents</a>, assembled per <ahref="#webid-non-normative">§ 3.1.2 Common assumptions not required by Solid26 Implementation Guide specifications</a>.</dd>
0 commit comments