Joachim Van Herwegen

One other thing I just thought of, could you also update the documentation at https://communitysolidserver.github.io/CommunitySolidServer/latest/architecture/features/notifications/ with some explanation about how the architecture of this one differs from the others?

The idea behind the interface of the indexed storage is to have something similar to what you would have in a SQL store, with the idea of at some point...

> The use case I initially wrote this for was to load an array of keys per account from the config with the SeededInitializer. How would you do this then?...

You could then have an inbetween KeyManager class or something like that, that takes an array of keys as input together with an accountId. The IndexedStorage is expected to be...

> Sure, should be possible indeed now that we have better type-checking. I had a look at this, and I've discovered there apparently is no type checking on variables, so...

> Do you see an easy way to support type-checking for variables? The issue is here: https://github.com/LinkedSoftwareDependencies/Components.js/blob/ad52da8afc2340ddc63e8a45c4d560e11ecb3ceb/lib/preprocess/parameterproperty/ParameterPropertyHandlerRange.ts#L94-L97 The type check simply always succeeds in the case of variables, even if...

> I would have to check what the connections are specifically to get it there. Currently the `ConfigConstructorPool` is the deepest class that has access to the variables. To reach...

Just to throw in my 2 cents: Whichever solution or changes are being done, I think it's important that there is only 1 "final" configuration serialization. Otherwise it becomes much...

> For reference, something like #13 would solve most of the current usability problems I think. One issue with that which Jackson also mentions is that it forces people to...

My only experience is with N3 reasoning in the past. When I made a reasoner I used the terms permise and conclusion instead of antecedents and consequences. Specifically in N3...