03 December 2024

Meeting recording

Attendees

Andy Rosen, Sequence Key
Christian Paquin, Microsoft
Cole Davis, Switchchord
David Bigsby, Government of British Columbia
Eric Scouten, Adobe
Hans Granqvist, Noosphere
Jeremy Uzan, Universal Music
Karen Kilroy, FileBaby
Liviu Gheorghe, Adobe
Peleus Uhley, Adobe
Philippe Rixhon, JPEG Trust
Richard W. Kroon, EIDR
Utkarsh Sharma, Vlinder

Meeting notes

New members introduction

🎥 0'50": Jeremy Uzan, Universal Music

Review previous action items

🎥 1'36": All action items from 11 November 2024 resulted in merged PRs, except for:

ACTION: Eric to review current revocation mechanisms and draft a PR describing at least one preferred revocation mechanism. → TRACKING: Added comment to existing issue #171: Recommend (require?) use of bitstring status lists for revocation?.
ACTION: Eric to follow up on feedback provided by Philippe on more concrete examples for how constrained might be defined in training and data mining assertion. → TRACKING: Filed as issue #7: Provide a better definition of constrained.

Overall review of identity claims aggregation model

🎥 2'51": From previous meeting:

Aside from issues flagged for 1.1 release and PRs being discussed today, what open issues / blockers / concerns do you have about the identity claims aggregation model being added in 1.1?

Members expressed support for the model, highlighting its usefulness in providing assertions that cannot be easily validated without a trusted aggregator.

Eric reiterated that there are some issues flagged as blockers for version 1.1 that still need to be addressed before ratification.

Review PR #188: Add support for verified web site

🎥 5'15": Review revised version of existing PR #188: Add support for verified web site.

Eric presented a revised proposal for verified websites, which simplifies the verification process by removing prescriptive language about using meta tags.

Members agreed with the new approach, noting that there could be multiple ways to verify websites, and the proposal is on the right track.

Christian and David raised concerns about the lack of detail on how verification methods are performed, suggesting the need for a descriptor or protocol identifier to ensure the level of assurance. Eric agreed to draft a proposal for allowing identity claims aggregator to describe its verification method. → TRACKING as issue #202 and flagged as a blocker for 1.1 ratification.

ACTION (✅): Eric to rename verified identity type from cawg.domain_control_validation to cawg.web_site and merge.

Proposal to split identity assertion spec into core data model spec and separate "methods" specs

🎥 40'58": Eric suggested decoupling specific methods such as the current §8.1 and §8.2 from the identity assertion spec and creating separate specs for each method, similar to the DID protocol and methods.

The group discussed the potential benefits and challenges of this approach, including the possibility of creating a more modular and flexible framework.

No clear outcome. Will revisit in a future meeting.