Re: Data Integrity conformance test suite

Greetings Julien,

The design goal of the test suite is to demonstrate implementations of the
specification in order to meet the criteria of having 2+ implementations
passing the normative statements and features laid out in the spec.

In the case of Data Integrity, this was made by asserting these statements
based on implementers of Data Integrity crypto suites. We used eddsa, ecdsa
and bbs to start as these were also candidate specifications.

The Data Integrity assertions are available here:
https://github.com/w3c-ccg/data-integrity-test-suite-assertion

However, these assertions are imported in the relevant crypto suite test
suite and invoked during execution. Using these assertions in a stand alone
mode for other crypto suites hasn't been in scope.

If I understand your inquiry, you have a crypto suite published for
MerkleProof2019 and want to ensure this crypto suite is conformant with the
Data Integrity specification.

Could you share how you would envision testing your MerkleProof2019
implementation and I might be able to assist you.

The preferred option is to have an api service that receives a credential
as input and returns the signed credential.

There is also an api shim available if you only have a sampled issued vc to
test:
https://github.com/w3c-ccg/vc-test-suite-api

I can help you get this setup.

Please let me know if this is useful information for you.

Regards,
Patrick

On Fri, May 23, 2025 at 9:10 AM Julien Fraichot <Julien.Fraichot@hyland.com>
wrote:

> Hi community,
>
>
>
> I may have missed the information but I was wondering if there is a test
> suite which allows to test against conformance of the Data Integrity spec
> for any cryptosuite?
>
>
>
> I have found the Eddsa and BBS test suites but they don’t seem to be
> exactly what I need as I am trying to evaluate conformity of the
> MerkleProof2019 with the DI specification. I’m all the more interested in
> something that would also cover tests for proof options like nonce,
> challenge, domain, etc to confirm if my implementation of them is correct
> or not.
>
>
>
> Thanks
>
>
>
> --
>
>
>
> Julien Fraichot
>
> Developer – Hyland Credentials
>
>
> ----------------------------------------- Please consider the environment
> before printing this e-mail -----------------------------------------
>
> CONFIDENTIALITY NOTICE: This message and any attached documents may
> contain confidential information from Hyland Software, Inc. The information
> is intended only for the use of the individual or entity named above. If
> the reader of this message is not the intended recipient, or an employee or
> agent responsible for the delivery of this message to the intended
> recipient, the reader is hereby notified that any dissemination,
> distribution or copying of this message or of any attached documents, or
> the taking of any action or omission to take any action in reliance on the
> contents of this message or of any attached documents, is strictly
> prohibited. If you have received this communication in error, please notify
> the sender immediately by e-mail or telephone, at +1 (440) 788-5000, and
> delete the original message immediately. Thank you.
>