diff --git a/protocol.html b/protocol.html index 3ea949c..f7b11b5 100644 --- a/protocol.html +++ b/protocol.html @@ -495,13 +495,17 @@

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].
+
Subscription Client
+
A subscription client that builds on HTTP client [RFC7230], [RFC7231], and [FETCH] by defining behaviour in terms of fetching across the platform.
+
Subscription Server
+
A subscription server that builds on HTTP server [RFC7230] and [RFC7231].
+
Notification Sender
+
A notification sender is the sender of a notification acting in conformance to the product class of a subscription type.
+
Notification Receiver
+
A notification receiver is the recipient of a notification acting in conformance to the product class of a subscription type.
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.
@@ -518,9 +522,11 @@

Specification Category

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

+

Interoperability of implementations for subscription clients and subscription 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 notification sender and notification receiver is tested by evaluating an implementation’s ability to produce and consume content that adheres to the notification data model and conforms to a particular subscription type.