We need to add another distinction where the multiple signatures are not chained, which is the default behavior of this PR.
If the document is not signed then we maintain the classic MerkleProof2019 signature.
If the document is already signed, then the next signature hashes the previous signature(s). This requires an update to cert-schema to hold the contexts for the different signature schemes.
For context: https://github.com/w3c-ccg/data-integrity-spec/issues/26 And implementation following https://hackmd.io/@RYgJMHAGSlaLMaQzwYjvsQ/SJoDWwTdK
We need to add another distinction where the multiple signatures are not chained, which is the default behavior of this PR.
If the document is not signed then we maintain the classic MerkleProof2019 signature.
If the document is already signed, then the next signature hashes the previous signature(s). This requires an update to cert-schema to hold the contexts for the different signature schemes.