Open peppelinux opened 1 month ago
the credential configuration in the CI metadata is one of the proposal to represent the credential in the holder UI
the second proposal is to embed the graphic style within the credential schema
What do you mean as graphic style in the second proposal?
In the holder device, the graphics of the credential must be reconstructed starting from the base image and inserting the various textual elements promptly (x,y coordinates) so building an ad-hoc template. The main problem with the two proposals made is that in the event of a change in one or both objects (graphics and metadata) we would have a non-aligned template in the app.
the two proposal are exclusive, DTD and IPZS agreed on the first one, with the graphic styles within the metadata, while the second proposal was brought by pagopa during the editor's call
During the editor's call of the 17 July we have decided that:
This issue aims to be resolved by extending the CI metadata
We have to propose an enrichment of the current credential schema including a graphic element, cryptographically verifiable
this proposal starts with the evaluation of implementing trust marks, such as in the form of a qrcode, that enable the cryptographic validation and also the human representation of the verifiable element