Propose reverting issue-credential-v2 and present-proof-v2 to v2.0, removing v2.1 and v2.2 #815
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…emoving v2.1 and v2.2 Signed-off-by: Stephen Curran <swcurran@gmail.com>
TimoGlastra
approved these changes
Feb 17, 2024
TelegramSam
approved these changes
Mar 13, 2024
|
WG agreed to merging |
Signed-off-by: Stephen Curran <swcurran@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposes that we remove v2.1 and v2.2 from these two protocols, as they are not implemented, v2.1 is not easily implemented (and is an edge case), and makes upgrading to V3.0 harder for anyone that does actually implement them. The bottom line is that as far as we know, no one has implemented these versions, and we want it to stay that way.
To make this change, I copy/pasted the RFCs from those defined in AIP 2.0, and then put in any clarifications that were unrelated to the v2.1 and v2.2 changes. The result is (I think) an up to date version of each RFC that reflects the reality and direction of the community.
To be discussed at an upcoming Aries Working Group meeting.