Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

#442 shoulds could become MUSTs in v3 #443

Open
bumblefudge opened this issue Aug 3, 2023 · 0 comments
Open

#442 shoulds could become MUSTs in v3 #443

bumblefudge opened this issue Aug 3, 2023 · 0 comments
Labels
v3
Milestone
future

Comments

@bumblefudge
Copy link
Collaborator

bumblefudge commented Aug 3, 2023 •
edited

ids being unique NEED to be unique for OIDC4VP implementations to use scopes/RARs as desired, and it feels like this requirement was implicit (at least judging by the UUID examples) so seems like a no-brainer to make this a normative requirement in v3. didn't in 442 so as to remain within errata scope.
@bumblefudge bumblefudge added the v3 label Aug 3, 2023
@bumblefudge bumblefudge added this to the future milestone Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
v3
Projects
None yet
Milestone
future
Development

No branches or pull requests
1 participant
@bumblefudge