solid / solid/data-interoperability-panel

Comparison with ESS Access Requests and Grants

Open
#317 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
58
Forks
18
PR merge metrics
No merged PRs in 30d

Description

I was just reading https://docs.inrupt.com/ess/latest/security/access-requests-grants/ and it seemed that ESS access requests:

An agent sends an access request to the resource owner. In ESS, the access request is serialized as a VC.

are quite similar to this panel's Data Needs:

A given Social Agent or Application expresses their access needs by providing one or more Access Need Groups to the Social Agent controlling the data they require access to.

And that ESS access grants:

For an approved request, ESS creates an access grant with an approved status.

are quite similar to this panel's Access Authorizations:

An Access Authorization records the decision of a Social Agent to grant access to some portion of data in their control to another Agent.

Given the existence of these two apparently similar systems within our project's community, would maybe it make sense to create a library that abstracts the differences and can deal with both transparently?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the ESS access requests and grants documentation with the Data Interoperability Panel specification sections on Data Needs and Access Authorizations. The issue does not name files, tests, or an implementation entry point. Done would require a settled scope for whether a transparent abstraction library is wanted and how the two systems' differences should be handled.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.