You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the creation of the named individual solid:PodOwner to refer to the current pod’s owner and accompanying predicate solid:podOwner, which would allow to declare the aforementioned Pod owner in a standard way would fill a gap in the Solid ecosystem and help answer questions such as the ones raised on Gitter recently.
The text was updated successfully, but these errors were encountered:
ACP talks about a Pod owner that always has Read and Write access to all Access Control Resources.
See: https://github.com/solid/authorization-panel/blob/master/proposals/acp/definitions.md#pod-owner
However, Pod Owner is defined neither by the ACP ontology, nor by the Solid ontology.
I think the creation of the named individual
solid:PodOwner
to refer to the current pod’s owner and accompanying predicatesolid:podOwner
, which would allow to declare the aforementioned Pod owner in a standard way would fill a gap in the Solid ecosystem and help answer questions such as the ones raised on Gitter recently.The text was updated successfully, but these errors were encountered: