data-interoperability-panel
data-interoperability-panel copied to clipboard
solid
Repository for the Solid Data Interoperability Panel
 To keep #187 focused on Trusted Grants/Consents I will focus on delegation chains here. Currently, we only use delegation where end-user delegates access...
A key element to the success of the application interoperability specification will be applications' ability to adapt to and support successive versions of shapes and shapes trees. To make that...
Version numbering in the shape tree specification may enable easy distinguishing of new vs. old instances. However the meaning of the version number should be made explicit. Pros of version...
From https://gitter.im/solid/data-interoperability-panel?at=6138b630f3449e13a4608150: > I believe that was related to cases where (for example) I grant you access to project 5, with inherited access to project 5’s tasks, and then i...
Handle reverse use case where invitation is used to validate the source of an incoming access request. - Trevor sends an access request to Bob, masquerading with a webid and...
I reference [OWL Property Chains](https://www.w3.org/TR/owl2-primer/#Property_Chains) since they seem to be a formal way of defining some of properties current draft of `interop` vocab proposes. I would like to take for...
In a conversation with @jeff-zucker I realized that the specification should be more explicit in pointing out when data registrations are provisioned (i.e. by the authorization agent during later stages...
The specification should do a better job incorporating requirements of Social Agents and Applications as stipulated by [Solid-OIDC](https://solid.github.io/solid-oidc/): - Incorporate oidcIssuer into the Social Agent profile examples - Reconcile [Client...
Initialize, document, and begin to use a public shape / shape tree repository such as https://github.com/shapetrees/shapetrees.pub.