-
Notifications
You must be signed in to change notification settings - Fork 116
Allow string values in JOSE properties in base JSON-LD context #1275
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
Comments
@msporny is correct that JOSE |
The issue was discussed in a meeting on 2023-09-14
View the transcript2.1. Allow string values in JOSE properties in base JSON-LD context (issue vc-data-model#1275)See github issue vc-data-model#1275. Brent Zundel: manu can you comment on this issue? Manu Sporny: This came up when we were processing fix ups to the base context. We were getting it in the proper shape to go into CR. We noticed that Orie had set some of the jwk properties to let them be URL, where the JWK doesn't allow that. Michael Jones: I agree with manu that "kid" needs to be able to be any string. Manu Sporny: I can take it. It will likely be objected, though. Can someone from the vc-jose-cose world do it? Michael Jones: I can review the PR. Brent Zundel: Assigning to both manu and selfissued. Michael Jones: manu, please ping me out of band. Brent Zundel: Any more comments? (silence). |
PR #1325 failed to achieve consensus, and it's unlikely the the current group would ever achieve consensus on such a PR, closing. |
The current base JSON-LD Context requires certain JOSE/JWK properties to be URLs by setting the
type
property to the value of@id
(which, in JSON-LD, effectively means: "This value MUST be a URL").For example, this exists in the current base JSON-LD Context:
@selfissued confirmed in https://github.com/w3c/vc-data-model/pull/1259/files/2414ad34c95734ca0e8c65202a8294bf4639d189#r1309411981 that "kid" does not necessarily have to be a URI.
There are multiple JOSE/JWK properties that follow this pattern and this issue is to track the concern that this seems to not be aligned with what the JOSE/JWK specifications say. If we are going to define JOSE/JWK properties in the base context, we should make sure that they're completely aligned w/ the JOSE/JWK specifications to increase interoperability.
The text was updated successfully, but these errors were encountered: