solid / solid/data-interoperability-panel
Storage without initial data registration
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
The user's Authorization Agent, as well as other applications, know about storage by way of data registrations. What in the case that a user has a new storage host/pod, but no initial registrations there? (Or similar: in the case of storage from which the last registration is removed)
- How does the user tell the AA about it?
- How does the AA keep track about it until the first registration?
Does something like a private pim:storage triple seem like a useful solution here, or is there already another way by which this is achieved?
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 reviewing how data registrations currently tell the Authorization Agent about storage, then determine whether an existing mechanism covers empty or emptied storage; done requires an agreed way to discover and track storage before its first registration.
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
- 25/100