Solid Protocol
-Version 0.9.1 Editor’s Draft, 2022-12-26
+Version 0.9.1 Editor’s Draft, 2022-12-31
More details about this document
@@ -240,7 +240,7 @@Version 0.9.1 Editor’s Draft, 2022-1
- Modified
-
+
@@ -1070,32 +1070,21 @@ Live Update
Solid Notifications Protocol
-
- Entities in a Solid ecosystem use the
- Solid Notifications Protocol
- to communicate about changes affecting a resource.
-
+ Entities in a Solid ecosystem use the Solid Notifications Protocol to communicate about changes affecting a resource.
-
- Servers MUST implement the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL].
-
+ Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Resource Server to enable clients to discover subscription resources and notification channels available to a given resource or storage.
-
- Clients MUST implement the Solid Notifications Protocol[SOLID-NOTIFICATIONS-PROTOCOL].
-
+ Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Subscription Server to process and produce instructions for subscription requests.
+
+ Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Notification Sender to produce and send messages to a Notification Receiver.
+
+ Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Notification Receiver to receive and process messages that conform to a notification channel type.
The following is non-normative.
-
- The Solid WebSockets API (Unofficial Draft)
- [SOLID-WEBSOCKETS-API]
- has been the common notification protocol for many years. That draft does not include an authentication mechanism,
- and therefore this Protocol has transitioned to require the Solid Notifications Protocol.
-
+ The Solid WebSockets API (Unofficial Draft) [SOLID-WEBSOCKETS-API] has been the common notification protocol for many years. That draft does not include an authentication mechanism, and therefore this Protocol has transitioned to require the Solid Notifications Protocol.
-
- Existing client and server implementations should begin providing support for the new notification protocol while supporting backwards compatibility, as appropriate.
-
+ Existing client and server implementations should begin providing support for the new notification protocol while supporting backwards compatibility, as appropriate.
@@ -1327,7 +1316,7 @@ Security and Privacy Review
- No.
- Does this specification allow an origin to send data to the underlying platform?
- - No. Resources are described within the framework of HTTP, where some kinds of resources are required to be RDF documents. Servers might be able to redirect to other resources, e.g., the
https:
URLs to file:
, data:
, or blob:
URLs, but no behaviour is defined by this specification.
+ - No. Resources are described within the framework of HTTP, where some kinds of resources are required to be RDF documents. Servers might be able to redirect to other resources, e.g., the
https:
URLs to file:
, data:
, or blob:
URLs, but no behaviour is defined by this specification.
- Do features in this specification allow an origin access to sensors on a user’s device
- No.
@@ -1507,7 +1496,7 @@ Normative References
- [RFC8288]
- Web Linking. M. Nottingham. IETF. October 2017. Proposed Standard. URL: https://httpwg.org/specs/rfc8288.html
- [SOLID-NOTIFICATIONS-PROTOCOL]
- - Solid Notifications Protocol. Aaron Coburn; Sarven Capadisli. W3C Solid Community Group. 09 May 2022. Version 0.1.0. URL: https://solidproject.org/TR/notifications-protocol
+ - Solid Notifications Protocol. Sarven Capadisli. W3C Solid Community Group. 31 December 2022. Version 0.2.0. URL: https://solidproject.org/TR/notifications-protocol
- [SOLID-OIDC]
- SOLID-OIDC. Aaron Coburn; elf Pavlik; Dmitri Zagidulin. W3C Solid Community Group. 28 March 2022. Version 0.1.0. URL: https://solidproject.org/TR/oidc
- [SPARQL11-QUERY]
@@ -1517,7 +1506,7 @@ Normative References
- [W3C-HTML]
- HTML. W3C. 28 January 2021. W3C Recommendation. URL: https://www.w3.org/TR/html/
- [WAC]
- - Web Access Control. Sarven Capadisli. W3C Solid Community Group. 11 July 2021. Draft. URL: https://solidproject.org/TR/wac
+ - Web Access Control. Sarven Capadisli. W3C Solid Community Group. 5 July 2022. Version 1.0.0-cr-1. URL: https://solidproject.org/TR/wac
- [WEBARCH]
- Architecture of the World Wide Web, Volume One. Ian Jacobs; Norman Walsh. W3C. 15 December 2004. W3C Recommendation. URL: https://www.w3.org/TR/webarch/
- [WEBID]
Live Update
Solid Notifications Protocol
- Entities in a Solid ecosystem use the - Solid Notifications Protocol - to communicate about changes affecting a resource. -
+Entities in a Solid ecosystem use the Solid Notifications Protocol to communicate about changes affecting a resource.
-- Servers MUST implement the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL]. -
+Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Resource Server to enable clients to discover subscription resources and notification channels available to a given resource or storage.
-- Clients MUST implement the Solid Notifications Protocol[SOLID-NOTIFICATIONS-PROTOCOL]. -
+Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Subscription Server to process and produce instructions for subscription requests.
+ +Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Notification Sender to produce and send messages to a Notification Receiver.
+ +Servers MUST conform to the Solid Notifications Protocol [SOLID-NOTIFICATIONS-PROTOCOL] by implementing the Notification Receiver to receive and process messages that conform to a notification channel type.
The following is non-normative.
-- The Solid WebSockets API (Unofficial Draft) - [SOLID-WEBSOCKETS-API] - has been the common notification protocol for many years. That draft does not include an authentication mechanism, - and therefore this Protocol has transitioned to require the Solid Notifications Protocol. -
+The Solid WebSockets API (Unofficial Draft) [SOLID-WEBSOCKETS-API] has been the common notification protocol for many years. That draft does not include an authentication mechanism, and therefore this Protocol has transitioned to require the Solid Notifications Protocol.
-- Existing client and server implementations should begin providing support for the new notification protocol while supporting backwards compatibility, as appropriate. -
+Existing client and server implementations should begin providing support for the new notification protocol while supporting backwards compatibility, as appropriate.
Security and Privacy Review
https:
URLs to file:
, data:
, or blob:
URLs, but no behaviour is defined by this specification.https:
URLs to file:
, data:
, or blob:
URLs, but no behaviour is defined by this specification.