Skip to content

Commit b58b0c9

Browse files
committed
Add Quick Notifications
Adds the Solid Quick Notifications Protocol that enables Solid Servers to directly provide clients with notification channels and/or let them negotiate subscriptions using HTTP headers within any GET requests.
1 parent c50a4f9 commit b58b0c9

File tree

4 files changed

+1206
-0
lines changed

4 files changed

+1206
-0
lines changed

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,12 @@ These reports are incubated by the [Solid Notifications Panel](https://github.co
1212
* Editors Draft:
1313
* [Solid Notifications Protocol](https://solid.github.io/notifications/protocol)
1414

15+
### Quick Protocol
16+
* Latest Published Version:
17+
* [Solid Quick Notifications Protocol](https://solidproject.org/TR/quick-notifications-protocol)
18+
* Editors Draft:
19+
* [Solid Quick Notifications Protocol](https://solid.github.io/notifications/quick-protocol)
20+
1521
### Notification Channel Types
1622

1723
The Solid Notification Protocol makes it possible to define [notification channel types](https://solid.github.io/notifications/protocol#notification-channel-types). In order to help with the discovery of notification channel types that can be used with the Solid Notifications Protocol, it is encouraged to register them for maximum global interoperability at [Solid Technical Reports](https://solidproject.org/TR/#notification-channel-type-registry).
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
sequenceDiagram
2+
participant Subscription Client
3+
participant Resource Server
4+
5+
Subscription Client ->> Resource Server: HEAD Resource (topic)
6+
Resource Server ->> Subscription Client: Existing Notifications Channels
7+
Resource Server ->> Subscription Client: Subscription Discovery
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
sequenceDiagram
2+
participant Subscription Client
3+
participant Resource Server
4+
5+
Resource Server -->> Subscription Client: Discovery Response
6+
Subscription Client ->> Resource Server: Subscription Request
7+
Resource Server ->> Subscription Client: Subscription Response (with Notification Channel)

0 commit comments

Comments
 (0)