From dabca8d514b7b826a0dc9a487d77d7027613ee7d Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 21 Nov 2022 15:08:48 +0100 Subject: [PATCH 1/5] Add normative-informative-content --- protocol.html | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/protocol.html b/protocol.html index 7fea7e6..8ca7430 100644 --- a/protocol.html +++ b/protocol.html @@ -477,9 +477,18 @@

Namespaces

Conformance

-

All assertions, diagrams, examples, and notes are non-normative, as are all sections explicitly marked non-normative. Everything else is normative.

+

This section describes the conformance model of the Solid Notifications Protocol.

-

The key words “MUST” and “MUST NOT” are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

+
+

Normative and Informative Content

+
+

All assertions, diagrams, examples, and notes are non-normative, as are all sections explicitly marked non-normative. Everything else is normative.

+ +

The key words “MUST”, “MUST NOT”, “SHOULD”, and “MAY” are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

+ +

The key words “strongly encouraged”, “strongly discouraged”, “encouraged", “discouraged", “can", “cannot”, “could”, “could not”, “might”, and “might not” are used for non-normative content.

+
+
From 376684aed8c58b2bdce16e78149ac9eaae0403cc Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 21 Nov 2022 15:09:49 +0100 Subject: [PATCH 2/5] Add classes-of-products --- protocol.html | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/protocol.html b/protocol.html index 8ca7430..fd6ee3f 100644 --- a/protocol.html +++ b/protocol.html @@ -489,6 +489,24 @@

Normative and Informative Content

The key words “strongly encouraged”, “strongly discouraged”, “encouraged", “discouraged", “can", “cannot”, “could”, “could not”, “might”, and “might not” are used for non-normative content.

+ +
+

Classes of Products

+
+

The Solid Notifications Protocol identifies the following Classes of Products for conforming implementations. These products are referenced throughout this specification.

+ + + +
+
Client
+
A client that builds on HTTP client [RFC7230], [RFC7231], and [FETCH] by defining behaviour in terms of fetching across the platform.
+
Notification Server
+
A notification server that builds on HTTP server [RFC7230] and [RFC7231].
+
Resource Server
+
A resource server that builds on HTTP server [RFC7230] and [RFC7231] by defining media types, HTTP header fields, and the behaviour of resources, as identified by link relations.
+
+
+
From a3e3ce7401ad7fc1fc7518a4db09e905b462a5d6 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 21 Nov 2022 15:10:20 +0100 Subject: [PATCH 3/5] Add specification-category --- protocol.html | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/protocol.html b/protocol.html index fd6ee3f..d9629e4 100644 --- a/protocol.html +++ b/protocol.html @@ -507,6 +507,13 @@

Classes of Products

+ +
+

Specification Category

+
+

The Solid Protocol identifies the following Specification Category to distinguish the types of conformance: API, Notation/syntax, Set of events, Protocol.

+
+
From 78ef50859e7b0c0a7c51f27230c2aa37ddb6b790 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 21 Nov 2022 15:10:48 +0100 Subject: [PATCH 4/5] Add interoperability --- protocol.html | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/protocol.html b/protocol.html index d9629e4..4904c5f 100644 --- a/protocol.html +++ b/protocol.html @@ -514,6 +514,15 @@

Specification Category

The Solid Protocol identifies the following Specification Category to distinguish the types of conformance: API, Notation/syntax, Set of events, Protocol.

+ +
+

Interoperability

+
+

Interoperability of implementations for clients and resource servers is tested by evaluating an implementation’s ability to request and respond to HTTP messages that conform to this specification.

+ +

Interoperability of implementations for clients and notification servers is tested by evaluating an implementation’s ability to request and respond to HTTP messages that conform to this specification.

+
+
From b4b4f3f8b33f65ab1b456351492e802776f04504 Mon Sep 17 00:00:00 2001 From: Sarven Capadisli Date: Mon, 21 Nov 2022 15:15:45 +0100 Subject: [PATCH 5/5] Add conformance to change-log --- protocol.html | 1 + 1 file changed, 1 insertion(+) diff --git a/protocol.html b/protocol.html index 4904c5f..69de298 100644 --- a/protocol.html +++ b/protocol.html @@ -976,6 +976,7 @@

Changes from notifications-protocol-20220509 to this
  • Add server notification channel discovery requirements with Link headers: describedby, http://www.w3.org/ns/solid/terms#storageDescription.
  • Clarify authentication and authorization as non-normative and encouragement.
  • Clarify server notification channel resource requirement using JSON-LD @context.
    • +
  • Update Conformance to add Normative and Information Content, Class of Products, Specification Category, Interoperability.