You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, the VC (JSON, JSON-LD, JWT) was built using the draft of VCDM, and the field schemaId was added to link the VC schema to the VC instance.
According to VCDM 1.1 (not draft), the schema can be added to the VC as a credentialSchema field.
So, the schemaId must be replaced to the credentialSchema object in all VC types and APIs
Is this a regression?
No
Description
Historically, the VC (JSON, JSON-LD, JWT) was built using the draft of VCDM, and the field
schemaId
was added to link the VC schema to the VC instance.According to VCDM 1.1 (not draft), the schema can be added to the VC as a
credentialSchema
field.So, the
schemaId
must be replaced to thecredentialSchema
object in all VC types and APIshttps://www.w3.org/TR/vc-data-model/#data-schemas
Please provide the exception or error you saw
Please provide the environment you discovered this bug in
Anything else?
No response
The text was updated successfully, but these errors were encountered: