Addition of Delegateable Owner

In the event that there is a single owner of a data pod, and that owner is no longer able to provide authorisations to other parties to access their data, then effectively the data is lost.

This may create issues with the other parties who are reliant on some or all of this data access for their own activities (eg periodicity regulatory reporting).

Adding a second owner may not be considered desirable by the owner, as this seems to convey full access to the data and its management.

Can the specification be extended to include the notion of zero or more delegate owners, who would have no ownership capabilities until a delegation protocol is successfully completed, after which they become owners of the data.

This ensures the data can continue to be made available, as determined by the owners.

The delegation protocol must be part of this specification to ensure uniformity of data pod ownership behaviour.

When elevated to data pod owners, delegate owners must not have the right remove the original owner, but otherwise have full control as per the original owner.

The original owner should be able to return delegate owners to their original state: I.e. return to being the sole owner of the data pod.

In this way, a hospitalised owner can temporarily give away management of their data pod, and then reclaim management once they recover. If they die, then their data still remains accessible and controlled.

Start by reviewing the Solid specification's existing data pod ownership and authorization rules. Define a uniform delegation protocol covering elevation, restrictions on removing the original owner, and returning delegates to their prior state. Done means the specification unambiguously describes these states and transitions.