openid / openid/OpenID4VC-HAIP
add requirements on transaction data
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 57
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
discussed in the WG. QES probably out of scope since it is eIDAS construct. payments is global. would be worth calling payment type explicitly. will open an issue to discuss implications of mandating any of the types.
from @leecam: "As a datapoint we did implement this without any SE changes. The security assurance is just the same as what you get when asserting the device key for the normal presentation"
will remove this requirement for now and put a placeholder that some of the types are likely to be recommended
Originally posted by @Sakurann in https://github.com/openid/oid4vc-haip-sd-jwt-vc/pull/122#discussion_r1859202119
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 with the transaction-data requirement described in this issue and the referenced discussion in PR #122. Review the WG discussion and the comments about QES, payment types, and recommended types before determining the agreed specification change. Done means the implications are resolved and the corresponding requirement or placeholder is updated, though no file or test is named here.
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