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.

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

Add language for handling implementation mismatches #181

Closed
decentralgabe opened this issue Jul 25, 2023 · 1 comment · Fixed by #189
Closed

Add language for handling implementation mismatches #181

decentralgabe opened this issue Jul 25, 2023 · 1 comment · Fixed by #189
Assignees
Labels
enhancement New feature or request pre-cr

Comments

@decentralgabe
Copy link
Collaborator

What if a credential uses JSON Schema Draft 7, enabled by this specification, but an implementer who sees such a VC only supports draft 2020-12?

Let's add some language on what should practically occur during implementation gaps.

@decentralgabe decentralgabe added the enhancement New feature or request label Jul 25, 2023
@decentralgabe decentralgabe self-assigned this Jul 25, 2023
@decentralgabe
Copy link
Collaborator Author

My gut is to say "validation failed" but a binary is not really good enough. Three statuses would be preferable, but that may be adding too much complexity to the spec. Keeping a binary pass/fail could work with a reason field as well.

I am wondering if there's an analog to be made to checking a credential's status but the status list cannot be resolved for some reason. Is this behavior just undefined? What guidance is there for verifiers?

Curious on other's thoughts: @msporny @OR13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pre-cr
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant