Feedback/suggestions before the final relase of OpenAttestation v4.0

[HJunyuan]

Context

Following earlier discussions in #249 to make the OpenAttestation framework compliant with W3C Verifiable Credentials Data Model v2.0, a new version of the framework has been in the works: OpenAttestation v4.0 (beta)

At a glance

• Documents issued with OA v4.0 now aligns with W3C VCDM v2.0 (DID-issued sample)
• renderMethod now aligns with the upcoming draft of W3C VC Rendering Methods
• For more details, refer to Action 1a, 1b, 1e in 🛠 Improvements to OA v3 to achieve W3C interoperability #249

Feedback or suggestions

This thread serves as a place for anyone to submit feedback or suggestions before the final release of OpenAttestation v4.0. Please start a new comment thread for each topic.

[cxcheng]

The OpenAttestation team has been discussing internally that the proof type "OAMerkleProofSignature2018" under OA v4 data model does not correctly reflect the fact that we are only applying hash of hashes rather than Merkle Tree for our algorithm. As part of our effort to work with W3C and promote our proof method, we feel it is important that we don't mislead regarding Merkle Tree. I am hereby proposing the type "OpenAttestationHashProof2018". Do you have objections on that, or have an alternate name to propose?