Skip to content

Conversation

@Sakurann
Copy link
Collaborator

resolves #124

Co-authored-by: Christian Bormann <8774236+c2bo@users.noreply.github.com>
@Sakurann Sakurann requested review from jogu and tlodderstedt March 17, 2025 21:42
Co-authored-by: Torsten Lodderstedt <torsten@lodderstedt.net>
@Sakurann Sakurann requested a review from jogu April 14, 2025 22:17
Copy link
Contributor

@tplooker tplooker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Related to #472 I think we need to merge the language there as how do you know whether the batch you have just received is materially different to the last one, if you are just obtaining new copies of a credential and the claim values are the same why should you be forced to delete the copies you have at the moment?

Copy link
Contributor

@tplooker tplooker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing my review based on above comment, easy to resolve I just think we need to check these PR's are consistent with one and other.

@Sakurann
Copy link
Collaborator Author

Sakurann commented May 5, 2025

WG discussion:

  • credential versioning has been agreed to be tackled in v1.1
  • for 1.0, agreed to close this in favor of section 13.5 already saying something similar

@Sakurann Sakurann closed this May 5, 2025
@Sakurann Sakurann added this to the Final 1.0 milestone Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

How to request new copies of a credential

6 participants