From 9d6bf9f1635c311e2ae464964b6677b627ed750f Mon Sep 17 00:00:00 2001 From: Dmitri Zagidulin Date: Tue, 25 Aug 2026 10:50:54 -0400 Subject: [PATCH 1/4] Dispatch render suites on renderSuite, not type. Signed-off-by: Dmitri Zagidulin --- index.html | 174 +++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 148 insertions(+), 26 deletions(-) diff --git a/index.html b/index.html index 54ce690..e5905f1 100644 --- a/index.html +++ b/index.html @@ -303,20 +303,23 @@

The `renderMethod` Property

more rendering methods that can be used by software to express the [=verifiable credential=] using a visual, auditory, or haptic mechanism. Each `renderMethod` value MUST specify its `type`, for example, -`TemplateRenderMethod`. The precise contents of each rendering -hint is determined by the specific `renderMethod` `type` -definition. +`SuiteRenderMethod`. The precise contents of each rendering +hint is determined by the render suite specified by the +`renderSuite` property.
-

TemplateRenderMethod

+

SuiteRenderMethod

-When an [=issuer=] desires to specify template-based rendering instructions +When an [=issuer=] desires to specify rendering instructions for a [=verifiable credential=], they MAY add a `renderMethod` property that uses -the data model described below. +the data model described below. The concrete rendering behavior is determined +by the render suite named in the `renderSuite` property. +Each render suite defines which of the properties below it uses; see the +individual render suite sections.

@@ -337,14 +340,18 @@

TemplateRenderMethod

@@ -425,10 +432,16 @@

TemplateRenderMethod

type -A REQUIRED [=string=] that MUST be the value `TemplateRenderMethod`. +A REQUIRED [=string=] that MUST be the value `SuiteRenderMethod`.
renderSuite -A REQUIRED [=string=] that identifies the algorithms that are used for -generating the concrete rendering. +A REQUIRED [=string=] that identifies the render suite, that is, the set of +algorithms used for generating the concrete rendering. The value is a plain +JSON string and is compared using exact, case-sensitive matching. This +specification defines the values `data`, `html`, and `nfc`. Implementations +MUST ignore any `renderMethod` entry whose `renderSuite` value they do not +recognize or support.
+

+Where render suite values are registered (a registry section in this +specification, the VC Specs Directory, or both), and whether extension +suite values are plain strings or URLs, is still under discussion. +

+
-

The `card` Render Suite

+

The `data` Render Suite

-The `card` render suite uses JSON templates to transform a +The `data` render suite uses JSON templates to transform a [=verifiable credential=] into a standardized data display format. This format enables wallets to display credentials in a responsive card layout with key data highlighted and configurable additional fields. Wallets that implement @@ -449,6 +462,45 @@

The `card` Render Suite

pointer.

+
+

Use of Common Properties

+

+The `data` render suite uses the common render method properties as follows: +

+ + + + + + + + + + + + + + + + + + + + + +
PropertyUse in this suite
template +Provides the card template, either embedded as a `data:` URL or referenced as +a map. The value MUST be, or dereference to, a JSON document that conforms to +the card object definition in [[[#card-object]]]. +
renderProperty +Not used by this suite. The JSON pointer strings in the card template +determine which properties of the [=verifiable credential=] are exposed. +
outputPreference +MAY be provided. The `accessMode` and `style` preferences apply to the +display of the rendered card. +
+
+

The Card Object

@@ -539,7 +591,7 @@

The Card Object

Card Examples

- The following example shows a valid `card` template with JSON pointer + The following example shows a valid card template with JSON pointer strings:

@@ -573,7 +625,7 @@

Card Examples

- The following example shows a valid `card` output: + The following example shows a valid card output: 

Card Examples
     

 
     
+          title="Basic usage of the data render suite">
 {
   ...
   "renderMethod": {
-    "type": "TemplateRenderMethod",
-    "renderSuite": "card",
+    "type": "SuiteRenderMethod",
+    "renderSuite": "data",
     // the JSON template is embedded in the VC
     "template": "data:application/json;base64,eyJuYW1lIjogIi9jcmVkZW50aWFsU3ViamVjdC9kZWdyZWUvbmFtZSIsICJkZXNjcmlwdGlvbiI6ICJVbml2ZXJzaXR5IERlZ3JlZSBDcmVkZW50aWFsIiwgImZpZWxkcyI6IFt7ImxhYmVsIjogIkluc3RpdHV0aW9uIiwgInZhbHVlIjogIi9pc3N1ZXIifV19"
   }
@@ -633,8 +685,8 @@ 
Card Examples

 {
 ...
 "renderMethod": {
-  "type": "TemplateRenderMethod",
-  "renderSuite": "card",
+  "type": "SuiteRenderMethod",
+  "renderSuite": "data",
   "template": {
     // this JSON template is fetched from the Web
     "id": "https://degree.example/credential-templates/bachelors.json",
@@ -650,15 +702,15 @@ 
Card Examples

           

 
           
+               title="A remotely hosted data render method">
 {
 ...
 "renderMethod": {
   // this render method is fetched from the Web
   "id": "https://degrees.example/bachelors-card.jsonld",
   "mediaType": "application/ld+json",
-  "type": "TemplateRenderMethod",
-  "renderSuite": "card",
+  "type": "SuiteRenderMethod",
+  "renderSuite": "data",
   "digestMultibase": "zQmG270iEu5h6JqWAPdhyxz2dRerWC85Wg6wFl9znFCwYxAp"
 }
           

@@ -700,7 +752,7 @@ 
The `html` Render Suite

     "notRendered": "should not appear"
   },
   "renderMethod": {
-    "type": "TemplateRenderMethod",
+    "type": "SuiteRenderMethod",
     "renderSuite": "html",
     "renderProperty": [
       "/issuer/name",
@@ -725,6 +777,42 @@ 
The `html` Render Suite

 }
         

 
+        
Use of Common Properties

+        

+The `html` render suite uses the common render method properties as follows:
+        

+        
+          
+            
+              
+              
+            
+          
+          
+            
+              
+              
+            
+            
+              
+              
+            
+            
+              
+              
+            
+          
+        
PropertyUse in this suite
template
+Provides the HTML fragment, either embedded as a `data:` URL or referenced as
+a map whose `id` dereferences to the fragment.
+              
renderProperty
+MAY be provided to limit the [=verifiable credential=] data passed to the
+template. If absent, the entire [=verifiable credential=] is provided.
+              
outputPreference
+MAY be provided. The `style` `width` and `height` preferences apply to the
+`iframe` hosting the template.
+              

+
         

 Implementations MUST provide an environment that allows for JavaScript to safely
 render the HTML template using the filtered [=verifiable credential=] data.
@@ -1027,7 +1115,7 @@ 
The `nfc` Render Suite

 {
 ...
 "renderMethod": {
-  "type": "TemplateRenderMethod",
+  "type": "SuiteRenderMethod",
   "renderSuite": "nfc",
   "name": "Tap to send",
   // the NFC payload is embedded
@@ -1039,6 +1127,40 @@ 
The `nfc` Render Suite

 }
+

Use of Common Properties

+

+The `nfc` render suite uses the common render method properties as follows: +

+ + + + + + + + + + + + + + + + + + + + + +
PropertyUse in this suite
template +Provides the binary NFC payload, typically embedded as a `data:` URL. +
renderProperty +MAY be provided to limit which [=verifiable credential=] data is transmitted +over the NFC connection. +
outputPreference +Not generally used by this suite. +
+
@@ -1055,7 +1177,7 @@

Algorithms

Card Template Processing

- When processing a `card` template, the following steps MUST be + When processing a card template, the following steps MUST be performed:

@@ -1126,7 +1248,7 @@

Host Page

  • Let `renderMethod` be the chosen `renderMethod` property in `vc` where -`renderMethod.type` is `TemplateRenderMethod` and +`renderMethod.type` is `SuiteRenderMethod` and `renderMethod.renderSuite` is `html`.
  • @@ -1489,7 +1611,7 @@

    SD-JWT VC Type Metadata Rendering

    features are requirements in sectors such as healthcare, retail, and banking/finance. In contrast, this specification is not tied to a single credential serialization, and instead defines render suites that span a -code-free declarative `card` suite, a data-driven `html` suite executed in a +code-free declarative `data` suite, a data-driven `html` suite executed in a confined, "sandboxed" environment, and a static `nfc` suite.

    • From 2b268a82ff2401a427ac05768d448856f985371e Mon Sep 17 00:00:00 2001 From: Dmitri Zagidulin Date: Tue, 15 Sep 2026 10:58:48 -0400 Subject: [PATCH 2/4] Rename 'data' to 'summary'. Signed-off-by: Dmitri Zagidulin --- index.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/index.html b/index.html index e5905f1..ff40eba 100644 --- a/index.html +++ b/index.html @@ -349,7 +349,7 @@

    SuiteRenderMethod

    A REQUIRED [=string=] that identifies the render suite, that is, the set of algorithms used for generating the concrete rendering. The value is a plain JSON string and is compared using exact, case-sensitive matching. This -specification defines the values `data`, `html`, and `nfc`. Implementations +specification defines the values `summary`, `html`, and `nfc`. Implementations MUST ignore any `renderMethod` entry whose `renderSuite` value they do not recognize or support. @@ -439,9 +439,9 @@

    SuiteRenderMethod

    -

    The `data` Render Suite

    +

    The `summary` Render Suite

    -The `data` render suite uses JSON templates to transform a +The `summary` render suite uses JSON templates to transform a [=verifiable credential=] into a standardized data display format. This format enables wallets to display credentials in a responsive card layout with key data highlighted and configurable additional fields. Wallets that implement @@ -462,10 +462,10 @@

    The `data` Render Suite

    pointer.

    -
    +

    Use of Common Properties

    -The `data` render suite uses the common render method properties as follows: +The `summary` render suite uses the common render method properties as follows:

    @@ -668,7 +668,7 @@

    Card Examples

    ... "renderMethod": { "type": "SuiteRenderMethod", - "renderSuite": "data", + "renderSuite": "summary", // the JSON template is embedded in the VC "template": "data:application/json;base64,eyJuYW1lIjogIi9jcmVkZW50aWFsU3ViamVjdC9kZWdyZWUvbmFtZSIsICJkZXNjcmlwdGlvbiI6ICJVbml2ZXJzaXR5IERlZ3JlZSBDcmVkZW50aWFsIiwgImZpZWxkcyI6IFt7ImxhYmVsIjogIkluc3RpdHV0aW9uIiwgInZhbHVlIjogIi9pc3N1ZXIifV19" } @@ -686,7 +686,7 @@

    Card Examples

    ... "renderMethod": { "type": "SuiteRenderMethod", - "renderSuite": "data", + "renderSuite": "summary", "template": { // this JSON template is fetched from the Web "id": "https://degree.example/credential-templates/bachelors.json", @@ -710,7 +710,7 @@

    Card Examples

    "id": "https://degrees.example/bachelors-card.jsonld", "mediaType": "application/ld+json", "type": "SuiteRenderMethod", - "renderSuite": "data", + "renderSuite": "summary", "digestMultibase": "zQmG270iEu5h6JqWAPdhyxz2dRerWC85Wg6wFl9znFCwYxAp" } @@ -1611,7 +1611,7 @@

    SD-JWT VC Type Metadata Rendering

    features are requirements in sectors such as healthcare, retail, and banking/finance. In contrast, this specification is not tied to a single credential serialization, and instead defines render suites that span a -code-free declarative `data` suite, a data-driven `html` suite executed in a +code-free declarative `summary` suite, a data-driven `html` suite executed in a confined, "sandboxed" environment, and a static `nfc` suite.

    From e8eb6d65b6058c1b596014cb7f70a9d0e7ee009d Mon Sep 17 00:00:00 2001 From: Dmitri Zagidulin Date: Tue, 22 Sep 2026 14:17:49 +0000 Subject: [PATCH 3/4] Fix renderSuite registry title. Co-authored-by: Ted Thibodeau Jr --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index ff40eba..55e1ec9 100644 --- a/index.html +++ b/index.html @@ -432,7 +432,7 @@

    SuiteRenderMethod

    -

    +

    Where render suite values are registered (a registry section in this specification, the VC Specs Directory, or both), and whether extension suite values are plain strings or URLs, is still under discussion. From 30f18112286703ca1822d9a81790b709410fd564 Mon Sep 17 00:00:00 2001 From: Dmitri Zagidulin Date: Tue, 29 Sep 2026 10:30:18 -0400 Subject: [PATCH 4/4] Rename the rest of the 'card' instances to 'summary'. Signed-off-by: Dmitri Zagidulin --- index.html | 72 +++++++++++++++++++++++++++--------------------------- 1 file changed, 36 insertions(+), 36 deletions(-) diff --git a/index.html b/index.html index 55e1ec9..70988fc 100644 --- a/index.html +++ b/index.html @@ -443,21 +443,21 @@

    The `summary` Render Suite

    The `summary` render suite uses JSON templates to transform a [=verifiable credential=] into a standardized data display format. This format -enables wallets to display credentials in a responsive card layout with key +enables wallets to display credentials in a responsive layout with key data highlighted and configurable additional fields. Wallets that implement -this method can render the standardized JSON output in their own card UI +this method can render the standardized JSON output in their own UI designs, allowing credentials to be displayed even when a wallet doesn't natively support a specific credential type.

    The template and the rendered output are both JSON objects that share a -single definition, the card object, given below. String values in the +single definition, the summary object, given below. String values in the template can be JSON pointer strings (as specified in [[[RFC6901]]]) that reference values in the [=verifiable credential=]. When processing the template, JSON pointer strings are evaluated against the credential data and replaced with the resolved values. Both the template and the resulting -output MUST conform to the card object definition. Compound data across +output MUST conform to the summary object definition. Compound data across multiple fields is not supported; each field references a single JSON pointer.

    @@ -478,15 +478,15 @@

    Use of Common Properties

    template -Provides the card template, either embedded as a `data:` URL or referenced as +Provides the summary template, either embedded as a `data:` URL or referenced as a map. The value MUST be, or dereference to, a JSON document that conforms to -the card object definition in [[[#card-object]]]. +the summary object definition in [[[#summary-object]]]. renderProperty -Not used by this suite. The JSON pointer strings in the card template +Not used by this suite. The JSON pointer strings in the summary template determine which properties of the [=verifiable credential=] are exposed. @@ -494,17 +494,17 @@

    Use of Common Properties

    outputPreference MAY be provided. The `accessMode` and `style` preferences apply to the -display of the rendered card. +display of the rendered summary.
    -
    -

    The Card Object

    +
    +

    The Summary Object

    -A card object is a JSON object [[RFC8259]] with the members defined below. +A summary object is a JSON object [[RFC8259]] with the members defined below. The same definition applies to the template and to the rendered output. In a template, the value of any member defined as a string MAY instead be a JSON pointer string (starting with `/`, as specified in [[[RFC6901]]]) that @@ -516,16 +516,16 @@

    The Card Object

    name
    -A REQUIRED string containing the display name for the credential card. +A REQUIRED string containing the display name for the credential summary.
    description
    -A REQUIRED string containing the description text for the credential card. +A REQUIRED string containing the description text for the credential summary.
    icon
    An OPTIONAL string containing a [=URL=] or `data:` URL [[RFC2397]] for an -icon or image to display on the card. +icon or image to display on the summary.
    theme
    @@ -582,21 +582,21 @@

    The Card Object

    -A template SHOULD be validated against the card object definition above -before processing. A non-normative JSON Schema for card templates is -provided in [[[#card-template-json-schema]]]. +A template SHOULD be validated against the summary object definition above +before processing. A non-normative JSON Schema for summary templates is +provided in [[[#summary-template-json-schema]]].

    -

    Card Examples

    +

    Summary Examples

    - The following example shows a valid card template with JSON pointer + The following example shows a valid summary template with JSON pointer strings: 

    +                 title="Example summary template">
 {
   "name": "/credentialSubject/degree/name",
   "description": "University Degree Credential",
@@ -625,11 +625,11 @@ 
    Card Examples

    - The following example shows a valid card output: + The following example shows a valid summary output: 

    +                 title="Example summary output">
 {
   "name": "Bachelor of Science and Arts",
   "description": "University Degree Credential",
@@ -663,7 +663,7 @@ 
    Card Examples
    
     
    
 
     
    +          title="Basic usage of the 'summary' render suite">
 {
   ...
   "renderMethod": {
@@ -681,7 +681,7 @@ 
    Card Examples
    
           
    
 
           
    +               title="A remotely hosted JSON template for a summary render template">
 {
 ...
 "renderMethod": {
@@ -702,7 +702,7 @@ 
    Card Examples
    
           
    
 
           
    +               title="A remotely hosted 'summary' render method">
 {
 ...
 "renderMethod": {
@@ -1175,16 +1175,16 @@ 
    Algorithms
    
     
    
 
     
    
-      
    Card Template Processing
    
+      
    Summary Template Processing
    
       
    
-        When processing a card template, the following steps MUST be
+        When processing a summary template, the following steps MUST be
         performed:
       
    
 
       
      
         
    1. 
-          Validate the template against the card object definition in
-          [[[#card-object]]]. If validation fails, processing MUST stop and an
+          Validate the template against the summary object definition in
+          [[[#summary-object]]]. If validation fails, processing MUST stop and an
           error MUST be returned.
         
      2. 
         
    2. 
@@ -1212,8 +1212,8 @@ 
      Card Template Processing
      
           
    
         
         
  • 
-          Validate the resulting JSON object against the card object definition
-          in [[[#card-object]]]. If validation fails, processing MUST stop and
+          Validate the resulting JSON object against the summary object definition
+          in [[[#summary-object]]]. If validation fails, processing MUST stop and
           an error MUST be returned.
         
    • 
       
@@ -1618,16 +1618,16 @@ 
    SD-JWT VC Type Metadata Rendering
    
 
   
    
 
-  
    
-    
    Card Template JSON Schema
    
+  
    
+    
    Summary Template JSON Schema
    
     
    
-The following JSON Schema implements the card object rules defined in
-[[[#card-object]]], as they apply to card templates. This schema is
+The following JSON Schema implements the summary object rules defined in
+[[[#summary-object]]], as they apply to summary templates. This schema is
 non-normative.
     
    
 
     
    +         title="JSON Schema for summary templates">
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "type": "object",