Description
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:
"kid": {
"@id": "https://www.iana.org/assignments/jwt#kid",
"@type": "@id"
}
@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.