solid/data-interoperability-panel

2021-12-07 Agenda: https://hackmd.io/iVlburEVSRmhFxAtjtmAsw | Code of Conduct: https://github.com/solid/specification#code-of-conduct

elf Pavlik

@elf-pavlik

I captured above in solid/data-interoperability-panel#109 which now would be preferable place to follow up.

elf Pavlik

@elf-pavlik

@justinwb when someone would create ReferencedDataGrant with scope AllInstancesfor DataRegistration xyz, rather thatn creating regular Data Grant for xyz?
I understand ReferencedDataGrant with scope InheritInstances since it relies on which instances are selected in "parent" grant. Actually I don't see reason to use ReferencedDataGrant in any other case other than with InheritInstances.

Justin Bingham

@justinwb

@elf-pavlik yeah i think would could probably tighten the scope of those shapes up more

they were a bit fluid as we kept optimizing the grant structure which is why we probably had a more liberal schema

elf Pavlik

@elf-pavlik

@justinwb when someone would create ReferencedDataGrant with scope AllInstancesfor DataRegistration xyz, rather thatn creating regular Data Grant for xyz?
I understand ReferencedDataGrant with scope InheritInstances since it relies on which instances are selected in "parent" grant. Actually I don't see reason to use ReferencedDataGrant in any other case other than with InheritInstances.

@justinwb and :point_up:

elf Pavlik

@elf-pavlik

I'm trying to visualize different data grants:

AllInstances

InheritSelected

elf Pavlik

@elf-pavlik

SelectedInstances

green - can access
gray - doesn't even know about
red - has link but can't access

tomorrow i'll play with remote data registrations

elf Pavlik

@elf-pavlik

I wonder how others feel about changing Referenced (shape trees, data grants) to Related? This would better fit established concepts like relational database, entity-relationships etc.
I know naming things is hard! I have impression that in this case someone used st:references in Shape Trees spec and it bubbled up from there.

Justin Bingham

@justinwb

yeah that’s exactly where it came from (that it was represented a reference / virtual tree)

main issue i would have with related is that there is still an implied (albeit) virtual hierarchy and i don’t know that related conveys that well enough.

Justin Bingham

@justinwb

@justinwb when someone would create ReferencedDataGrant with scope AllInstancesfor DataRegistration xyz, rather thatn creating regular Data Grant for xyz?
I understand ReferencedDataGrant with scope InheritInstances since it relies on which instances are selected in "parent" grant. Actually I don't see reason to use ReferencedDataGrant in any other case other than with InheritInstances.

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.

we should walk through some examples on tuesday that i’ve got broken out in turtle

elf Pavlik

@elf-pavlik

Sounds great @justinwb. Let's take a look at your examples tomorrow. I'll start HackMD with agenda

pad for tomorrow: https://hackmd.io/17e4EC9CTUGRwA6fR_-5LQ

Justin Bingham

@justinwb

:+1:

fyi - was a bit late getting last weeks minutes up - see here: solid/data-interoperability-panel#111

elf Pavlik

@elf-pavlik

https://solid.github.io/data-interoperability-panel/specification/#datamodel-remote-agent-data-registration

<#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+           
}

Justin Bingham

@justinwb

https://hackmd.io/cqvolbxhQbyOxYhz7KaSwQ?view

elf Pavlik

@elf-pavlik

@justinwb sorry for interjecting i'll create issue describing it in detail

Justin Bingham

@justinwb

no worries!

elf Pavlik

@elf-pavlik

https://solid.github.io/data-interoperability-panel/specification/#datamodel-referenced-data-grant

q+ re: scopes other than InheritInstances

Dmitri Zagidulin

@dmitrizagidulin

(have to drop; thanks all!)

elf Pavlik

@elf-pavlik

@justinwb netlify needs to be updated to match how authentication-panel works - run build.sh

elf Pavlik

@elf-pavlik

I'm merging those old PRs into archive, @justinwb could you please take a look at those two stale branches? https://github.com/solid/data-interoperability-panel/branches/stale

elf Pavlik

@elf-pavlik

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 main and 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

Justin Bingham

@justinwb

oh yeah lets switch it

sorry just seeing these other @ s

@elf-pavlik deleted both stale branches :white_check_mark:

elf Pavlik

@elf-pavlik

pad for today: https://hackmd.io/IJclKsllSqCsAW4y46z_Pg

elf Pavlik

@elf-pavlik

elf Pavlik

@elf-pavlik

solid/data-interoperability-panel#113

hRicklefs

@hRicklefs

One for next week but I would be curious to understand how the conversation we just had relates to what you talk about in the authorisation panel.

1 reply

@elf-pavlik could you send me and @JulietteCarter an invite for the meeting you mentioned to talk about the interfaces.

elf Pavlik

@elf-pavlik

I'm going to send each one of you a direct message

elf Pavlik

@elf-pavlik

I hope we can merge this primer PR on Tuesday solid/data-interoperability-panel#119 -- rendered preview

elf Pavlik

@elf-pavlik

Proposal of small change to Create Data Instance which will should allow to keep IRIs opaque for the client solid/data-interoperability-panel#120

hRicklefs

@hRicklefs

On leave today so wont join later on

Justin Bingham

@justinwb

enjoy the time off @hRicklefs !

Justin Bingham

@justinwb

@/all HackMD for today - please add as you like - https://hackmd.io/@hAlm_W2-T-q16baquNyRXg/H1oZNqmqu

Justin Bingham

@justinwb

@elf-pavlik have provided some feedback on solid/data-interoperability-panel#119

elf Pavlik

@elf-pavlik

thanks @justinwb! I've just addressed your feedback

elf Pavlik

@elf-pavlik

@/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

Eric Prud'hommeaux

@ericprud

example PR with pr-preview links in first comment: w3c/lds-wg-charter#73

Where communities thrive

People

Repo info

Activity