User Choice considerations
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The spec may leave the user with several choices:
- ScenarioSets -> the equivalent credential_query is a recommended user choice in OpenID4VP
- ElementLogic -> the equivalent claims_query is not a user choice in OpenID4VP
There is currently no mention of the user in the spec. I propose that we add guidance on this.
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
Compare the ScenarioSets and ElementLogic cases with the referenced OpenID4VP credential_query and claims_query behavior. Identify where the specification should explain user choice, then add guidance that clearly distinguishes the two cases and run the specification's existing checks, if available, to confirm the wording is consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100