Implement a Generic Display Credential Data Format in UniCore for Reliable Frontend Rendering

[nanderstabel]

Description

At the moment, UniCore's credential 'output' is unreliable and therefore it is inconvenient for frontends to rely on certain data to be rendered properly. To solve this:

• We need a generic Display Credential data format.
• This data format will be the single source of truth for any frontend relying on UniCore.
• The data format consists of at least two parts:
  a. An outer shell: Non-subject-specific data such as issuance details, issuer (connection ID), and potentially others.
  b. Subject data: The actual data about the subject, which will initially be rendered using our default renderer.

Topics to consider:

Different credential formats might require data-specific renderers.
Credential issuers may define claim-specific display properties that we should respect. (See: OpenID4VCI Issue #376 Comment)

Motivation

• Consistency Across Frontends: By establishing a unified data format, we ensure that all frontends relying on UniCore present credential data consistently. This eliminates discrepancies and reduces the potential for errors or misunderstandings.

• Reduced Redundancy: Avoids the need to handle multiple formats separately, which can lead to redundant code and increased potential for bugs.

Resources

No response

To-do List

• Add a generic Display Credential data format

[M-Adam-Hus]

Implement a Generic Display Credential Data Format in UniCore for Reliable Frontend Rendering