Add outputPreference terms section.#51
Conversation
iherman
left a comment
There was a problem hiding this comment.
As discussed offline with @BigBlueHat : the normative references to https://w3c.github.io/cg-reports/a11y-discov-vocab/CG-FINAL-vocabulary-20260128/ are probably o.k., in spite of the fact that the target is a CG document. It is, presumably, a stable document and abides to the requirements on normative references. But it is probably a good idea to check this with the document editors.
Co-authored-by: Ivan Herman <ivan@w3.org>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com> Co-authored-by: BigBlueHat <byoung@bigbluehat.com>
|
Normative, multiple reviews, changes requested and made, no objections, merging. |
|
This was discussed during the vcwg meeting on 19 May 2026. View the transcriptAdd outputPreference terms section. by BigBlueHat · Pull Request #51 · w3c/vc-render-method · GitHubManu_Sporny: Okay, great. <Benjamin_Young> Mustache in HTML Render Method for folks to check out: vc-examples/credentials/html-render-method-mustache at main · credential-handler/vc-examples · GitHub Manu_Sporny: right, that looks good. Then let's go ahead and merge unless anybody has any objections. Looks like I approved as and this is normative, right? No objections. Benjamin_Young: Yeah,… Benjamin_Young: it adds a new should section. No, I don't think so. Manu_Sporny: And rebase and merge. Thank you very much for that one, Benjamin. And did this address an issue that you can think of that you can All right. Benjamin_Young: This was born out of the HTML render method coming into being without some of the things that SVG, Mustache, and other things had. Manu_Sporny: right. Manu_Sporny: Then let's go ahead and jump to the other issue that you raised which is discussing PDF rendering expectations. That's issue 53. over to you Benjamin. |
This is still early stage content, but posting it for review/feedback before finalizing anything.
Preview | Diff