solid / solid/data-interoperability-panel

Clearly define how access modes in data grant apply to the data in data registration

Open
#159 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data-authorization
Dominant language
Bikeshed
Stars
58
Forks
18
PR merge metrics
No merged PRs in 30d

Description

We should clarify if we will use Create, Update and Delete access mode. I think we should use Create if we want to allow creation of new data instances, which means currently SelectedInstances scope would not allow Create as valid access mode.

Having shape validation in place, distinction between Update and Delete also becomes practical. Resource can't be set to empty by Update since it would validate against the shape.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the specification's definitions of access modes, data registration, and scopes. Resolve whether Create, Update, and Delete apply to data registration and how SelectedInstances interacts with Create; done means the specification clearly states these rules and distinguishes Update from Delete under shape validation.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.