- From: Otto Mora <omora@privado.id>
- Date: Fri, 3 Jan 2025 16:55:49 -0600
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>, Kim Hamilton <kimdhamilton@gmail.com>
- Message-ID: <CACRdrhCA+GH_VJHeZ3tjFEukaDTYG6NoAJq8Tce1UeBevm5+AA@mail.gmail.com>
*Hi Manu,* Thanks for raising this. We socialized this initiative at IIW this past fall. We presented an initial schema standardization effort for Age Verification and Estimation. The discussion centered around the development of a general purpose age schema which would allow for both “age estimation” (several assurance methods to be used) as well as “age verification”. I presented an early draft of the data fields being considered for the schema spec. The group provided feedback regarding the fields and also suggested additional ones to be considered. One of the participants pointed me out to existing solutions for age verification in the industry, including https://www.mytruage.org as well as the support of age verification included in the credit card payment networks (EMV). My understanding is that "My True Age" is following the Connexus spec. We are open to discussing how to better collaborate with Connexus / NAC. That website you shared indicates that the main overlap is on the Age Token credential ( https://convenience-org.github.io/age-vocab/#OverAgeTokenCredential ). From my analysis the age token credential is actually a subset of our "Proof of Age" schema. The only field that overlaps is the "overAge" field. The schema itself is being used by Privado ID / Iden3 in the web3 space for platforms that want to age-gate adult content (I am involved in some of these discussions currently). We would be open to discussing this with Connexus so that their Age Token credential aligns well with our more general Proof of Age schema proposal. Do you think we could propose a meeting to explore collaboration? Regards, Otto Mora Product Evangelist otto@privado.id privado.id * <https://x.com/PrivadoID>* <https://www.linkedin.com/company/privado-id> <https://www.youtube.com/@PrivadoID> We have spun off from Polygon ID to Privado ID; hence, *our email addresses will be changing* from polygon.technology to privado.id On Fri, Jan 3, 2025 at 9:42 AM Manu Sporny <msporny@digitalbazaar.com> wrote: > On Thu, Jan 2, 2025 at 6:52 PM Kim Hamilton <kimdhamilton@gmail.com> > wrote: > > Decentralized Identity Foundation (DIF) invites you to join us Jan 28th > at 10am PST for our Proof of Age Workshop exploring privacy-preserving age > verification solutions, including our plans for development of a > standardized credential schemas for the Age Verification and Age Estimation. > > Hmm... seems like DIF might be duplicating work that has already been > done (and is being actively maintained). > > There exist open standards for digital age verification (using VCs) > that are in production and integrated into point of sale systems with > 80%+ market share of the convenience retail ecosystem. This is what > has been deployed in production for over a year with California DMV, > for example. CCG has had presentations on this: > > https://www.conexxus.org/resources/age-verification-initiative > https://www.conexxus.org/public-standards (see Conexxus Age > Verification API Specification) > https://w3id.org/age/ > > Those of us involved in that initiative won't be able to attend the > Jan 28th DIF meeting because there will be another meeting on that day > at the Conexxus Annual Conference on the very topic of digital age > verification. > > -- manu > > -- > Manu Sporny - https://www.linkedin.com/in/manusporny/ > Founder/CEO - Digital Bazaar, Inc. > https://www.digitalbazaar.com/ >
Received on Friday, 3 January 2025 22:56:05 UTC