WRT to the Demo, upgrading the “Demo” v1 generator Should we consider, in reference to the NIST IR Report - That the TP-Report could be issued as a compliance credential? , If it were to use - OpenID4VCI (line 1872) for issuing VC’s, and that it works with 23220 - Card and security devices, which has the best standard for physical issuance (line 1876) - and then also with SD-JWT (Line 1835) - - So, perhaps the Generator v2, Demo should upgrade to SD-JWT ? And, we either revise schema from 27560 / or directly iterate a version of the record information structure, from the Kantara - Consent Receipt. We (Paul and I) have been working on this schema to make things in the transparency lab, e.g eConsent (as it is referred to in NIST Report) Thoughts? - Mark
On 2 Dec 2024, at 19:17, Salvatore D'Agostino <sal@idmachines.com> wrote:
Get [Outlook for iOS](https://aka.ms/o0ukef) ---------------------------------------------------------------
From: Carol Buttle <carol@kantarainitiative.org> Sent: Monday, December 2, 2024 7:02:10 PM To: digital_identity@nist.gov <digital_identity@nist.gov> Cc: Kay Chopard <kay@kantarainitiative.org>; Salvatore D'Agostino <sal@idmachines.com> Subject: NIST AVS Kantara Comments
Dear Team,
Kantara Initiative are pleased to have had the opportunity to provide comments for:
Attribute Validation Services for Identity Management: Architecture, Security, Privacy, and Operational Considerations
Comments as per your template are attached.
Should you have any difficulties opening the file, or any other queries, please do not hesitate to contact me.
Regards,
Carol --
Carol Buttle | Chief Technology Officer
[Logo, company name
Description automatically generated] Mobile:+44 (0)7747 882435 LinkedIn:@KantaraInitiative <image.png><NIST - AVS - Kantara Comments.Final.xlsx>