Michael B. Jones
Michael B. Jones
As described in issued #918, I believe this would move us in the wrong direction - towards unnecessary and useless complexity.
@TallTed thanks for explaining the future-dated coupon use case. That motivates why issuanceDate and validFrom would sometimes be different. I can't see it motivating why expirationDate and validUntil would ever...
For context, https://github.com/w3c/vc-jwt/issues/9 (Represent issuance time with "iat" rather than "nbf") is related.
> deprecate `issuanceDate` since the current (v1.1) definition is semantically misleading. > add REQUIRED `issued` that is semantically the same as the `iat` JWT claim. I'd prefer fixing the misleading...
(Adding a comment so that I'm notified of discussion on this issue)
I believe we need to add that using registered JWT claims is the best practice to the JSON Proof Token specification.
Can someone provide a concise description of what the two different headers would be for and would contain (and would not contain)?
I agree that we need to do this analysis.
-1 to "derive", as it's not intuitive usage of the word in context.
This is unnecessary, since it's done elsewhere, as noted above.