Skip to content

Conversation

@ottonomy
Copy link

@ottonomy ottonomy commented Dec 18, 2025

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:

  • If a credential uses this render method, it is possible to identify which data in the credential best corresponds to summary properties that would be desirable to display on a card, with a few top-level properties and a priority-ordered list of labeled data fields pulled out of a credential's structure for display.
  • Summary views could display the core data fields plus one or two of the deeper fields, and detail views could display all of the fields.

Preview | Diff

[=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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

</p>

<p>
The template is a JSON object that matches the json-card output structure.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

</pre>

<p>
The following example shows a valid json-card template with JSON pointer
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

</table>

<p>
The following example shows a valid json-card output:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The following example shows a valid json-card output:
The following example shows a valid `json-card` output:

</ol>
</li>
<li>
Validate the resulting JSON object against the json-card output schema. If
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants