RE: [Agenda] W3C CCG 2023-11-07- TruAge Verification

Hi Manu, all.

Thanks for the very nice presentation. I have some questions related to that.

- Are there any technical specifications of the platfrom available? 
- If I understand correctly, those "one time tokens" are VCs. Is that correct?
- In slide 18 ("HOW DOES THE TRUAGE APP WORK?") I see that the cashier communicates with the truage system when a customer presents a token. I understand that this happens in order to "burn" the token. Is this correct? Does this creates privacy risks (e.g., the TruAge system know with customers the client communicates)? 
- If I understand correctly all one time tokens are created upfront. Is there any reason for this design choice? An alternative could be that the customer app requests (and receives) a short-live token just before the purchase. 
- How "CCG Authorization Capabilities (ZCAPs)" are used in the system?

Thanks a lot,

-----Original Message-----
From: Manu Sporny <> 
Sent: Sunday, November 5, 2023 6:27 PM
To: W3C Credentials CG (Public List) <>
Subject: Re: [Agenda] W3C CCG 2023-11-07- TruAge Verification

On Wed, Nov 1, 2023 at 12:37 PM Harrison <> wrote:
> Main Agenda: TruAge Verification
> We are excited to have Manu Sporny lead the discussion on "TruAge Verification" at our W3C CCG meeting next Tuesday.

Please find the slide deck for this week's CCG presentation on TruAge digital age verification using W3C Verifiable Credentials attached to this email.

In the presentation, we'll be covering the business driver, technical design, privacy design, and W3C and CCG technologies used to create the TruAge system including lessons learned when deploying it into production and integrating it with partner systems (such as DMVs).

-- manu

Manu Sporny -
Founder/CEO - Digital Bazaar, Inc.

Received on Tuesday, 14 November 2023 10:10:56 UTC