Kristina
Kristina
@TallTed Thank you for the feedback. I will be more careful when linking to the external resources.
The use case is the user has to upload all of the credentials to a portal. I don't file issues just for fun. And I don't think you would tell...
> With current PE I can already create a definition that literally does what Kristina is asking for. The protocol would allow for it. The only thing I need to...
suggested action would be: in the data-model, potentially mention generic guidance, not specific to any concrete method. if any of the securing specs decide to handle concrete methods (if any)...
also would be valuable to separate encryption at the presentation layer (more use-cases), from the encryption at the credential layer which is implied by the title of this issue.
one week since marked pending close
[editor's call] diffence in approach - vc-jwt has `exp` claim which is recommended to be used, while data integrity does not have a claim for a proof expiration date. suggested...
(discussion would benefit from a use-case that shows a need to expire a VP)
Personally, I don't think the guidance should go beyond > they are meant to be extremely short lived, and bound to a challenge provided by a verifier Details are up...
agreed that this topic should be addressed in the securing specs (vc-jwt and data integrity)