RE: Request for Editor permission to add OpenAttestationRenderMethod

Hi Steve, it has been awhile. 

We have worked on adapting our OpenAttestation data model to be compliant with the W3C VC Data Model 2.0 including our render method. As soon as we have an updated spec, we will share with you.

This Email is filed in GovTech DRMS
<https://drms.in.tech.gov.sg/?xmail-id=43af8579-b30a-4c1e-8e8a-da281e4f3005>
[3S-id=43af8579-b30a-4c1e-8e8a-da281e4f3005:a0a98837]

-----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/

>

Received on Thursday, 16 May 2024 00:31:59 UTC