Wouter Termont

Yes, I agree. In the end we are just creating an UMA-like AS with a Solid pod as storage backend. But my question was rather: why would we want a...

Not sure I follow you. If a Data Registration is an abstraction of 'which data is in a user's pod' (and how it is organised), it should be able to...

> [@elf-pavlik:] As a matter of fact, [advertising `interop:hasRegistrySet`] only optimizes that rare experience [when the user wants to change their Authorization Agent] by not requiring the user to manually...

> We deliberately did not follow the legacy mechanisms used because they failed to meet the stated problems and goals for security and interoperability. Of ccourse I am all in...

No, supporting SAI is not that simple (it also needs clientside implementation to work with those triples). What @justinwb says is what I've been repeating the past weeks: SAI is...

Yes, big fan of that idea, @elf-pavlik! Not sure about the trees though. I'm more in favour of leaving out the dependence on trees, and only use them as ONE...

True, the SAI spec is rather a hard read (which it need not be): it is too heavily loaded with explanatory tables, schema's and examples to really get the (rather...

> [@ThisIsMissEm] Maybe there's something more like ShapeTrees that could make sense to supersede TypeIndexes? [...] Maybe a "ShapeIndexes" or something? [...] [I]t does seem like you'd want to be...

Specifically, the important questions here are: - (how) is the access receipt sent to the requesting social agent? (to their AA? to their inbox?) - what (if anything) happens upon...

> There's no restriction to how the receipt is transferred, though in this spec we specify hasAccessInbox as discoverable from the webid of the social agent, and would be the...