Skip to content

Conversation

@dmitrizagidulin
Copy link
Collaborator

@dmitrizagidulin dmitrizagidulin commented Nov 13, 2025

Addresses issue #27


Preview | Diff

Signed-off-by: Dmitri Zagidulin <dzagidulin@gmail.com>
Co-authored-by: Manu Sporny <msporny@digitalbazaar.com>
@dmitrizagidulin dmitrizagidulin merged commit f1de044 into main Nov 14, 2025
@dmitrizagidulin dmitrizagidulin deleted the extension-mechanism branch November 14, 2025 02:24
@iherman
Copy link
Member

iherman commented Nov 14, 2025

This was discussed during the vcwg meeting on 14 November 2025.

View the transcript

w3c/vc-render-method#36

dmitriz: I made a pass on it, please have a look and tell if you think more is needed

phila: I strikes me as straightforward. I think we should merge, and anybody with a problem can suggest further edits.

manu_: It is not only an extension mechanism.

phila: it is an extension of VCDM.

dmitriz: question to manu_ and the group: could specific render methods (PDF, other...) be separate specifications, just like for DI?

manu_: let's not do that, this will give us too many specs to publish

brent: note that we have the freedom to break out a spec listed in our charter into separate documents

JoeAndrieu: +1, let's start with one spec; creating new documents creates overhead

dmitriz: agreed

phila: proposal "this document is an extension of VCDM, and here is how you can extend it yourself"

dmitriz: that seems reasonable

JoeAndrieu: this is also defining not just an extension of VCDM but an extension mechanism for render methods itself

phila: with that in mind, I have no problem with merging this
… we may want to extend it further

dmitriz: should I merge now, or do we have to pass the 7 days review perdio

manu_: seems editorial

phila: let's move on to the issues


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.

5 participants