Tom Haegemans

Ability to use S3 Object Storage as a storage backend

2

### Context With use.id, we currently use a file store as storage backend for our pod server. However, * file stores are not that easy to manage and * managed...

Ensure CSS can run as a stateless container

1

### Context use.id's infrastructure is based on containers. In use.id, we only make use of the storage (aka pods) component of the CSS. It is best practice to make containers...

Inconsistency in identifiers for apps: WebIDs and ClientIDs

36

An app in Solid needs to have an identifier. The spec states that "WebIDs [...] are used as the primary identifier for users and applications." ([Solid Protocol, Section 9.1](https://solidproject.org/ED/protocol#webid)). However,...

Distinction between each of the components required for Solid

4

Hi all, The goal of the Solid standard is to make sure that there is a loose coupling between each of the components required for Solid (e.g. storage, UMA AS,...

Requirement of use.id customers: requiring the user to be logged in to access data

5

When you share data with another WebID (e.g. I share data with use.id/wouter), the party with the other WebID can access my data as long as my store is online...

Integrity of `skos:preflabel` and `skos:prefdefinition`

4

We are currently implementing the interop spec into use.id, but are concerned about relying on `skos:preflabel` and `skos:prefdefinition` of the Access Need Groups to render the UI of the authz...

Multiple authorisation apps per social agent

3

We are setting up a WebID provisioning service (called use.id) and one of our customers has a very interesting use case which would accelerate the adoption of Solid: they provide...