We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@iherman requested that we more generally specify the enveloped and embedded proof extension mechanisms, and then continue to normatively refer to the securing mechanisms that the WG has defined as RECOMMENDED mechanisms. @msporny clarified some guidelines around doing that.
This issue is being raised to track that concern.
The text was updated successfully, but these errors were encountered:
PR #1403 has been raised to address this issue. This issue will be closed once PR #1403 has been merged.
Sorry, something went wrong.
The issue was discussed in a meeting on 2024-01-03
See github issue vc-data-model#1400.
Brent Zundel: 1400 Clarify embedded proof extension point. also on track with this. expect it to be addressed by EOW.
PR #1403 has been merged, closing.
msporny
No branches or pull requests
@iherman requested that we more generally specify the enveloped and embedded proof extension mechanisms, and then continue to normatively refer to the securing mechanisms that the WG has defined as RECOMMENDED mechanisms. @msporny clarified some guidelines around doing that.
This issue is being raised to track that concern.
The text was updated successfully, but these errors were encountered: