Implement solid service support

[Xuanwo]

FWIW...

Solid is w3c standard for enabling interoperable read-write web, that enables storage decoupled, decentralized web applications.

It's interaction model has two kinds of resources:

1. Containers: analogous to directory. Has containment rdf gaph as their representations.
2. Non containers: Any other rdf or non rdf resources.

It also supports notion of auxiliary resources.

Standardizes following operations:

1. HEAD, GET, PATCH, PUT, DELETE on any resource.
2. POST on container resource to create children.

It's PUT allows creating non existing parent containers automatically.

It standardizes uri slash semantics too.

Along with above, it standardizes decentralized oidc identity provider, authentication via web-id (one to one), or through oidc flows. And has access control mechanism.

Solid protocol will be w3c recommendation soon (Currently ED, with v0.9). Has few companies (like inrupt, headed by w3c chief himself) already providing enterprize implementations. And exists popular oss implementations. Has growing number of apps. Adopted by few govts for providing decentralized services for their citizens.

Originally posted by @damooo in #403 (comment)

[tisonkun]

@Xuanwo How do we review this issue today?

[Xuanwo]

@Xuanwo How do we review this issue today?

A potential service for the community to consider. Let me add some tag for it.

[gabrielgrant]

Just to clarify: Solid is not (yet) a W3C standard, nor an official draft on the recommendations track. The official list is here: https://www.w3.org/TR/

There is a community group iterating internally on a Solid draft, but the W3C tries to be clear that these are not to be considered endorsed by the W3C. More info about this