solid / solid/data-interoperability-panel
Should we restrict Social Agent Reigstration discovery to AA of that social agent?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Currently, any application acting on behalf of the End-user (social agent) would be able to discover social agent registrations created for them by other agents (starting from WebID of those agents). Should we restrict it to only AA of that social agent?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file, test, or entry point is named. Start by locating the Social Agent Registration discovery rules and the definitions of the End-user, social agent, and authorisation agent in the specification. Done means resolving whether discovery is restricted and recording the decided access rule in the relevant specification text.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100