Slightly reword the text on status management for wallet attestation
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We currently have this text in VCI:
status: OPTIONAL. Status mechanism for the Wallet Attestation as defined in [I-D.ietf-oauth-status-list]
I would propose to slightly adjust this to
status: OPTIONAL. Status mechanism for the Wallet (client), using the status mechanism as defined in [I-D.ietf-oauth-status-list]
We don't really care about the validity of the token itself, but about the statement (in the scope of that wallet instance to issuer relationship) that it is a valid client/wallet instance we are interacting with. We shouldn't really care about the lifetime of the token itself - this wording attempts to make that a bit clearer.
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 in the VCI specification text containing the status field and compare the current wording with the proposed wording in this issue. Update the description to clarify that the mechanism concerns the Wallet client while retaining the status-list reference; done means the revised text appears accurately in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100