Re: Request for Editor permission to add OpenAttestationRenderMethod

There seems to be a fair level of interest around renderMethods. During IIW
Dimitri and I were pondering on the idea of starting a vc-render-method
taskforce with biweekly meetings. This would be great to ensure there's no
duplication of work and keep track of the progress.

If there's enough interest/participants in starting this effort I would be
happy to facilitate.

Would it make sense to follow the model of the vc specifications directory
<https://w3c.github.io/vc-specs-dir/#adding-a-specification-entry> to
manage adding the different methods proposed in this thread?

BCGov and I will be looking at implementing the OverlayCapture method, we
will also implement the RenderMethod2024 proposed by Steve and Ashley.

Regards

On Tue, May 14, 2024 at 10:42 PM Sin Yong LOH (IMDA) <
LOH_Sin_Yong@imda.gov.sg> wrote:

> Message Classification: Restricted
>
> Hi Steve,
>
> Let's collaborate since we are also working on this. The last thing we
> want is to have each of us having a different implementation that are not
> interoperable.
>
> I have added my colleagues Hendry and Issac into this conversation.
>
> cc. Calvin - Please don't forget to include us in this exercise. Thanks.
>
> Sin Yong, Loh
> Director
> TradeTrust / Digital Utilities Cluster
> (65) 6751 2763
>
>
> -----Original Message-----
> From: Steve Capell <steve.capell@gmail.com>
> Sent: Wednesday, May 15, 2024 2:54 AM
> To: Manu Sporny <msporny@digitalbazaar.com>
> Cc: Calvin CHENG (GOVTECH) <Calvin_CHENG@tech.gov.sg>; Patrick St-Louis <
> patrick.st-louis@dtlab-labcn.org>; public-credentials@w3.org; Ashley
> Harwood <ashley.harwood@gosource.com.au>; Nam Hoang <
> nam.hoang@gosource.com.au>; Sin Yong LOH (IMDA) <LOH_Sin_Yong@imda.gov.sg>
> Subject: Re: Request for Editor permission to add
> OpenAttestationRenderMethod
>
> Hi Calvin
>
> Nice to see you in this community !
>
> We are also preparing an html render template spec - which is very similar
> to OA except it’s a hash link to the external rebderer (just to prevent an
> attack where someone manipulates a rebderer to present something not in the
> vc)
>
> Perhaps we should collaborate with the govtech team on this?
>
> Steven Capell
> Mob: 0410 437854
>
> > On 14 May 2024, at 3:53 PM, Manu Sporny <msporny@digitalbazaar.com>
> wrote:
> >
> > On Tue, May 14, 2024 at 3:21 AM Calvin CHENG (GOVTECH)
> > <Calvin_CHENG@tech.gov.sg> wrote:
> >> Other than that, I would propose for both myself @cxcheng, and my
> colleague Kyle @HJunyuan be given the permission to submit PRs.
> >
> > Done (see Editors/Authors list at top of spec now):
> >
> > https://w3c-ccg.github.io/vc-render-method/
> >
> >> We can work together, but probably focus on editing our respective part
> of the render method spec.
> >
> > Sounds good.
> >
> >> Currently, the organization of the document is focused on
> >> SvgRenderTemplate2023. I propose we break it up to have each render
> >> method have its own section on “Data Model”, “Algorithms” (API is
> >> more appropriate for us),
> >
> > Sounds good. Do you expect something like adding these sections?
> >
> > Data Model:
> >
> > * OpenAttestationSOMETHING
> > * OverlayCaptureSOMETHING
> >
> > Algorithms:
> >
> > * Render (OpenAttestationSOMETHING)
> > * Render (OverlayCaptureSOMETHING)
> >
> >> “Security Considerations”, “Privacy Considerations”,
> “Internationalization Considerations” are better put into each method’s own
> section.
> >
> > I wouldn't split these up for now because W3C presumes a single
> > section for each of those considerations. What we tend to do is give
> > general guidance, and then note which render methods that general
> > guidance applies to. For example, we might provide general guidance
> > for "Server-based Rendering" and then provide a Privacy warning noting
> > that doing so could result in the server viewing Personally
> > Identifiable Information. We'd then say which render methods are
> > covered by that privacy consideration.
> >
> > The three of you have full rights to open PRs now. When you do so,
> > please 1) keep your PR simple and easy to review (a few paragraphs or
> > a section or two at a time), 2) keep your commit messages clean
> > (simple, active voice, under 50 characters, ideally). All the Editor's
> > will be pinged for a review, and my hope is that we can get things
> > merged quickly to just make sure we have new content going into the
> > spec at a rapid clip for the first few months.
> >
> > -- manu
> >
> > --
> > Manu Sporny - https://www.linkedin.com/in/manusporny/
> > Founder/CEO - Digital Bazaar, Inc.
> > https://www.digitalbazaar.com/
> >
>