Addressing data cascading
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
Which components are relevant for data cascading eg. spread of information beyond its original intended use, in the Solid ecosystem eg. access control, connectivity, customisation, context, data policies?
How can the Solid ecosystem address mitigate potential misuse or set constraints towards permitted reuse?
..
See also https://dr.amy.gy/chapter3#ccccc
Contributor guide
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
Start by reviewing the issue's questions about data cascading, access control, connectivity, customisation, context, and data policies, along with the linked chapter. Identify which Solid ecosystem components are relevant and document how the ecosystem could mitigate misuse or constrain permitted reuse. Done means producing an agreed analysis or proposal, but no implementation entry point is named.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100