Solid Technical Reports
Living Document,
More details about this document
- This version
- https://solidproject.org/TR/
- Editors
- SarvenCapadisli
- Created
- Published
- Modified
- Feedback
- GitHub solid/specification (pull requests, new issue, open issues)
MIT License. Copyright © 2019–2024 W3C Solid Community Group.
Abstract
Hi! We’re the Solid Community Group (CG) of the W3C. The purpose of this document is to help readers orient themselves with the activities of the Solid CG.
The CG has a charter.
The Solid CG’s technical reports (TR) include specifications, use cases and requirements, best practices and guidelines, primers and notes about the Solid ecosystem.
Work Items
The aims of the Solid project are in line with those of the Web itself: empowerment towards an equitable, informed and interconnected society
. Solid adds to existing Web standards to realise a space where individuals can maintain their autonomy, control their data and privacy, and choose applications and services to fulfil their needs.
The information in these documents may be subject to change, therefore please see each document’s publication status and versions for further details. You are invited to contribute any feedback, comments, or questions you might have.
The Test Suites support the Technical Reports:
| Work Item | Repository | Current Stage |
|---|---|---|
| Test Suite | https://github.com/solid-contrib/test-suite | TBD |
| Specification Tests | https://github.com/solid-contrib/specification-tests | TBD |
Notification Channel Type Registry
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.
To update the registry table an implementer MUST submit a modification request for this index as a pull request at the https://github.com/solid/specification repository, which includes the following information:
- Specification
- The URL of the document that specifies the notification channel type.
- Name
- The name of the notification channel type.
- IRI
- The IRI of the notification channel type.
- Description
- A short English description of the notification channel type.
| Specification | IRI | Description |
|---|---|---|
| EventSourceChannel2023 | http://www.w3.org/ns/solid/notifications#EventSourceChannel2023 | A notification channel type that uses the EventSource Web API. |
| LDNChannel2023 | http://www.w3.org/ns/solid/notifications#LDNChannel2023 | A notification channel type that uses the Linked Data Notifications protocol. |
| StreamingHTTPChannel2023 | http://www.w3.org/ns/solid/notifications#StreamingHTTPChannel2023 | A notification channel type that uses the Fetch API. |
| WebhookChannel2023 | http://www.w3.org/ns/solid/notifications#WebhookChannel2023 | A notification channel type that uses Webhooks. |
| WebSocketChannel2023 | http://www.w3.org/ns/solid/notifications#WebSocketChannel2023 | A notification channel type that uses the WebSocket API. |
Participate
It’s easy to join the CG if you’d like to contribute to the Solid project. Please note that in order to join, you’ll need to request a W3C account if you don’t already have one.
We publish a list of current participants on our W3C page.
The Solid CG conducts all technical work in public, mainly in various repositories of the Solid organisation but also in text chat, periodic teleconferences and face-to-face meetings.
Code of Conduct
Please note that all work and communication within the Solid CG is covered by the Solid Code of Conduct as well as the Positive Work Environment at W3C: Code of Conduct.