msporny
commented
1 year ago Here is some preliminary example output from the test suite below:
Verifiable Credentials Data Model v2.0
✓ "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."
OR13
mprorock
dlongley
decentralgabe
mkhraisha
wip-abramson
Abstract
The Verifiable Credentials v2.0 test suite provides a mechanism to test if an issuer or verifier is conformant with the Verifiable Credentials v2.0 data model.
Owners
@clehner @msporny (same organization, looking for a supporter from another organization)
Work Item Questions
We are trying to create a mechanism that an implementer of the Verifiable Credentials v2.0 data model can use to determine if they are conformant with the Verifiable Credentials v2.0 specification.
At present, there is no test suite for the Verifiable Credentials v2.0 data model.
The Verifiable Credentials v1.1 data model required a number of things that made testing not as good as it could be, namely:
The current approach utilizes the Verifiable Credentials API to provide a unified interface for issuing and verifying a Verifiable Credential. This approach has the following advantages:
We believe this approach will be successful because it has already been used to demonstrate interoperability among 13+ implementers in the Jobs for the Future Plugfest. That is, we already have 13 implementers that can integrate with this test suite.
This work item is highly technical in nature and executes upon the decisions made in the Verifiable Credentials v2.0 work, which has been demonstrated to be more broadly inclusive of different input from a variety of parties from around the world.
Given that this is a test suite, it's audience are implementers and not necessarily people involved in design, product, marketing, anthropological, and UX fields.
We are generating a human-readable report as a part of the test suite output with easy to read columns stating which implementations pass vs. fail certain tests. The report should be citable/referenceable by non-technical individuals to understand how interoperability in the ecosystem is doing from a week-to-week basis.