aries-cloudagent-python
aries-cloudagent-python copied to clipboard
hyperledger
[Anoncreds] update the legacy "Issue Credential" to store credential in W3C format
In 2023, BC Gov did a series of “Code With Us” procurements to enable issuing and presenting AnonCreds VCs in W3C format. Nothing changed in AnonCreds other than the data in the credentials and presentations were moved around such that the confiormed to the VCDM Data Model and conformed to a Data Integrity proof with an “anoncreds-2023” cryptosuite. The work was done in AnonCreds RS, Credo (then AFJ) and ACA-Py. Unfortunately, the ACA-Py effort lagged behind the rest of the implementation, and it didn’t get fully completed, and as a result, the migration work to get everyoine using W3C conforment did not happen — the community was to busy with other activities and goals.
The underlying work is there and available in all three codebases, but activating it has not (AFAIK) been done in any organization.
The idea with this issue is that the holder can keep the credential in any format, and the store and retrieve code would handle any conversions needed from “legacy” format to “W3C VCDM” format — as all the data is available in both. The conversion is just moving JSON around.
I aded the background of the issued to the description — and repeated it here, so you see it in your email.
In 2023, BC Gov did a series of “Code With Us” procurements to enable issuing and presenting AnonCreds VCs in W3C format. Nothing changed in AnonCreds other than the data in the credentials and presentations were moved around such that the confiormed to the VCDM Data Model and conformed to a Data Integrity proof with an “anoncreds-2023” cryptosuite. The work was done in AnonCreds RS, Credo (then AFJ) and ACA-Py. Unfortunately, the ACA-Py effort lagged behind the rest of the implementation, and it didn’t get fully completed, and as a result, the migration work to get everyoine using W3C conforment did not happen — the community was to busy with other activities and goals.
The underlying work is there and available in all three codebases, but activating it has not (AFAIK) been done in any organization.
The idea with this issue is that the holder can keep the credential in any format, and the store and retrieve code would handle any conversions needed from “legacy” format to “W3C VCDM” format — as all the data is available in both. The conversion is just moving JSON around.
