-
Notifications
You must be signed in to change notification settings - Fork 13
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
Update language to align with v2 resolutions #38
Comments
we should agree that iat/exp of VC-JWT are validity of the VC-JWT signature and are different from ValifFrom/ValidUntil that are validity of the data in the Credential #39 (comment) |
@Sakurann I agree they are different, I presented on this at TPAC. Basically:
changing the name of the left hand side does not change the alignment of intention:
|
I agree with
I dont with
ValidFrom and validUntil should not be mapped to any JWT Claim and used as-is. and exp JWT Claim should be used for the JWS signature validity. Please see my proposal in issue #4 |
See 1.1 production rules: https://w3c.github.io/vc-jwt/#in-addition-to These are the rules for 1.1... We can of course change them or not implement a similar mapping for 2.0. |
No longer needs, especially when #88 is merged |
issuanceDate
,validFrom
,validUntil
The text was updated successfully, but these errors were encountered: