Following up on the long-term solution for how applications can request access to resources

Hey all,

Thanks for a great meeting today. Hope I didn't take too much time of the
meeting with my issue, but I'm very glad that it is resolved. The work on
v5 is progressing well, and hopefully we have a new beta to share with you
very soon ^_^

There was some questions on how to follow up the long term solution for the
issue, and we at inrupt are proposing the following: To create issues in
the solid-spec repo and label them with application-acl
<https://github.com/solid/solid-spec/issues/143>. This might not be the
ideal solution (e.g. only users with write access to the repo can add the
label), but we think it's the best one right now. Please reply your
criticism in the issue or by replying to this email.

FYI: We've created an issue with the label already: Allow non-owners to
access a shared resource with a web app of their own choice
<https://github.com/solid/solid-spec/issues/142> (well, two if you count
the previous issue as well). This works as an example for how this could
work (and a good issue in and of itself, of course).

At some point we probably will focus the work into one or more repoes, but
we'll see how this progresses.

Thanks again for the meeting, and hope to see you again in two weeks ^_^

BR,
Arne

Received on Thursday, 7 March 2019 16:30:55 UTC