diff --git a/protocol.html b/protocol.html index 7fea7e6..69de298 100644 --- a/protocol.html +++ b/protocol.html @@ -477,9 +477,52 @@

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.

+
+
+ +
+

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.
+
+
+
+ +
+

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.

+
+
@@ -933,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.