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>Solid has the notion of <em>auxiliary resources</em> to provide supplementary information such as descriptive metadata, authorization conditions, data shape constraints, digital rights or provenance record about a given resource (hereafter referred as the <em>subject resource</em>), and affects how resources and others associated with it are processed, served or interpreted.</p>
685
685
686
-
<pid="auxiliary-resources-management">Server manages the association between a subject resource and auxiliary resources defined by this specification. The lifecycle of auxiliary resources defined by this specification depend on the lifecycle of the subject resource that they are associated with.</p>
686
+
<p><spanabout="" id="server-auxiliary-resources-management"rel="spec:requirement" resource="#server-auxiliary-resources-management"><spanproperty="spec:statement"><spanrel="spec:requirementSubject" resource="spec:Server">Servers</span><spanrel="spec:requirementLevel" resource="spec:MUST">MUST</span> support auxiliary resources defined by this specification and manage the association between a subject resource and auxiliary resources. The lifecycle of auxiliary resources defined by this specification depend on the lifecycle of the subject resource that they are associated with.</span></span></p>
687
687
688
688
<pid="auxiliary-resources-rdf-document">Auxiliary resources are represented as <em>RDF document</em>s [<cite><aclass="bibref" href="#bib-rdf11-concepts">RDF11-CONCEPTS</a></cite>]. HTTP interactions on auxiliary resources are subject to the requirements as per <cite><ahref="#reading-writing-resources">Reading and Writing Resources</a></cite>.</p>
<p><spanabout="" id="server-link-auxiliary-type" rel="spec:requirement" resource="#server-link-auxiliary-type"><spanproperty="spec:statement"><spanrel="spec:requirementSubject" resource="spec:Server">Servers</span><spanrel="spec:requirementLevel" resource="spec:MUST">MUST</span> advertise auxiliary resources associated with a subject resource by responding to <code>HEAD</code> and <code>GET</code> requests including the HTTP <code>Link</code> header with the <code>rel</code> parameter [<cite><aclass="bibref" href="#bib-rfc8288">RFC8288</a></cite>].</span></span></p>
705
+
704
706
<p><spanabout="" id="client-link-auxiliary-type" rel="spec:requirement" resource="#client-link-auxiliary-type">Clients can discover auxiliary resources associated with a subject resource by making an HTTP <code>HEAD</code> or <code>GET</code> request on the target URL, and checking the HTTP <code>Link</code> header with the <code>rel</code> parameter [<cite><aclass="bibref" href="#bib-rfc8288">RFC8288</a></cite>].</span></p>
0 commit comments