Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prioritizing display of VC Fields When No RenderMethod Provided #509

Closed
Tracked by #513
kayaelle opened this issue Sep 22, 2023 · 1 comment
Closed
Tracked by #513

Prioritizing display of VC Fields When No RenderMethod Provided #509

kayaelle opened this issue Sep 22, 2023 · 1 comment
Labels
discuss Needs discussion with the DCC tech team enhancement New feature or request future minor Fix when we can

Comments

@kayaelle
Copy link
Member

From discussion at #460

@kayaelle One thing that has confused me for a while now is the presence of name, description, and image at multiple levels of the credential. In the event that name, description, or image appear both at the root level of the credential and at credentialSubject.achievement, how should the wallet handle that?

I think this is confusing too. The name, description, and image are intended to be specific to the VC that was issued whereas the credentialSubject.achievement is intended to be the generic description that applies to anyone that the badge was issued to. Up for discussion could be prioritizing the root level over the credentialSubject.achievement content.

I think this is a related but different discussion about prioritizing fields in VCs versus OB3. I'll make an issue for discussion. Note that currently this wallet is only displaying Open Badges fields.

@kayaelle kayaelle added enhancement New feature or request discuss Needs discussion with the DCC tech team future labels Sep 22, 2023
@alexfigtree alexfigtree added the minor Fix when we can label Mar 15, 2024
@alexfigtree
Copy link
Member

Closing in favor of: #513

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Needs discussion with the DCC tech team enhancement New feature or request future minor Fix when we can
Projects
Status: LCW Backlog
Development

No branches or pull requests

2 participants