Missing documentation about interop:accessScenario
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the specification text defining interop:accessScenario and the related access-grant terms. Compare the intended meanings of interop:PersonalAccess and interop:SharedAccess, then document examples and clarify whether the predicate can distinguish user-owned data from data shared with the user. Done means the specification explains the predicate and its practical scope clearly.
Written by the indexing model from the issue text.
Description
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 ?)
- 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 79 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 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 514 days ago, and no pull request is open. Open
solid/data-interoperability-panel#334 · 5 comments · 1 assignee ·
-
New `interop:ApplicationDataGrant` typeMay be free again @elf-pavlik claimed this 514 days ago, and no pull request is open. Open
solid/data-interoperability-panel#333 · 4 comments · 1 reaction · 1 assignee ·
All issues in solid/data-interoperability-panel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
MicrosoftLearning/PL-400_Microsoft-Power-Platform-Developer#231 ·
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
VenetoStato/giorgio#6 ·
-
specification
Difficulty 1/5 Under an hour Newbie friendliness 85/100
WICG/webmonetization#754 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linagora/twake-on-matrix#3446 ·
Maintainers usually reply within 3 days
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days