Comparison with ESS Access Requests and Grants
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- backend-api-design
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.
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?
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solid/data-interoperability-panel
-
Align with LWS Access Requests and GrantsMay be free again @elf-pavlik claimed this 78 days ago, and no pull request is open. Open
solid/data-interoperability-panel#338 · 11 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
solid/data-interoperability-panel#337 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
solid/data-interoperability-panel#336 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
solid/data-interoperability-panel#335 · 3 comments ·
-
Remove `interop:AccessAuthorization`, `interop:AccessGrant` and `interop:AccessNeedGroup`May be free again @elf-pavlik claimed this 513 days ago, and no pull request is open. Open
solid/data-interoperability-panel#334 · 5 comments · 1 assignee ·
All issues in solid/data-interoperability-panel
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
-
Bug: lockTtlSeconds / lockHeartbeatIntervalSeconds accept non-positive and non-finite valuesPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CopilotKit/CopilotKit#7618 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TencentCloud/Octop#1622 ·
Maintainers usually reply within 1 day
-
Independent PhaseMap objects share and leak their default mode groupingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Bug Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
php/php-src#24121 · 1 comment ·
Maintainers usually reply within 1 day