The purpose of this test suite is to demonstrate a path to interoperability for the VC JSON Schema specification. The technologies explored in this test suite are experimental. This document contains the most recent interoperability report for a VC JSON Schema using both `JsonSchema` and `JsonSchemaCredential` types. This report is auto-generated.
Tests passed 2/50 4%
Tests failed 48/50 96%
Failures 48
Tests skipped 4
Total tests 54
These tests were run on
The results of the tests are shown below:
Implementation ⇒
⇓Test Name
|
tbd |
---|---|
2.1 ID - The value MUST be a URL that identifies the schema associated with the verifiable credential. |
❌
|
2.1 The type property MUST be JsonSchema. |
❌
|
3 Implementers MUST provide support for JSON Schema specifications where, in the following table, the required column's value is yes |
🛑
|
3.1.1 The $id MUST be present and its value MUST represent a valid URI-reference |
❌
|
3.1.2, 4 The $schema property MUST be present in each schema |
❌
|
4.2 (Success) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Failure) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Indeterminate) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
Implementation ⇒
⇓Test Name
|
tbd |
---|---|
2.1 ID - The value MUST be a URL that identifies the schema associated with the verifiable credential. |
❌
|
2.1 The type property MUST be JsonSchema. |
❌
|
3 Implementers MUST provide support for JSON Schema specifications where, in the following table, the required column's value is yes |
✓
|
3.1.1 The $id MUST be present and its value MUST represent a valid URI-reference |
❌
|
3.1.2, 4 The $schema property MUST be present in each schema |
❌
|
4.2 (Success) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Failure) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Indeterminate) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
Implementation ⇒
⇓Test Name
|
tbd |
---|---|
2.1 ID - The value MUST be a URL that identifies the schema associated with the verifiable credential. |
❌
|
2.1 The type property MUST be JsonSchema. |
❌
|
3 Implementers MUST provide support for JSON Schema specifications where, in the following table, the required column's value is yes |
🛑
|
3.1.1 The $id MUST be present and its value MUST represent a valid URI-reference |
❌
|
3.1.2, 4 The $schema property MUST be present in each schema |
❌
|
4.2 (Success) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Failure) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Indeterminate) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
Implementation ⇒
⇓Test Name
|
tbd |
---|---|
2.1 ID - The value MUST be a URL that identifies the schema associated with the verifiable credential. |
❌
|
2.1 The type property MUST be JsonSchemaCredential. |
❌
|
2.2 The credentialSubject property MUST contain two properties: type - the value of which MUST be JsonSchema; jsonSchema - an object which contains a valid JSON Schema |
❌
|
2.2 The value of the credentialSchema property MUST always be set to [known json schema] |
❌
|
3 Implementers MUST provide support for JSON Schema specifications where, in the following table, the required column's value is yes |
🛑
|
3.1.1 The $id MUST be present and its value MUST represent a valid URI-reference |
❌
|
3.1.2, 4 The $schema property MUST be present in each schema |
❌
|
4.2 (Success) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Failure) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Indeterminate) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
Implementation ⇒
⇓Test Name
|
tbd |
---|---|
2.1 ID - The value MUST be a URL that identifies the schema associated with the verifiable credential. |
❌
|
2.1 The type property MUST be JsonSchemaCredential. |
❌
|
2.2 The credentialSubject property MUST contain two properties: type - the value of which MUST be JsonSchema; jsonSchema - an object which contains a valid JSON Schema |
❌
|
2.2 The value of the credentialSchema property MUST always be set to [known json schema] |
❌
|
3 Implementers MUST provide support for JSON Schema specifications where, in the following table, the required column's value is yes |
✓
|
3.1.1 The $id MUST be present and its value MUST represent a valid URI-reference |
❌
|
3.1.2, 4 The $schema property MUST be present in each schema |
❌
|
4.2 (Success) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Failure) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Indeterminate) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
Implementation ⇒
⇓Test Name
|
tbd |
---|---|
2.1 ID - The value MUST be a URL that identifies the schema associated with the verifiable credential. |
❌
|
2.1 The type property MUST be JsonSchemaCredential. |
❌
|
2.2 The credentialSubject property MUST contain two properties: type - the value of which MUST be JsonSchema; jsonSchema - an object which contains a valid JSON Schema |
❌
|
2.2 The value of the credentialSchema property MUST always be set to [known json schema] |
❌
|
3 Implementers MUST provide support for JSON Schema specifications where, in the following table, the required column's value is yes |
🛑
|
3.1.1 The $id MUST be present and its value MUST represent a valid URI-reference |
❌
|
3.1.2, 4 The $schema property MUST be present in each schema |
❌
|
4.2 (Success) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Failure) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|
4.2 (Indeterminate) Validation MUST result in one of the following three possible outcomes: success, failure, or indeterminate. |
❌
|