Missing documentation about interop:accessScenario

[srosset81]

In the specification, there are no explanation or examples about the interop:accessScenario predicate, which can be either interop:PersonalAccess or interop:SharedAccess.

It is only indicated: "Context in which the access group should be presented"

Can it be used by applications to indicate if they want only data owned by user OR also data that has been shared with the user ? (since applications cannot define the scope of the access grants they would need - interop:All or interop:AllFromRegistry -- it could be a way to make this possible ?)

[elf-pavlik]

To be honest I didn't use it in sai-js implementation and don't recall what it was intended for, maybe @ericprud could help?
I think any policies that are enforceable by law not the authorization system would be better handled by ODRL

• Distinction between policies which can be enforced by technology and by law authorization-panel#286
• https://protect.oeg.fi.upm.es/solid-consent/

[ericprud]

I have two, probably mutually-exclusive theories:

1. schemas for shared app data typically have more release-engineering/concensus-building in their development; this flag indicated data that wasn't fit for publish consumption because the creator hadn't done enough homework to make it stable or backwards-compatible
2. something analogous to installing in $HOME/bin/ vs /bin/,.
   Most probably neither of these is correct.