FHIR Chat · Displaying human-friendly issuer name · smart/health-cards

Stream: smart/health-cards

Topic: Displaying human-friendly issuer name


view this post on Zulip Matt Printz (Jun 04 2021 at 14:53):

We are looking to display the issuer along with the SHC content, but the "iss" url can be awfully cryptic. Is there a known way for mapping the issuer back to something human readable?

view this post on Zulip Michael Turman (Jun 04 2021 at 15:40):

Taking the ISS back to an Issuer directory is one path - the VCI team is working on standing up an interim directory until more formal trust frameworks are in place. The design for the directory includes a 'display' name and optional logo for each Issuer.

view this post on Zulip Matt Printz (Jun 04 2021 at 18:14):

Thanks Michael. Do we know if the directory will have an API so that we can pull down and cache the display name info?

view this post on Zulip Josh Mandel (Jun 04 2021 at 18:27):

"iss" url can be awfully cryptic. Is there a known way for mapping the issuer back to something human readable?

This is indeed the kind of thing a trust framework can help with -- but it's also the reason why we encourage iss URLs to be meaningful, because without a trust framework, that's often all you've got. (And to state the obvious: relying on an untrustworthy source of this mapping leads to confusion and mistakes for a verifier.)

view this post on Zulip Michael Turman (Jun 04 2021 at 23:20):

The directory is hosted in a public repo and could be cached. @Daniel Levenson can weigh in with more specifics.

view this post on Zulip Daniel Levenson (Jun 10 2021 at 16:56):

Apologies for the delayed follow-up here. I'm no longer working on the trust directory with TCP, but I believe the latest thinking is that name is a recommended (but technically not a required) field on an VC Issuer within a trust directory and very much cache-able. Plan is to host a JSON file on a publically accessible GH repo, so an API with one endpoint (GET path/to/issuers.json). However, @JP Pollak and @James Kizer are the best point of contacts for this information going forward.


Last updated: Apr 12 2022 at 19:14 UTC