From 4ec41fdd9e6c7cc3b067a4bf32a4aa64c13decf4 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Thu, 2 Apr 2020 12:47:58 +0200 Subject: [PATCH] Revise slash semantics --- main/resource-access.bs | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/main/resource-access.bs b/main/resource-access.bs index aa833353..57ddc8ed 100644 --- a/main/resource-access.bs +++ b/main/resource-access.bs @@ -77,10 +77,12 @@ A Solid client MUST use the `Content-Type` HTTP header in `PUT`, `POST` and ## Uniform Resource Identifier ## {#uri} -### Required shared slash semantics ### {#uri-path-component} +### Shared slash semantics ### {#uri-slash-semantics} -Server and client share the slash semantics in the URI path component -representing hierarchy [[!RFC3986]]. +The slash character in the URI path indicates hierarchical relationship +segments, and enables relative referencing [[!RFC3986]]. The semantics of the +slash character is shared by servers and clients. Paths ending with a slash +denote a container resource. [[Source](https://github.com/solid/specification/issues/35#issuecomment-547949014)] If two URIs differ only in the trailing slash, and the server has associated a