Creating this issue to unblock #264, and to continue this thread.

For context, a note is provided in the addition of ownership requirements in #264 that states:

When a server supports multiple storages, there must be complete trust between its owners

Assuming that:

• server in this context is equivalent to a running instance of a solid server (e.g. community-server at https://pod.example)
• support of multiple storages with different owners equates to a typical pod hosting scenario (e.g. https://solidcommunity.net)

In this case, it would be true more often than not that a server with multiple storages does not realize complete trust between the owners of those storages. For example, I have a solidcommunity.net pod, but I do not know the majority of that user population, let alone completely trust them.

If server in this context was meant to uniquely identify scheme, host, and port (e.g. https://justinwb.pod.example/, that may address cases where server represents a storage partitioned by subdomain, but not cases where a server partitions storages by path (e.g. https://pod.example/justin/, https://pod.example/alice/).