Clients can discover auxiliary resources associated with a subject resource by making an HTTP HEAD or GET request on the target URL, and checking the HTTP Link header with the rel parameter [RFC8288].
describedbyhttp://www.w3.org/ns/solid/terms#statResourceClients can discover resources that are described by description resources by making an HTTP HEAD or GET request on the target URL, and checking the HTTP Link header with a rel value of describes (inverse of the describedby relation) [RFC6892].
+ An auxiliary resource of type Container Metadata Resource provides server-maintained metadata about contained resources. +
+When a read operation targets a container, servers MUST advertize the existence of this type of resource using a HTTP Link header with a rel value of http://www.w3.org/ns/solid/terms#statResource.
+
+ When a read operation targets a Container Metadata Resource, servers MUST supply the following metadata about a representation of each contained resource of the corresponding container:
+
+
+ rdf:type and a class whose URI is the expansion of the URI Template [RFC6570] http://www.w3.org/ns/iana/media-types/{+iana-media-type}#Resource, where iana-media-type corresponds to a value from the IANA Media Types [IANA-MEDIA-TYPES].
+
dct:modified using a xsd:dateTime data type; and stat:mtime given as a UNIX timestamp.stat:size predicate.
Servers MUST NOT allow non-read operations and reject requests using methods other than GET, HEAD and OPTIONS using a 405 status code.
By default, the server uses the authorization rule for the corresponding container for the container metadata resource. However, servers MAY associate an explicit authorization rule with the container metadata resource that further restricts access to the resource. +
+