Solid mini-series: 2. classes of products
by Elf Pavlik
The classes of products defined in the Solid CG technical reports and how they work together.
Video
Transcript
The Solid Community Group reports define compact and focused classes of products.
Let's examine how they can be used together in various implementations and deployments.
In our scenario, we will imagine a standards organization with a group called Pumpkin Community Group, which has multiple participants. The organization provides various web applications and web storage for the groups.
Since Solid allows every user to use an application of their choice, we also have various applications, each accessing data on Pumpkin Community Group pod, specifically the issue tracker.
If we look closely at the web storage hosted by this standards organization, we can distinguish the pods from the identity provider. Further, we can distinguish components that implement specific classes of products from various Community Groups reports.
The Resource Server implements requirements from Solid Protocol, Solid Notifications Protocol, and OAuth2.
The Authorization Server implements requirements from OAuth2, User-Managed Access (UMA2) and Solid-OIDC. The Subscription Server and Notification Sender implement requirements from the Solid Notifications Protocol.
With additional requirements depending on supported channel types.
OIDC Provider implements requirements from OpenID Connect and Solid-OIDC.
Also, IDP can implement FedCM, which is its own spec which is being worked on in the FedID Working Group.
Similarly, we can take a look at the example of a Progressive Web Application.
The Solid Client implements requirements from Solid Protocol. The OIDC Client implements requirements from Solid-OIDC, OpenId Connect, OAuth2, and User-Managed Access (UMA2). Notification Discovery Client, Notification Subscription Client, and Notification Receiver all implement requirements from the Solid Notifications Protocol, again with additional requirements depending on supported channel types.
and SAI Application is defined in Solid Application Interoperability spec.
Solid community participants developed proprietary and open-source implementations, including reusable packages in various programming languages. An active effort is underway to compile a dataset of all those efforts, which can be used by multiple directory apps that offer different presentations of that information.
