VC v2.0 Interoperability Report
Verifiable Credentials Data Model v2.0 Interoperability Report
Basic Conformance
| Test Name | Implementer | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| apicatalog.com | Aviary Tech | Digital Bazaar | Gen Digital | Kataru Content VC | MakoLab | OpSecId | Procivis One Core | SpruceID | Trential | VC Issuer Mock | |
| A conforming document MUST be secured by at least one securing mechanism as described in Section 4.12 Securing Mechanisms. |
|
|
|
|
|
|
|
|
|
|
|
| A conforming issuer implementation MUST include all required properties in the conforming documents it produces. |
|
|
|
|
|
|
|
|
|
|
|
| A conforming issuer implementation MUST secure the conforming documents it produces using a securing mechanismdescribed in Section 4.12 Securing Mechanisms. |
|
|
|
|
|
|
|
|
|
|
|
| A conforming verifier implementation MUST perform verification on a conforming document as described inSection 4.12 Securing Mechanisms. |
|
|
|
|
|
❌
|
|
|
|
|
|
| A conforming verifier implementation MUST produce errors when non-conforming documents are detected. |
|
|
|
|
|
❌
|
|
|
|
|
|