2021-12-07 Agenda: https://hackmd.io/iVlburEVSRmhFxAtjtmAsw | Code of Conduct: https://github.com/solid/specification#code-of-conduct
@justinwb when someone would create
ReferencedDataGrantwith scopeAllInstancesforDataRegistrationxyz, rather thatn creating regularData Grantfor xyz?
I understandReferencedDataGrantwith scopeInheritInstancessince it relies on which instances are selected in "parent" grant. Actually I don't see reason to useReferencedDataGrantin any other case other than withInheritInstances.
InheritInstances is definitely the most important case, but even when presenting AllInstances, there’s a difference in how a root (e.g. project) grant and the behavior of types (like tasks) that inherit based on the root being selected.
<#RemoteAgentDataRegistration> {
a [interop:RemoteAgentDataRegistration] ;
interop:registeredBy IRI ;
interop:registeredWith IRI ;
interop:registeredAt xsd:dateTime ;
interop:updatedAt xsd:dateTime ;
interop:hasDataRegistration IRI ;
interop:fromAgent IRI ;
interop:registeredShapeTree IRI ;
interop:hasAccessReceipt IRI* ;
interop:satisfiesDataGrant IRI+
}InheritInstances
I'm merging those old PRs into archive
done https://github.com/solid/data-interoperability-panel/pulls
@justinwb I think we should change default branch to
mainand prune branches in the repo https://github.com/solid/data-interoperability-panel/branches
this repo seems to be one of the last ones still using master as the base branch
1 reply
@/all HackMD for today - please add as you like - https://hackmd.io/@hAlm_W2-T-q16baquNyRXg/H1oZNqmqu
I added couple of things, rather than trying to resolve them during the call we could pick some actions (self-assign on those issues) and resolve them over the next couple of days
