Github url

solid

by solid

solid /solid

Solid - Re-decentralizing the web (project directory)

7.5K Stars 345 Forks Last release: Not found MIT License 128 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Solid

Solid Logo

Re-decentralizing the web

Read more about Solid information.

Solid (derived from "social linked data") is a proposed set of conventions and tools for building decentralized Web applications based onLinked Data principles. Solid is modular and extensible. It relies as much as possible on existingW3C standards and protocols.

Solid is made possible by a community of contributors.

Table of Contents

  1. About Solid
  2. Standards Used
  3. Project directory
  4. Contributing to Solid

About Solid

Specifically, Solid is:

  • A tech stack -- a set of complementarystandards anddata formats/vocabularies that together provide capabilities that are currently available only through centralized social media services (think Facebook/Twitter/LinkedIn/many others), such as_identity_, authentication and login, authorization and permission lists,contact management, messaging and notifications, feed aggregation and subscription, comments and discussions, and more.
  • A Specifications documentthat describes a REST API that extends those existing standards, contains design notes on the individual components used, and is intended as a guide for developers who plan to build servers or applications.
  • A set of servers that implement this specification.
  • An ecosystem of social apps,identity providers and helper libraries (such as solid-auth-client) that run on the Solid platform.
  • A community providing documentation, discussion (see thesolid forum), andtalks/presentations.

Standards Used

The Solid platform uses the following standards.

Solid Platform Notes

Solid applications are somewhat like multi-user applications where instances talk to each other through a shared filesystem, and the Web is that filesystem.

  1. The LDP specification defines a set of rules for HTTP operations on Web resources, some based on RDF, to provide an architecture for reading and writing Linked Data on the Web. The most important feature of LDP is that it provides us with a standard way of RESTfully writing resources (documents) on the Web, without having to rely on less flexible conventions (APIs) based around sending form-encoded data using POST. For more insight into LDP, take a look at the examples in the LDPPrimer document.

  2. Solid's basic protocol is REST, as refined by LDP with minor extensions. New items are created in a container (which could be called a collection or directory) by sending them to the container URL with an HTTP POST or issuing an HTTP PUT within its URL space. Items are updated with HTTP PUT or HTTP PATCH. Items are removed with HTTP DELETE. Items are found using HTTP GET and following links. A GET on the container returns an enumeration of the items in the container.

  3. Servers are application-agnostic, so that new applications can be developed without needing to modify servers. For example, even though the LDP 1.0 specs contains nothing specific to "social", many of the W3C Social Work Group'sUser Stories can be implemented using only application logic, with no need to change code on the server. The design ideal is to keep a small standard data management core and extend it as necessary to support increasingly powerful classes of applications.

  4. The data model is RDF. This means the data can be transmitted in various syntaxes like Turtle,JSON-LD (JSON with a "context"), orRDFa (HTML attributes). RDF is REST-friendly, using URLs everywhere, and it provides decentralized extensibility, so that a set of applications can cooperate in sharing a new kind of data without needing approval from any central authority.

Project directory

Implementing

Community

Contributing to Solid

Get a WebID

In order to try out some of the apps built using Solid, you will need typically an identity on some solid server. There are two forms of authentication we use, and so two types of account.

WebID-OIDC

This uses OpenID Connect to give you a WebID. It involves signing in with a password at your chosen identity provider, such as (2018/2) solid.community.

WebID_TLS

A WebID profile from one of the Solid-compliant identity providers, such as databox.me,

With WebID-TLS, you will need to make a WebID browser certificate from the above profile (this is usually created when you sign up for a WebID profile account, but it only works on Firefox at the moment (2018)).

Running a server

Additionally, to get started with developing for the Solid platform, you'll need:

  1. A Solid-compliant server.

  2. While not required, an understanding of RDF/Turtle principles andLinked Data Platform concepts will help you understand the general workflow.

Solid Project Workflow

To contribute to Solid development, and to bring up issues or feature requests, please use the following workflow:

  1. Have a question or a feature request or a concern about the Solid framework, or on one of its servers? Open an issue onsolid/solid (this repo here).

Have an issue with the Solid spec specifically? Open an issue onsolid/solid anyway. And then, as a result of discussion, if it's agreed that it is actually a Spec issue, it will be moved to

solid-spec

. 3. The individual solid/solid issues can coordinate and track component/dependent issues on the various affected Solid servers, apps, and so on.

Places to chat

https://github.com/solid/information#solid-conversations

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.