Skip to content
This repository was archived by the owner on Nov 14, 2025. It is now read-only.

Update to TemplateRenderMethod and consider re-evaluating the use of in-lined render templates #421

@absoludity

Description

@absoludity

Now that TemplateRenderMethod has been released and supersedes the render methods we've used up until this point, we should update to both use and recommend that (it's much more general and has had more eyes looking at it).

The TemplateRenderMethod still allows in-line templates, but also provides good support for linking to external templates with integrity checks (using digestMultibase) (see the related #408).

I dived into the current rendering support because I'm trying to understand why we are recommending in-lined templates. I've tried to find the history for the decision to in-line a template (and potentially logos / images) within the credential itself. The trail is as follows:

Other than our WebRenderingTemplate2022, none of the above assumes or prefers inlined templates, while still allowing people to use inlined templates if they want to.

I personally think we should do the same: when we update to TemplateRenderMethod, let's demonstrate links to external templates with integrity via the digestMultibase field by default, while also demonstrating how you can use an inline template to develop your template initially (but talk about the cons of inlining your template in all the credentials you issue). Looking at the advantages (of in-lined templates, I think that's implied) on https://github.com/w3c-ccg/vc-render-method/issues/7 , I think (personally) the only one which is an advantage is the ease of creation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    WG-TechnicalIssues for the technical working group

    Type

    No type

    Projects

    Status

    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions