Render method to enable card-like displays in wallets and displayers #39
+438
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TallTed
reviewed
Dec 18, 2025
| [=verifiable credential=] into a standardized JSON card format. This format | ||
| enables wallets to display credentials in a responsive card layout with key | ||
| data highlighted and configurable additional fields. Wallets that implement | ||
| this method can render the standardized JSON output into their own card UI |
Member
There was a problem hiding this comment.
Suggested change
| this method can render the standardized JSON output into their own card UI | |
| this method can render the standardized JSON output in their own card UI |
TallTed
reviewed
Dec 18, 2025
| </p> | ||
|
|
||
| <p> | ||
| The template is a JSON object that matches the json-card output structure. |
Member
There was a problem hiding this comment.
Suggested change
| The template is a JSON object that matches the json-card output structure. | |
| The template is a JSON object that matches the `json-card` output structure. |
TallTed
reviewed
Dec 18, 2025
| processing the template, JSON pointer strings are evaluated against the | ||
| credential data and replaced with the resolved values. The template MUST | ||
| conform to the JSON template schema defined below, and the resulting output | ||
| MUST conform to the json-card output schema. Compound data across multiple |
Member
There was a problem hiding this comment.
Suggested change
| MUST conform to the json-card output schema. Compound data across multiple | |
| MUST conform to the `json-card` output schema. Compound data across multiple |
TallTed
reviewed
Dec 18, 2025
| </pre> | ||
|
|
||
| <p> | ||
| The following example shows a valid json-card template with JSON pointer |
Member
There was a problem hiding this comment.
Suggested change
| The following example shows a valid json-card template with JSON pointer | |
| The following example shows a valid `json-card` template with JSON pointer |
TallTed
reviewed
Dec 18, 2025
| </table> | ||
|
|
||
| <p> | ||
| The following example shows a valid json-card output: |
Member
There was a problem hiding this comment.
Suggested change
| The following example shows a valid json-card output: | |
| The following example shows a valid `json-card` output: |
TallTed
reviewed
Dec 18, 2025
| </ol> | ||
| </li> | ||
| <li> | ||
| Validate the resulting JSON object against the json-card output schema. If |
Member
There was a problem hiding this comment.
Suggested change
| Validate the resulting JSON object against the json-card output schema. If | |
| Validate the resulting JSON object against the `json-card` output schema. If |
msporny
reviewed
Jan 4, 2026
Member
msporny
left a comment
msporny
left a comment
There was a problem hiding this comment.
At a high level, this looks useful to me. A couple of suggestions:
- Perhaps we can call this the "Summary" or "Card" render suite? I don't know what a "json-card" is and what this is actually doing is providing a fallback summary display.
- What is the Internationalization and Accessibility story here? I don't think we'll pass the i18n and a11y reviews without one.
msporny
reviewed
Jan 4, 2026
Comment on lines
+810
to
+811
| "issueDate": "/validFrom", | ||
| "expirationDate": "/validUntil" |
Member
There was a problem hiding this comment.
I don't understand the purpose of these properties?
msporny
reviewed
Jan 4, 2026
Comment on lines
+798
to
+799
| "label": "Institution", | ||
| "value": "/issuer" |
Member
There was a problem hiding this comment.
Suggested change
| "label": "Institution", | |
| "value": "/issuer" | |
| "label": "Institution", | |
| "language": "en", | |
| "value": "/issuer" |
We could do this for i18n?
|
+1 to the concept in this PR. I think if any VC has both a "Summary Card JSON" render method and a (forthcoming PR) sandboxed-HTML render method, it should cover the vast majority of rendering cases. The "Summary Card JSON" rendering is useful for interfaces that want to have significant control over their own UX and integrate perhaps many different VCs at once into a unified view (lists, tables, cards, etc.) and the sandboxed-HTML render method provides the issuer's preferred custom view of a single VC (potentially even interactive!). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For discussion and consideration, I don't have any particular product that aims to use this concept imminently. Feel free to edit.
The concept is:
fields, and detail views could display all of thefields.Preview | Diff