Re: WebRenderingTemplate2022 Render Method

Thanks everyone for your feedback and help.

To start, I've opened an issue in the vc-render-method repo
<https://github.com/w3c-ccg/vc-render-method/issues/7>.

@dzagidulin@gmail.com, I'd love to discuss our approaches in the ticket and
work towards adding this method to the vc render method spec.

In the ticket mentioned, I've shared details on our implementation of
WebRenderingTemplate2022, including an example/library.

Many thanks,
Ashley

On Fri, 22 Mar 2024 at 06:47, Benjamin Young <byoung@digitalbazaar.com>
wrote:

> It definitely looks like someone or other should start a PR (and/or
> issues) to get this work headed into the render method spec, so we can
> start discussing, iterating, etc. :)
>
> Any of you folks most familiar with how this is implemented interested in
> starting things off? You should be able to copy the SVG section that's
> there now, and update it to match WebRenderingTemplate2022.
>
> Additionally, if folks have other render methods they'd like to explore,
> pull requests welcome! :)
>
> On Thu, Mar 21, 2024 at 2:31 PM Patrick St-Louis <
> patrick.st-louis@dtlab-labcn.org> wrote:
>
>> Greetings,
>>
>> @Benjamin Young <byoung@digitalbazaar.com> @dzagidulin@gmail.com
>> <dzagidulin@gmail.com>
>> The UNTP specification also makes use of this to provide visual
>> representations of VC data. They have a sample of a Digital Product
>> Passport
>> <https://uncefact.github.io/spec-untp/docs/specification/DigitalProductPassport#sample-file>
>> with a 'render' attribute referencing *WebRenderingTemplate2022*. It's
>> currently defined in this context
>> <https://vckit-contexts.s3.ap-southeast-2.amazonaws.com/dev-render-method-context.json>.
>> Any more information on this would be appreciated as we have a use case for
>> this.
>>
>> Regards
>>
>>
>>
>> On Thu, Mar 21, 2024 at 10:54 AM Dmitri Zagidulin <dzagidulin@gmail.com>
>> wrote:
>>
>>> Hi Ashley,
>>> thanks for the heads up, this is exciting!
>>>
>>> I was one of the co-authors on that renderMethod paper, and we've been
>>> also implementing WebRenderingTemplate (though we're thinking of dropping
>>> the year from it) over at Digital Credentials Consortium / Learner
>>> Credential Wallet <https://lcw.app>.
>>>
>>> We're using it to link to an HTML/CSS template, from a VC, which can
>>> then be used to render the VC as a PDF (it's a really commonly asked-for
>>> feature).
>>>
>>> We were just about to make a pull request to the RenderMethod / Web
>>> Template spec, but now that I see there's another team using some version
>>> of it, we should expedite that process :)
>>> Anyways, yeah, let's compare notes! (Maybe it'll make sense to organize
>>> a call on it, hear from various interested parties what they're doing with
>>> it).
>>>
>>> Dmitri
>>>
>>>
>>> On Thu, Mar 21, 2024 at 1:42 AM Ashley Harwood <
>>> ashley.harwood@gosource.com.au> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> Last year, we explored different render methods for integrating into
>>>> our Verifiable Credentials.
>>>>
>>>> During our investigation, we came across a method known as
>>>> WebRenderingTemplate2022 and integrated it into our solution.
>>>>
>>>> Now, as we're gearing up for conformity testing, we're making sure that
>>>> the functionality we've implemented aligns with the W3C VCDM, and similar
>>>> specifications.
>>>>
>>>> However, we're currently unable to find any further information about
>>>> WebRenderingTemplate2022 apart from this reference
>>>> <https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/cb4ae0c10a5f6bb11549c916c9247021399597ef/draft-documents/rendering-vcs-snapshot-9-27-22.md?plain=1#L503>
>>>> .
>>>>
>>>> So, was WebRenderingTemplate2022 actually a valid method? And if it
>>>> was, what happened to it?
>>>>
>>>> Many Thanks,
>>>> Ashley
>>>>
>>>>
>>>> ---
>>>> The content of this email and attachments are considered confidential.
>>>> If you are not the intended recipient, please delete the email and any
>>>> copies, and notify the sender immediately.  The information in this email
>>>> must only be used, reproduced, copied, or disclosed for the purposes for
>>>> which it was supplied.
>>>>
>>>
>
> --
> https://linkedin.com/in/benjaminyoung
> Developer Engagement Engineer
> Digital Bazaar <https://digitalbazaar.com/>
>

-- 


---
The content of this email and attachments are considered 
confidential. If you are not the intended recipient, please delete the 
email and any copies, and notify the sender immediately.  The information 
in this email must only be used, reproduced, copied, or disclosed for the 
purposes for which it was supplied.