From d94754da88ebd8685947096d824737d356056caf Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 5 Apr 2021 09:30:13 +0200 Subject: [PATCH 1/8] Add Inbox Discovery on Client Error --- protocol.html | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/protocol.html b/protocol.html index 546bae54..c6d53a47 100644 --- a/protocol.html +++ b/protocol.html @@ -688,6 +688,29 @@

Notifications

A Solid server MUST conform to the LDN specification by implementing the Receiver parts to receive notifications and make Inbox contents available [LDN].

A Solid client MUST conform to the LDN specification by implementing the Sender or Consumer parts to discover the location of a resource’s Inbox, and to send notifications to an Inbox or to retrieve the contents of an Inbox [LDN].

+ +
+

Inbox Discovery on Client Error

+
+

This section extends the LDN protocol to allow the discovery of the Inbox URL of a target resource on client errors (HTTP responses with 4xx status codes) [RFC7231][LDN].

+ +

Servers who want to advertise the Inbox URL in a HTTP response with a 4xx status code, MUST do one of the following:

+ +
    +
  • include the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
    • +
  • include an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is target and the object is the Inbox.
    • +
+ +

Senders and consumers do the following to discover the Inbox URL in a HTTP response with a 4xx status code:

+ +
    +
  • use the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
    • +
  • parse an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is target and the object is the Inbox.
    • +
+ +

These may be carried out in either order, but if the first fails to result in an Inbox the second MUST be tried.

+
+
From 1b3f35ddb7b6dde4151d0896c7f5decc53d83c40 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 5 Apr 2021 14:39:24 +0200 Subject: [PATCH 2/8] Clarifications and corrections on request and roles --- protocol.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/protocol.html b/protocol.html index c6d53a47..10b1baa5 100644 --- a/protocol.html +++ b/protocol.html @@ -698,14 +698,14 @@

Inbox Discovery on Client Error

-

Senders and consumers do the following to discover the Inbox URL in a HTTP response with a 4xx status code:

+

Senders do the following to discover the Inbox URL in a HTTP response with a 4xx status code:

These may be carried out in either order, but if the first fails to result in an Inbox the second MUST be tried.

From f36ee6c8ddee07f9fd789d847924315d64f19607 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 5 Apr 2021 15:03:00 +0200 Subject: [PATCH 3/8] Add Discovery example: Client error --- protocol.html | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/protocol.html b/protocol.html index 10b1baa5..8f351d3f 100644 --- a/protocol.html +++ b/protocol.html @@ -709,6 +709,17 @@

Inbox Discovery on Client Error

These may be carried out in either order, but if the first fails to result in an Inbox the second MUST be tried.

+ +
+

Discovery example: Client error

+ 
PUT /article HTTP/1.1
+Host: example.org
+Content-Type: text/html;charset=utf-8
+
+HTTP/1.1 403 Forbidden
+Link: <http://example.org/inbox/> rel="http://www.w3.org/ns/ldp#inbox"
+
Discovering an Inbox in the response of a rejected request.
+
From f2fe58d5617aa84101e8ea4508bb2e12a3a2b303 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Tue, 6 Apr 2021 12:04:25 +0200 Subject: [PATCH 4/8] Update protocol.html Co-authored-by: Matthieu Bosquet --- protocol.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/protocol.html b/protocol.html index 8f351d3f..296e56aa 100644 --- a/protocol.html +++ b/protocol.html @@ -704,8 +704,8 @@

Inbox Discovery on Client Error

Senders do the following to discover the Inbox URL in a HTTP response with a 4xx status code:

    -
  • use the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
    • -
  • parse an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is the target resource and the object is the Inbox.
    • +
  • Use the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
    • +
  • Parse an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is the target resource and the object is the Inbox.

These may be carried out in either order, but if the first fails to result in an Inbox the second MUST be tried.

From 8db97aa76a00160e1866ff47d5bff88f0983f5db Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Tue, 6 Apr 2021 12:04:32 +0200 Subject: [PATCH 5/8] Update protocol.html Co-authored-by: Matthieu Bosquet --- protocol.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/protocol.html b/protocol.html index 296e56aa..5ec57067 100644 --- a/protocol.html +++ b/protocol.html @@ -697,8 +697,8 @@

Inbox Discovery on Client Error

Servers who want to advertise the Inbox URL in a HTTP response with a 4xx status code, MUST do one of the following:

    -
  • include the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
    • -
  • return an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is the target resource and the object is the Inbox.
    • +
  • Include the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
    • +
  • Return an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is the target resource and the object is the Inbox.

Senders do the following to discover the Inbox URL in a HTTP response with a 4xx status code:

From 18d864301c3b3b43031c1d12fd45850bfdbe646c Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Tue, 6 Apr 2021 12:04:38 +0200 Subject: [PATCH 6/8] Update protocol.html Co-authored-by: Matthieu Bosquet --- protocol.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocol.html b/protocol.html index 5ec57067..6046bdd7 100644 --- a/protocol.html +++ b/protocol.html @@ -701,7 +701,7 @@

Inbox Discovery on Client Error

  • Return an RDF representation [RDF11-CONCEPTS], whose encoded RDF graph contains a relation of type http://www.w3.org/ns/ldp#inbox. The subject of that relation is the target resource and the object is the Inbox.
    • -

    Senders do the following to discover the Inbox URL in a HTTP response with a 4xx status code:

    +

    Senders do the following to discover the Inbox URL in an HTTP response with a 4xx status code:

    • Use the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
      • From 033dcdef0b8a8528f7b4e761a4ade4cd99038389 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Tue, 6 Apr 2021 12:04:43 +0200 Subject: [PATCH 7/8] Update protocol.html Co-authored-by: Matthieu Bosquet --- protocol.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocol.html b/protocol.html index 6046bdd7..f9abd000 100644 --- a/protocol.html +++ b/protocol.html @@ -694,7 +694,7 @@

      Inbox Discovery on Client Error

      This section extends the LDN protocol to allow the discovery of the Inbox URL of a target resource on client errors (HTTP responses with 4xx status codes) [RFC7231][LDN].

      -

      Servers who want to advertise the Inbox URL in a HTTP response with a 4xx status code, MUST do one of the following:

      +

      Servers who want to advertise the Inbox URL in an HTTP response with a 4xx status code, MUST do one of the following:

      • Include the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.
        • From 366a5e6d3b916a332692274f0ed297023917d156 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Sun, 11 Apr 2021 22:24:06 +0200 Subject: [PATCH 8/8] Make only one inbox advertisement clear --- protocol.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocol.html b/protocol.html index f9abd000..336788dd 100644 --- a/protocol.html +++ b/protocol.html @@ -694,7 +694,7 @@

        Inbox Discovery on Client Error

        This section extends the LDN protocol to allow the discovery of the Inbox URL of a target resource on client errors (HTTP responses with 4xx status codes) [RFC7231][LDN].

        -

        Servers who want to advertise the Inbox URL in an HTTP response with a 4xx status code, MUST do one of the following:

        +

        Servers who want to advertise the Inbox URL in an HTTP response with a 4xx status code, MUST do only one of the following:

        • Include the Link header with a rel value of http://www.w3.org/ns/ldp#inbox.