This is a interoperability report for implementers for the Verifiable Credentials Data Model v2.0 specification.

Conformance Testing Results

Tests passed 196/240 81%

Tests failed 44/240 19%

Failures 44

Tests skipped 75

Total tests 315

These tests were run on

Key

🚫
 Pending
✓
 Passed
❌
 Failed
⊘
 Access Denied
⏱
 Timeout
—
 Not Implemented

The results of the tests are shown below:

Basic Conformance

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
Conforming document (compliance): VCDM "MUST be enforced." ("all relevant normative statements in Sections 4. Basic Concepts, 5. Advanced Concepts, and 6. Syntaxes")
🚫
🚫
🚫
🚫
🚫
verifiers MUST produce errors when non-conforming documents are detected.
✓
✓
✓
✓
✓

Contexts

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
Verifiable credentials MUST include a @context property.
✓
✓
✓
✓
✓
Verifiable presentations MUST include a @context property.
✓
✓
✓
✓
✓
Verifiable credentials: The value of the @context property MUST be an ordered set where the first item is a URL with the value https://www.w3.org/ns/credentials/v2.
✓
✓
✓
✓
✓
Verifiable presentations: The value of the @context property MUST be an ordered set where the first item is a URL with the value https://www.w3.org/ns/credentials/v2.
✓
✓
✓
✓
✓
Verifiable Credential `@context`: "Subsequent items in the ordered set MUST be composed of any combination of URLs and/or objects where each is processable as a JSON-LD Context."
✓
✓
✓
✓
✓
Verifiable Presentation `@context`: "Subsequent items in the ordered set MUST be composed of any combination of URLs and/or objects where each is processable as a JSON-LD Context."
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-3-contexts.js:121:9)
✓
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 500 Internal Server Error": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 500 Internal Server Error"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-3-contexts.js:121:9)
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-3-contexts.js:121:9)
❌
Got unwanted rejection: Failed to support multiple `@context` URLs in a VP. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to support multiple `@context` URLs in a VP.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-3-contexts.js:121:9)

Identifiers

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
If present, the value of the id property MUST be a single URL, which MAY be dereferenceable.
✓
✓
✓
✓
✓

Types

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
Verifiable credentials MUST contain a type property with an associated value.
✓
✓
✓
✓
✓
Verifiable presentations MUST contain a type property with an associated value.
✓
✓
✓
✓
✓
The value of the type property MUST be one or more terms and/or absolute URL strings.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with an unmapped (via `@context`) type.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with an unmapped (via `@context`) type.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:66:9)
✓
❌
Missing expected rejection (HTTPError): Failed to reject a VC with an unmapped (via `@context`) type.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with an unmapped (via `@context`) type.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:66:9)
✓
✓
If more than one (type) value is provided, the order does not matter.
✓
✓
✓
✓
✓
Verifiable Credential objects MUST have a type specified.
✓
✓
✓
✓
✓
Verifiable Presentation objects MUST have a type specified.
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:105:11)
✓
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 500 Internal Server Error": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 500 Internal Server Error"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:105:11)
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:105:11)
❌
Got unwanted rejection: Failed to accept VP with `@context` mapped type. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept VP with `@context` mapped type.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:105:11)
`credentialStatus` objects MUST have a type specified.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with `credentialStatus` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with `credentialStatus` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:122:11)
✓
✓
✓
✓
`termsOfUse` objects MUST have a type specified.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with `termsOfUse` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with `termsOfUse` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:135:11)
✓
✓
✓
✓
`evidence` objects MUST have a type specified.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with `evidence` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with `evidence` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:148:11)
✓
✓
✓
✓
`refreshService` objects MUST have a type specified.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with `refreshService` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with `refreshService` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:160:11)
✓
✓
✓
✓
`credentialSchema` objects MUST have a type specified.
❌
Missing expected rejection (HTTPError): Failed to reject `credentialSchema` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject `credentialSchema` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-5-types.js:172:11)
✓
✓
✓
✓

Names and Descriptions

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
If present, the value of the name property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
❌
Got unwanted rejection: Failed to accept a VC using `name` in a defined language. Actual message: "A validation error occured in the 'Issue Credential' validator.": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC using `name` in a defined language.
                    Actual message: "A validation error occured in the 'Issue Credential' validator."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-6-names-and-descriptions.js:54:9)
✓
✓
✓
If present, the value of the description property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
❌
Got unwanted rejection: Failed to accept a VC using `description` in a defined language. Actual message: "A validation error occured in the 'Issue Credential' validator.": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC using `description` in a defined language.
                    Actual message: "A validation error occured in the 'Issue Credential' validator."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-6-names-and-descriptions.js:79:9)
✓
✓
✓
If present (on `issuer`), the value of the name property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
❌
Got unwanted rejection: Failed to accept a VC using `issuer.name` with language & direction expressed. Actual message: "Invalid credential.": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC using `issuer.name` with language & direction expressed.
                    Actual message: "Invalid credential."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-6-names-and-descriptions.js:111:9)
✓
✓
✓
If present (on `issuer`), the value of the description property MUST be a string or a language value object as described in 11.1 Language and Base Direction.
✓
❌
Got unwanted rejection: Failed to accept a VC using `issuer.description` with language & direction expressed. Actual message: "Invalid credential.": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC using `issuer.description` with language & direction expressed.
                    Actual message: "Invalid credential."
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-6-names-and-descriptions.js:138:9)
✓
✓
✓

Issuer

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
A verifiable credential MUST have an issuer property.
✓
✓
✓
✓
✓
The value of the issuer property MUST be either a URL, or an object containing an id property whose value is a URL.
❌
Missing expected rejection (HTTPError): Failed to reject an issuer identifier that was not a URL.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject an issuer identifier that was not a URL.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-7-issuer.js:44:9)
❌
Missing expected rejection (HTTPError): Failed to reject an issuer identifier that was not a URL.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject an issuer identifier that was not a URL.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-7-issuer.js:44:9)
❌
Failed to reject a null issuer identifier.: 
AssertionError [ERR_ASSERTION]: Failed to reject a null issuer identifier.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-7-issuer.js:48:9)
❌
Failed to reject a null issuer identifier.: 
AssertionError [ERR_ASSERTION]: Failed to reject a null issuer identifier.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-7-issuer.js:48:9)
❌
Failed to reject a null issuer identifier.: 
AssertionError [ERR_ASSERTION]: Failed to reject a null issuer identifier.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-7-issuer.js:48:9)

Credential Subject

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
A verifiable credential MUST contain a credentialSubject property.
✓
✓
✓
✓
✓
The value of the credentialSubject property is a set of objects where each object MUST be the subject of one or more claims, which MUST be serialized inside the credentialSubject property.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with an empty `credentialSubject`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with an empty `credentialSubject`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-8-credential-subject.js:45:9)
✓
✓
✓
✓

Validity Period

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
If present, the value of the validFrom property MUST be an [XMLSCHEMA11-2] dateTimeStamp string value representing the date and time the credential becomes valid, which could be a date and time in the future or in the past.
✓
✓
✓
✓
✓
If present, the value of the validUntil property MUST be an [XMLSCHEMA11-2] dateTimeStamp string value representing the date and time the credential ceases to be valid, which could be a date and time in the past or in the future.
❌
Got unwanted rejection: Failed to accept a VC with a valid `validUntil` date-time. Actual message: "Expired": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VC with a valid `validUntil` date-time.
                    Actual message: "Expired"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/4-9-validity-period.js:57:9)
✓
✓
✓
✓
If a validUntil value also exists, the validFrom value MUST express a datetime that is temporally the same or earlier than the datetime expressed by the validUntil value.
✓
✓
✓
✓
✓
If a validFrom value also exists, the validUntil value MUST express a datetime that is temporally the same or later than the datetime expressed by the validFrom value.
✓
✓
✓
✓
✓
Time values that are incorrectly serialized without an offset MUST be interpreted as UTC.
🚫
🚫
🚫
🚫
🚫

Status

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
If present (credentialStatus.id), the normative guidance in Section 4.4 Identifiers MUST be followed.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with a non-URL `credentialStatus.id`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with a non-URL `credentialStatus.id`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/410-status.js:42:9)
✓
✓
✓
✓
(If a credentialStatus property is present), The type property is REQUIRED. It is used to express the type of status information expressed by the object. The related normative guidance in Section 4.5 Types MUST be followed.
❌
Missing expected rejection (HTTPError): Failed to reject a VC missing `credentialStatus.type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC missing `credentialStatus.type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/410-status.js:52:9)
✓
❌
Missing expected rejection (HTTPError): Failed to reject a VC with a non-URL `credentialStatus.type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with a non-URL `credentialStatus.type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/410-status.js:56:9)
✓
✓
Credential status specifications MUST NOT enable tracking of individuals
🚫
🚫
🚫
🚫
🚫

Data Schemas

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
The value of the credentialSchema property MUST be one or more data schemas that provide verifiers with enough information to determine whether the provided data conforms to the provided schema(s).
✓
✓
✓
✓
✓
Each credentialSchema MUST specify its type (for example, JsonSchema), and an id property that MUST be a URL identifying the schema file.
❌
Missing expected rejection (HTTPError): Failed to reject `credentialSchema` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject `credentialSchema` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/411-data-schemas.js:48:9)
❌
Missing expected rejection (HTTPError): Failed to reject `credentialSchema` without an `id`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject `credentialSchema` without an `id`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/411-data-schemas.js:52:9)
✓
✓
✓
If multiple schemas are present, validity is determined according to the processing rules outlined by each associated type property
✓
✓
✓
✓
✓

Securing Mechanisms

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID 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 produces conforming documents, MUST include all required properties in the conforming documents that it produces, and MUST secure the conforming documents it produces using a securing mechanism as described in Section 4.12 Securing Mechanisms.
✓
✓
✓
✓
✓
A conforming verifier implementation consumes conforming documents, MUST perform verification on a conforming document as described in Section 4.12 Securing Mechanisms, MUST check that each required property satisfies the normative requirements for that property, and MUST produce errors when non-conforming documents are detected.
❌
Got unwanted rejection: Failed to verify credential. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify credential.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/412-securing-mechanisms.js:87:9)
✓
❌
Got unwanted rejection: Failed to verify credential. Actual message: "Request failed with status code 500 Internal Server Error": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify credential.
                    Actual message: "Request failed with status code 500 Internal Server Error"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/412-securing-mechanisms.js:87:9)
✓
✓

Verifiable Presentations

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
If [the `id` field is] present, the normative guidance in Section 4.4 Identifiers MUST be followed.
🚫
🚫
🚫
🚫
🚫
The type property MUST be present. One value of this property MUST be VerifiablePresentation, but additional types MAY be included.The related normative guidance in Section 4.5 Types MUST be followed.
✓
✓
✓
✓
✓
The verifiableCredential property MAY be present. The value MUST beone or more verifiable credential and/or enveloped verifiable credential objects (the values MUST NOT be non-object values such as numbers, strings, or URLs).
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:71:9)
✓
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 500 Internal Server Error": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 500 Internal Server Error"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:71:9)
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:71:9)
❌
Got unwanted rejection: Failed to verify a valid VP. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to verify a valid VP.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:71:9)

VP - Enveloped Verifiable Credentials

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
The @context property of the object MUST be present and include a context, such as the base context for this specification, that defines at least the id, type, and EnvelopedVerifiableCredential terms as defined by the base context provided by this specification.
❌
Got unwanted rejection: Failed to accept a VP containing a enveloped VC. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VP containing a enveloped VC.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:101:9)
❌
Got unwanted rejection: Failed to accept a VP containing a enveloped VC. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VP containing a enveloped VC.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:101:9)
❌
Got unwanted rejection: Failed to accept a VP containing a enveloped VC. Actual message: "Request failed with status code 500 Internal Server Error": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VP containing a enveloped VC.
                    Actual message: "Request failed with status code 500 Internal Server Error"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:101:9)
❌
Got unwanted rejection: Failed to accept a VP containing a enveloped VC. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VP containing a enveloped VC.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:101:9)
❌
Got unwanted rejection: Failed to accept a VP containing a enveloped VC. Actual message: "Request failed with status code 400 Bad Request": 
AssertionError [ERR_ASSERTION]: Got unwanted rejection: Failed to accept a VP containing a enveloped VC.
                    Actual message: "Request failed with status code 400 Bad Request"
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/413-verifiable-presentations.js:101:9)
The id value of the object MUST be a data: URL [RFC2397] that expresses a secured verifiable credential using an enveloping security scheme, such as Securing Verifiable Credentials using JOSE and COSE [VC-JOSE-COSE].
🚫
🚫
🚫
🚫
🚫
The type value of the object MUST be EnvelopedVerifiableCredential.
🚫
🚫
🚫
🚫
🚫

VP - Enveloped Verifiable Presentations

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
The @context property of the object MUST be present and include a context, such as the base context for this specification, that defines at least the id, type, and EnvelopedVerifiablePresentation terms as defined by the base context provided by this specification.
🚫
🚫
🚫
🚫
🚫
The id value of the object MUST be a data: URL [RFC2397] that expresses a secured verifiable presentation using an enveloping securing mechanism, such as Securing Verifiable Credentials using JOSE and COSE [VC-JOSE-COSE].
🚫
🚫
🚫
🚫
🚫
The type value of the object MUST be EnvelopedVerifiablePresentation.
🚫
🚫
🚫
🚫
🚫

VP - Presentations Including Holder Claims

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
A verifiable presentation that includes a self-asserted verifiable credential that is only secured using the same mechanism as the verifiable presentation MUST include a holder property.
🚫
🚫
🚫
🚫
🚫
When a self-asserted verifiable credential is secured using the same mechanism as the verifiable presentation, the value of the issuer property of the verifiable credential MUST be identical to the holder property of the verifiable presentation.
🚫
🚫
🚫
🚫
🚫

Advanced Concepts

Implementer ⇒
⇓Test Name
apicatalog.com Digital Bazaar OpSecId SpruceID VC Issuer Mock
When processing the active context defined by the base JSON-LD Context document defined in this specification, compliant JSON-LD-based processors produce an error when a JSON-LD context redefines any term.
✓
✓
✓
✓
✓
The value of the relatedResource property MUST be one or more objects of the following form:
🚫
🚫
🚫
🚫
🚫
The identifier for the resource is REQUIRED and conforms to the format defined in Section 4.4 Identifiers. The value MUST be unique among the list of related resource objects.
🚫
🚫
🚫
🚫
🚫
Each object associated with relatedResource MUST contain at least a digestSRI or a digestMultibase value.
🚫
🚫
🚫
🚫
🚫
The value of the refreshService property MUST be one or more refresh services that provides enough information to the recipient's software such that the recipient can refresh the verifiable credential.
✓
✓
✓
✓
✓
Each refreshService value MUST specify its type.
❌
Missing expected rejection (HTTPError): Failed to reject a VC with `refreshService` without a `type`.: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError): Failed to reject a VC with `refreshService` without a `type`.
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/50-advanced-concepts.js:100:11)
✓
✓
✓
✓
The value of the termsOfUse property MUST specify one or more terms of use policies under which the creator issued the credential or presentation.
✓
✓
✓
✓
✓
Each termsOfUse value MUST specify its type, for example, IssuerPolicy, and MAY specify its instance id.
❌
Missing expected rejection (HTTPError).: 
AssertionError [ERR_ASSERTION]: Missing expected rejection (HTTPError).
                        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at async Context.<anonymous> (file:///home/runner/work/vc-data-model-2.0-test-suite/vc-data-model-2.0-test-suite/tests/50-advanced-concepts.js:119:9)
✓
✓
✓
✓
If present, the value associated with the evidence property is a single object or a set of one or more objects.
✓
✓
✓
✓
✓
In order to avoid collisions regarding how the following properties are used, implementations MUST specify a type property in the value associated with the reserved property.
🚫
🚫
🚫
🚫
🚫