-
Notifications
You must be signed in to change notification settings - Fork 3
Solid Environment & Glossary
Glossary of Common terms used in the solid environnement. You can also see https://github.com/solid/vocab/tree/specification-terms
- ACL : Access Control List
- CRUD : Create, Read, Update, Delete (in solid used in conjonction with a HTTP RESTful API)
- CSS : Community Solid Server
- DPoP : Demonstration of Proof-of-Possession
- ESS : Enterprise Solid Server
- HTML : Hyper Text Markup Language
- IdP : WebID Identity Provider (see also OIDC Provider)
- Interoperability
- LDP : Linked Data Provider
- Linked Data
- NSS : Node Solid Server
- OP : OIDC Provider
- pod
- PSS : PHP Solid Server
- RDF : Resource Description Framework
- solid-server
- solidos (used to be mashlib) : web app used to display linked data (pod data's or external linked data) implemented by default in NSS
- solid protocol : set of rules relative to solid server implementation and data interoperability
- solid specifications :
- solid Technical report
- SPARQL Query Language for RDF
- Store, kb ... : graph representation of linked data in computer memory
- turtle, JsonLD, RDFa : RDF syntax notation used to describe linked data
- W3C : World Wide Web Consortium (elaborates recommendations and specifications)
- WAC : Web Access Control
- WebID : Web Identity
- WPS : WebSocket Pub/Sub (notifications)
- Tim Berners Lee presentation at Oxford University https://www.w3.org/2023/Talks/0310-intro-solidos-tbl/intro-to-solidos.html#(1)
- solid project
- https://www.inrupt.com/videos
https://github.com/CommunitySolidServer/tutorials/blob/main/getting-started.md
- a pod is a storage place linked to a WebID : ex: https://solidos.solidcommunity.net/profile/card#me
- a pod is a web server
- a pod can contain any type of data (linked data, text, music video, ....)
- pod's are stored on a Solid server.
-
a solid server is accessible through a url : example the community solid server https://solidcommunity.net
-
a solid server can be an IdP (identity provider = provider of WebID's), a LDP (linked data provider = pod provider) or both
-
Solid servers should be interoperable. This means that a solid app should works on pod's from whatever server is used.
-
example of server
- NSS : node-solid-server IdP+LDP open-source. solidcommunity.net is using NSS
- CSS : community-solid-server IDP+LDP open-source
- PSS : IDP+LDP open-source
- ESS : enterprise-solid-server developped by inrupt
- ...
FOSDEM presentation by Noël de Martin https://fosdem.org/2023/schedule/event/sovcloud_from_zero_to_hero_with_solid/
Are accessed via authenticated REST API following the Solid protocol
Linked data are managed with the use of RDF libraries (rdflib.js, N3, ..)
- SolidOS is a default solid web app to access solid data on solid-server whose resources/container can be fetched on Unix like file-system
- NSS allways support SolidOS and CSS with file-system (example: CSS with mashlib recipe)
https://forum.solidproject.org/t/migrating-centrally-stored-user-data-to-solid-pods/6423/8