Goal here is to review the proof structure. The problem is that the proof is used for the input (by putting the certificate store) and the output (by putting the signature)
The main idea is to use proof only for the signature, and move the proof input into another structure (named credentialProof ... not good but can review)
By doing this, we can make sure the schema works for the input :)
List of changes:
in the schema, proof has been renamed to credentialProof
in the signature (w3c proof field)
the input has been removed
the signature has been flatted
proof.signature.proof is now proof.proofs
proof.signature.privacy.obfuscatedData is not proof.privacy.obfuscated
rename v3 OpenAttestationDocument to OpenAttestationCredential
rename OpenAttestationDocumentWithIssuer to OpenAttestationCredentialWithInnerIssuer
Goal here is to review the proof structure. The problem is that the proof is used for the input (by putting the certificate store) and the output (by putting the signature)
The main idea is to use
proofonly for the signature, and move the proof input into another structure (named credentialProof ... not good but can review)By doing this, we can make sure the schema works for the input :)
List of changes: