When using EcdsaSecp256k1RecoverySignature2020, I found additional JSON-LD context to be needed for signing and verifying proofs, in order for properties such as proofPurpose to be expanded.
In the Credentials base context, context for these properties is defined within the context of the proof types like EcdsaSecp256k1Signature2019. In a new proof/signature type, it seems they must be defined again, until there is a new version of the credentials based context that includes the needed properties at the top level. In this PR I reuse the context definitions proof types from JsonWebSignature2020. This appears the same as in the Credentials base context but without using compact URIs for sec: and xsd:.
When using
EcdsaSecp256k1RecoverySignature2020
, I found additional JSON-LD context to be needed for signing and verifying proofs, in order for properties such asproofPurpose
to be expanded.In the Credentials base context, context for these properties is defined within the context of the proof types like
EcdsaSecp256k1Signature2019
. In a new proof/signature type, it seems they must be defined again, until there is a new version of the credentials based context that includes the needed properties at the top level. In this PR I reuse the context definitions proof types from JsonWebSignature2020. This appears the same as in the Credentials base context but without using compact URIs forsec:
andxsd:
.