diff --git a/protocol.html b/protocol.html index 735b1b7..bfcf170 100644 --- a/protocol.html +++ b/protocol.html @@ -410,22 +410,22 @@

Terminology

This specification defines the following terms. These terms are referenced throughout this specification.

- +
- Notification Channel + notification channel
- A Notification Channel is an abstract thing which is identified by a URI and whose properties describe the available communication interface and features. + A notification channel is an abstract thing which is identified by a URI and whose properties describe the available communication interface and features.
-
- Notification Subscription Metadata Resource +
+ notification channel resource
-
+
An RDF document [RDF11-CONCEPTS] - that includes metadata about the capabilities of a notification channel. + that includes information about the capabilities of a notification channel.
subscription resource
@@ -509,59 +509,62 @@

Issue: Solid Notification Vocabulary and

Discovery

-

The following properties are used for the discovery of a notification channel and its capabilities:

+
+

Notification Channel Discovery

+
+ -
-
feature
-
feature predicate denotes a particular feature of a notification channel (Notification Features).
-
notificationChannel
-
notificationChannel predicate denotes that a resource has a notification channel.
-
subscription
-
subscription predicate denotes a subscription resource associated with a notification channel (Subscription).
-
type
-
type predicate (rdf:type) denotes the subscription type (Subscription).
-
+ -
-

Issue: Notification Subscription Metadata Discovery

-
-

The specific mechanism defining the discovery of the Notification Subscription Metadata Resource is under consideration: issues/58.

+

+ + + Servers + MUST accept requests on the Notification Channel Resource when the value of the Accept header indicates a preferred representation in application/ld+json [JSON-LD11]. + + +

+ +

The following properties are used for the discovery of a notification channel and its capabilities:

+ +
+
feature
+
feature predicate denotes a particular feature of a notification channel (Notification Features).
+
notificationChannel
+
notificationChannel predicate denotes that a resource has a notification channel.
+
subscription
+
subscription predicate denotes a subscription resource associated with a notification channel (Subscription).
+
type
+
type predicate (rdf:type) denotes the notification channel type (Notification Channel).
+
+ +

Servers MUST include the @context field as an array containing the value https://www.w3.org/ns/solid/notification/v1 in the JSON-LD representation of a Notification Channel Resource.

-
+
-

- - - The server - MUST be capable of serializing the - Notification Subscription Metadata Resource as - Turtle [TURTLE] - or JSON-LD [JSON-LD11]. - - -

+
+

Notification Channel Conformance

+
-

Turtle Serialization

+

A Notification Channel has the following properties:

-

- - When serializing the Notification Subscription Metadata Resource as Turtle, - every notify:notificationChannel definition - MUST - materialize an rdf:type triple, indicating the channel type. - -

+
    +
  • At least one notify:notificationChannel property whose object describes a notification channel.
    • +
  • At least one rdf:type property whose object is notify:NotificationChannel.
    • +
  • Zero or more notify:feature property values (Notification Features).
    • +
  • Zero or one notify:subscription property value (Notification Subscription).
    • +
-

- A sample representation of this resource might include the following: -

+

+ Sample representations of the Notification Channel Resource might include the following: +

-
-

- Example: Representation of a Notification Subscription Metadata Resource. -

+
+

+ Example: Representation of a Notification Channel Resource. +

- 
Content-Type: text/turtle
+                        
Content-Type: text/turtle
 
 @prefix notify: <http://www.w3.org/ns/solid/notifications#> .
 
@@ -574,28 +577,15 @@ 
Turtle Serialization

   notify:feature notify:state, notify:rate, notify:expiration .
 

 
-                    
TURTLE serialization of a Notification Subscription Metadata Resource

-
+
Turtle serialization of a resource including notification channel information.
+
-

JSON-LD Serialization

+
+

+ Example: Representation of a Notification Channel Resource. +

-

- - When serializing the Notification Subscription Metadata Resource as JSON-LD, - the @contextfield MUST - be an array containing the value https://www.w3.org/ns/solid/notification/v1. - In addition, for every notificationChannel definition, - the Subscription Metadata Resource MUST - materialize a type field, indicating the channel type. - -

- -
-

- Example: Representation of a Notification Subscription Metadata Resource. -

- - 
Content-Type: application/ld+json
+                        
Content-Type: application/ld+json
 
 {
   "@context": [
@@ -609,8 +599,10 @@ 
JSON-LD Serialization

   }]
 }

 
-                    
JSON-LD serialization of a Notification Subscription Metadata Resource

-
+
JSON-LD serialization of resource including notification channel information.
+
+
+
@@ -983,6 +975,8 @@

Normative References

Linked Data Notifications. Sarven Capadisli; Amy Guy. W3C. 2 May 2017. W3C Recommendation. URL: https://www.w3.org/TR/ldn/
[OAUTH-POP-KEY-DISTRIBUTION]
OAuth 2.0 Proof-of-Possession: Authorization Server to Client Key Distribution. J. Bradley; P. Hunt; M. Jones; H. Tschofenig. IETF. 5 March 2015. Internet Draft (work in progress). URL: https://datatracker.ietf.org/doc/draft-ietf-oauth-pop-key-distribution/
+
[POWDER-DR]
+
Protocol for Web Description Resources (POWDER): Description Resources. Phil Archer; Kevin Smith; Andrea Perego. W3C. 1 September 2009. W3C Recommendation. URL: https://www.w3.org/TR/powder-dr/
[RDF-SCHEMA]
RDF Schema 1.1. Dan Brickley; Ramanathan Guha. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf-schema/
[RDF11-CONCEPTS]