VCDM v2.0 Interoperability Report

Verifiable Credentials Data Model v2.0 Interoperability Report

W3C Group Note

More details about this document
This version:
https://www.w3.org/TR/2023/NOTE-vcdm2-test-suite-20230408/
Latest published version:
https://www.w3.org/TR/vcdm2-test-suite/
Latest editor's draft:
https://w3c-ccg.github.io/vcdm-test-suite/#issue-credential
History:
https://www.w3.org/standards/history/vcdm2-test-suite
Commit history
Editor:
Charles E. Lehner
Author:
Charles E. Lehner
Feedback:
GitHub w3c-ccg/vcdm-test-suite (pull requests, new issue, open issues)

Abstract

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

Status of This Document

This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This document was published by the Verifiable Credentials Working Group as a Group Note using the Note track.

Group Notes are not endorsed by W3C nor its Members.

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

The W3C Patent Policy does not carry any licensing requirements or commitments on this document.

This document is governed by the 2 November 2021 W3C Process Document.

1. Conformance Testing Results

This section is non-normative.

Tests passed 22/22 100%

Tests failed 0/22 0%

Tests skipped 22

Total tests 44

These tests were run on

1.1 Key

This section is non-normative.

The results of the tests are shown below:

2. Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, and MUST NOT in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2.1 Verifiable Credentials Data Model v2.0

This section is non-normative.

Issuer ⇒
Test Name
example API Catalog Danube Tech Digital Bazaar EWF GS1 US LearnCard MATTR Mavennet mesur.io SecureKey Transmute
"Conforming processors MUST produce errors when nonconforming documents are consumed."
"Verifiable credentials and verifiable presentations MUST include a @context property."
Verifiable credentials and 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."
@context: "Subsequent items in the array MUST express context information and be composed of any combination of URLs or objects."
"All libraries or processors MUST ensure that the order of the values in the @context property is what is expected for the specific application."
if present: "The id property MUST express an identifier that others are expected to use when expressing statements about a specific thing identified by that identifier."
if present: "The id property MUST NOT have more than one value."
if present: "The value of the id property MUST be a URL which MAY be dereferenced."
"The value of the id property MUST be a single URL."
"Verifiable credentials and verifiable presentations MUST have a type property."
"The value of the type property MUST be, or map to (through interpretation of the @context property), one or more URLs."
list: "objects that MUST have a type specified."
"A verifiable credential MUST have a credentialSubject property."
"The value of the credentialSubject property is defined as a set of objects that MUST contain one or more claims that are each related to a subject of the verifiable credential."
"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."
"A credential MUST have an validFrom property."
"The value of the validFrom property MUST be a string value of an [XMLSCHEMA11-2] combined date-time string representing the date and time the credential becomes valid, which could be a date and time in the future."
"If present, the value of the validUntil property MUST be a string value of an [XMLSCHEMA11-2] combined date-time string representing the date and time the credential ceases to be valid, which could be a date and time in the past."
"If present, the value of the credentialStatus property MUST include" id and type
credentialStatus id property "MUST be a URL which MAY be dereferenced."
"If present, the value of the verifiableCredential property MUST be constructed from one or more verifiable credentials, or of data derived from verifiable credentials in a cryptographically verifiable format."

A. References

A.1 Normative references

[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119
[RFC8174]
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc8174