UI/UX difficulties when working with different credential formats that mean the same credential type

[JoTiTu]

From an UI perspective a wallet displays Credential Types and the user does not have to know if it is a mDoc or Sd-JWT credential. So the user just cares if it is for example a CreditCard. This is easy as long as the credential is used either as a Sd-Jwt OR mDoc.

Assuming an issuer issues the Credentials Type CreditCard in two different formats at the same time (mDoc AND Sd-Jwt) using a different schema for each of them, this gets more difficult because now the wallet has to know that both schemas semantically refer to the same Credential Type. This link between two schemas that refer to the same type is important so the wallet can make sure to map them and only show the Credential Type in the wallet once.

As of my knowledge currently there is no such feature but it would make the life of wallet implementers a lot easier since as of now workarounds are necessary to create groups.

So basically it would need some kind of link between two credential_supported_id.

[jogu]

I can see the potential problem here.

It may not be ideal, but my initial reaction would be that display.name in the two entries in credential_configurations_supported would be the same - could the wallet use that as a signal?

[JoTiTu]

That might be true in some cases but I think that this wouldn't be a bulletproof solution and more of a workaround.
A issuer could issue two different credentials that might share some similar fields even though they are semantically different.
I think a dedicated solution to address this grouping problem would be beneficial.