[Openid-dcp] 回覆: Last Call! Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)
Thomas Darimont
thomas.darimont at oidf.org
Wed Jul 8 07:46:39 UTC 2026
*
...review the logs, which is now tracked on a separate tracker…
Already done.
Kind regards,
Thomas
---------------------
Thomas Darimont
Certification Specialist | Certification Team
OpenID Foundation
________________________________
From: Gail Hodges <gail at oidf.org>
Sent: Wednesday, July 8, 2026 9:43 AM
To: Henry <henry.hang at turingspace.co>
Cc: openid-specs-digital-credentials-protocols at lists.openid.net <openid-specs-digital-credentials-protocols at lists.openid.net>; Oriol Canadés Díez <ocanades at outlook.com>; Joseph Heenan <joseph.heenan at oidf.org>; Thomas Darimont <thomas.darimont at oidf.org>; Serj Hallam <serj.hallam at oidf.org>
Subject: Re: 回覆: Last Call! Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)
Henry
Many thanks.
I am on leave but Thomas will review the logs, which is now tracked on a separate tracker… And Serj will update the marketing columns accordingly.
On Jul 8, 2026, at 2:22 AM, Henry <henry.hang at turingspace.co> wrote:
Hi Gail,
This is Henry from Turing Space, it looks a few columns are missing on tracker, and here are some details for it. I have also sent the test logs separately to certification at oidf.org<mailto:certification at oidf.org>. Thank you all.
1. Tests run: OpenID4VCI 1.0 + HAIP 1.0 as Issuer, SD-JWT
2.
Test logs: email to certification at oidf.org<mailto:certification at oidf.org>
3. Feedback on tests: passed all, email to certification at oidf.org<mailto:certification at oidf.org>
4. Entity name: Turing Space
5. Entity logo: yes, logo use authorised. email to certification at oidf.org<mailto:certification at oidf.org>
6. Quote for launch comms:
The conformance testing is essential to building real-world interoperability — and we are proud to contribute to strengthening the ecosystem, making the world more trustworthy.
Name and title for attribution: Henry Hang, CTO of Turing Space.
7. Contribution Agreement: signed all WGs on 29th April.
8. Membership: Not yet now.
--
Best regards,
Henry
[https://github.com/Turing-Chain/resources/blob/master/turing-space_Logo_S.png?raw=true]
Henry Hang
Co-Founder & CTO
P +886-913-138-802
T +882-2-7709-9601
E henry.hang at turingspace.co
Turing Space Inc.
[https://github.com/Turing-Chain/resources/blob/master/website(gray).png?raw=true]<https://turingcerts.com/>[https://github.com/Turing-Chain/resources/blob/master/facebook(gray).png?raw=true]<https://www.facebook.com/turingcerts/>[https://github.com/Turing-Chain/resources/blob/master/linkedin(gray).png?raw=true]<https://tw.linkedin.com/company/turingspace>
Email Confidentiality Notice
The contents of this email (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this email, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and delete it (including any attachments) from your system. Neither Turing Space Inc. nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
信件保密警語
本信件及附件內容為機密性資料，若您並非被指定之收信人或在任何原因未經授權的情形之下收到本信件，請勿披露、複製或轉載本信件內容於任何人，並請立即通知原發信人，以及請從您的電腦刪除此信件和任何附件。如若更改或偽造此訊息，美商圖靈(Turing Space Inc.)及其任何子公司或關聯公司均不承擔任何責任。
メールの機密情報について
当社から送信されるメールのメッセージ及び添付物には、機密情報を含んでいる場合がございます。当社から送信されたメールに心当たりがない場合、自己のために利用することや、第三者への開示は固く禁止いたします。速やかに送信元へその旨をご連絡いただき、本メール及び本メールの添付物をすべて破棄していただけますようお願い申し上げます。Turing Spaceおよびその子会社または関連会社は、本情報のいかなる変更または改ざんに対しても責任を負いません。
________________________________
寄件者: Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols-bounces at lists.openid.net> 代表 Oriol Canadés Díez via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net>
寄件日期: 2026年6月1日 上午 02:49
收件者: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
副本: Oriol Canadés Díez <ocanades at outlook.com>
主旨: Re: [Openid-dcp] Last Call! Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)
Hello Gail,
Fikua Lab would like to take part in the final call. Here is our feedback for the tracker.
Tests we ran (all passed):
*
OpenID4VP 1.0 + HAIP 1.0 — as verifier, SD-JWT VC + MDOC
*
OpenID4VP 1.0 + HAIP 1.0 — as wallet, SD-JWT VC + MDOC
*
OpenID4VCI 1.0 + HAIP 1.0 — as issuer, SD-JWT VC + MDOC
*
OpenID4VCI 1.0 + HAIP 1.0 — as wallet, SD-JWT VC + MDOC
All tests in the plans we ran passed.
Test logs: All our runs are published. You can reach them at https://lab.fikua.com/ → OIDF Conformance Results, where each test links to its corresponding run in the OIDF conformance suite.
[image.png]
Feedback on the tests: The suite worked as expected for our SD-JWT VC configurations across both the issuance and presentation flows. No issues or bugs to report.
*
Entity name: Permission granted to use the name "Fikua".
*
Entity logo: Permission granted to use the Fikua logo.
*
Quote:
"As we build toward the EU Digital Identity Wallet, conformance to OpenID4VP, OpenID4VCI and HAIP is no longer optional; it is the foundation regulators and relying parties will depend on. The OIDF test suite let Fikua validate that our Issuer, Wallet and Verifier all speak the same language as the rest of Europe."
*
Contribution agreement: A signed contribution agreement is in place.
*
Membership: Membership is in place.
Happy to provide anything else you need for the tracker.
Best regards,
Oriol Canadés Díez
Tel (+34) 634 53 08 74
ocanades at o<mailto:oriol.canades at in2.es>utlook.com
www.<http://www.in2.es/>oriolcanades.com
From: Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols-bounces at lists.openid.net> on behalf of Gail Hodges via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols at lists.openid.net>
Date: Wednesday, 27 May 2026 at 22:26
To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
Cc: Gail Hodges <gail at oidf.org>; Joseph Heenan <joseph.heenan at oidf.org>; Serj Hallam <serj.hallam at oidf.org>
Subject: [Openid-dcp] Last Call! Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)
Hello DCP WG Implementers
This is the Final Call to "test the tests" for OpenID4VP 1.0, OpenID4VCI 1.0, and HAIP 1.0, feedback due by June 2nd.
We have feedback from 5 implementers (Bundesdruckerei, Lissi, Meeco, Hopae, UIDAI/Aadhaar). Another 6 implementers confirmed that they plan to provide feedback. We are trending towards having the minimum feedback required for the WG to confirm that the test suite meets requirements, and it can be published for self-certification.
If you want to take part, we need to know:
1. What tests you ran
* OpenID4VP 1.0 + HAIP 1.0 for SD-JWT and/or mdoc, as wallet
* OpenID4VP 1.0 + HAIP 1.0 for SD-JWT and/or mdoc, as verifier
* OpenID4VPVCI 1.0 + HAIP 1.0for SD-JWT and/or mdoc, as issuer
* OpenID4VPVCI 1.0 + HAIP 1.0for SD-JWT and or mdoc, as wallet
2.
Test logs for the tests you ran
3. Any feedback on tests themselves, issues bugs, or let us know if it worked as expected
4. Entity name, permission to use entity name or not
5. Entity logo, permission to use entity logo or not
6. Quote if you want to be included in comms, and if so the name and title to attribute quote to
7. Confirmation that a signed contribution agreement is in place (to cover feedback)
8. Confirmation if membership is in place or not (not required to be a member, we are tracking however)
I can update the tracker for you:
https://docs.google.com/spreadsheets/d/1Zfp41ah1u2JCdnjv6NvcTF7k4TJnlBjBkwr4Fp--stg/edit?gid=0#gid=0
Tests are located in usual place:
*
OpenID for Verifiable Presentations<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/
* OpenID for Verifiable Credential Issuance<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/
It is not required for your configuration to pass all tests for your feedback to be welcome. There is also value in knowing that tests that do not pass, fail to pass for expected reasons.
Only after the WG approves the test suite is ready, and OIDF “launches,” the test suite will they be made available for self-certification. At this stage, for modest fees, any implementer can submit their test results for OIDF review and publication of passing results on OIDF website. At this point no fees apply we are solely proving out the open source test suite. Open source projects do not have to pay fees to submit their results for self-certification.
Gail
From: Gail Hodges <gail at oidf.org<mailto:gail at oidf.org>>
Date: Tuesday, April 28, 2026 at 1:15 PM
To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net<mailto:openid-specs-digital-credentials-protocols at lists.openid.net>>
Cc: Joseph Heenan <joseph.heenan at oidf.org<mailto:joseph.heenan at oidf.org>>, Thomas Darimont <thomas.darimont at oidf.org<mailto:thomas.darimont at oidf.org>>
Subject: Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)
Hello all
Hello leading implementers of OpenID4VP 1.0, OpenID4VCI 1.0 and HAIP 1.0! Many thanks to all of you who have been testing the tests in interop this past year.
We need your help.
We need at least 3 issuers, 3 wallets and 3 verifiers to “tests the tests” for the test suite to make sure they are fully debugged, so OIDF can launch the open source test suite. Tests are located in usual place:
* OpenID for Verifiable Presentations<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/
* OpenID for Verifiable Credential Issuance<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/> 1.0 + HAIP 1.0https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/
Please use the ‘demo’ system to test as per the above instructions; that has the latest changes/fixes applied.
From: Gail Hodges <gail at oidf.org>
Date: Tuesday, April 28, 2026 at 8:15 PM
To: Digital Credentials Protocols List <openid-specs-digital-credentials-protocols at lists.openid.net>
Cc: Joseph Heenan <joseph.heenan at oidf.org>, Thomas Darimont <thomas.darimont at oidf.org>
Subject: Testing the Tests & Launch Comms (OpenID4VP/VCI/HAIP 1.0)
Hello all
Hello leading implementers of OpenID4VP 1.0, OpenID4VCI 1.0 and HAIP 1.0! Many thanks to all of you who have been testing the tests in interop this past year.
We need your help.
We need at least 3 issuers, 3 wallets and 3 verifiers to “tests the tests” for the test suite to make sure they are fully debugged, so OIDF can launch the open source test suite. Tests are located in usual place:
*
OpenID for Verifiable Presentations<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-presentations/
*
OpenID for Verifiable Credential Issuance<https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/> 1.0 + HAIP 1.0 https://openid.net/certification/conformance-testing-for-openid-for-verifiable-credential-issuance/
Please use the ‘demo’ system to test as per the above instructions; that has the latest changes/fixes applied.
We are using this template to track your feedback, and you appetite to be included in the OIDF comms launching the conformance test suite:
1.
What tests you ran/are running
2.
That all feedback you have is submitted to certification at oidf.org (including passing results, bugs or gaps)
3.
Your lead person contact person and their contact information (if different to what we have shown for you )
4.
If you want your entity to be named in comms, and a quote if you want to give one.
5.
If you do not have a DCP WG contribution agreement signed, please complete it to IPR protect your feedback https://openid.net/intellectual-property naming DCP WG or better yet "ALL WGs."
The Certification team will triage feedback, with WG feedback where needed.
Once the test suite is live, the following conformance capabilities will be enabled:
*
Self-certification will launch
*
Entities will have the option but not the obligation to self-certify for modest fees, discounts for members.
*
Tests available
*
OpenID4VP 1.0 + HAIP 1.0 for SD-JWT and mdoc (Note: not generic VP )
*
OpenID4VPVCI 1.0 + HAIP 1.0for SD-JWT and mdoc (Note: not generic VCI)
*
OIDF will be launching a new Independent Conformance Service, where third parties may be accredited to operate the conformance suite on behalf of OIDF to operate conformance.
*
Program to launch in Q2
*
First 6 MOU signatories were announced in March & April.
*
OIDF will continue to collaborate with and brief leading ecosystems like EC, California, India, Brazil, World Bank (for their clients), as well as peer standards bodies (e.g. CSC, FIDO, W3C etc)
Thanks in advance!
Joseph, Thomas, Gail
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260708/5adae2d0/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 64672 bytes
Desc: image.png
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20260708/5adae2d0/attachment-0001.png>
More information about the Openid-specs-digital-credentials-protocols
mailing list