1. Administrative and Agenda Review
   • Attendees were reminded to log in, join the microphone queue, and
   respect the online participants.
   • Agenda was presented with no objections to additions or
   deletions.
   • Resources and document links were provided.

2. Document Structure and Status Update
   • Original VCon draft was split into three separate documents:
   • Overview (informational, use cases)
   • Core protocol (technical schema and format)
   • Contact Center Extension (application-specific extensions)
   • Two additional documents were adopted:
   • Privacy Primer
   • Mimi Messages
   • Authors confirmed coordination on the split and updated drafts.

3. Overview Presentation (Thomas McCarthy)

Key Concepts:
• VCon: A “conversation container” akin to vCard but for conversations.

• Encapsulates multimedia (audio, video, chat, etc.) involving humans,
formatted in JSON (vs. CBOR).
• Enables interoperability between applications and systems, with
benefits in data portability, analytics, and compliance.

Container Structure:
• Parties: Human participants, identified by phone, STIR tokens, or
DIDs.
• Dialogues: Actual conversations, indexed and cross-referenced with
parties.
• Analysis: Derived or processed data (e.g., transcripts, sentiment).
• Attachments: Context (e.g., leads, consent documents).

Discussion:
• Strong objection raised (Dan) against allowing imagery in
Dialogues—should be Attachments.
• Consensus: Imagery belongs in Attachments unless strictly
transcript-like (e.g., Mimi messages).
• Suggestion to formalize this distinction.
• Query raised about ML model attribution—clarified this is supported
via schema/vendor fields in the Analysis section.

1. Real-World Use Cases & Implementation Status
   • Use Cases: Contact centers, healthcare, messaging, and ECRIT.
   • Implementation: 2 of 3 use cases have existing implementations;
   healthcare work ongoing.
   • Format: Remains JSON for developer accessibility, despite CBOR’s
   technical advantages.

2. VCon Core Schema Updates (Dan Petrie)

Document Changes:
• All three drafts confirmed as Working Group items.
• Notable core changes:
• Added SIP URL and DID support to Party object.
• Session ID added to Dialogue.
• Consistent hashing format.
• Removed inline beacons from redacted/amended forms.
• Hyphenated parameters renamed with underscores.
• GZIP allowed for signed/encrypted VCons.
• Deep copy model adopted for amended (formerly “appended”) VCons.
• Patched model deferred to future extension.

Amended vs Patched:
• Amended (new term replacing “Appended”): Deep copy of full prior VCon
+ changes.
• Patched: Incremental diffs (e.g., using JSON Patch). Will be defined
in future extension.
• Discussion raised about renaming and possibly generalizing
transformation lineage (e.g., OpenLineage-style graph). Consensus to
keep Amended and define Patched separately.

1. Extension and Versioning Mechanism
   • Consensus to deprecate top-level version field in favor of
   extension-based versioning.
   • Introduced:
   • extensions field: lists all applied extensions.
   • critical (or must-support): indicates breaking/incompatible
   extensions requiring app understanding.
   • QLog approach reviewed; suggestion made to consider using URIs
   vs. type names for proprietary extension identifiers.

2. Interoperability and Hackathon Update
   • First VCon interop held in Hyannis: 9 implementations
   participated.
   • Hackathon follow-up:
   • Multiple implementations updated.
   • Discussions resolved approach to versioning and extensions.
   • Encoding field issue identified and will be clarified.
   • More test cases (e.g., call transfer) requested.

3. Contact Center Extension
   • Split from core; IANA registries added for new parameters.
   • Parameters not deemed CC-specific retained in Core (e.g.,
   application name, disposition).
   • Party UUID and DID will remain separate per feedback.
   • More values for interactionType still needed (Jonathan to
   provide).

4. Consent Attachment Proposal (Thomas McCarthy & Steve Lasker)

Overview:
• Standardized Consent Attachment proposed for inclusion in VCon.
• Enables structured, interoperable consent recording and verification.

• Includes fields: expiration, party, dialogue, and array of consents
(true/false with types).
• Optional: terms of service, consent ledger URLs, proof objects, and
update intervals.

Discussion:
• Dan Petrie suggested it may be better as an extension vs. an
attachment.
• Concern raised about hardcoding to SCITT; consensus to generalize to
support other mechanisms.
• Request for clear policy on revocation—what to do if consent is
withdrawn.
• Thomas referenced a forthcoming Life Cycle document that defines
those semantics.
• Linking model debated: should Dialogues reference Consents or vice
versa?
• Agreement that multiple Dialogues can map to a single Consent object.

• Legal critique (Dan Gillmor): cautioned against treating participant
consent as equivalent to data subject consent (e.g., when referring to
third parties not in the conversation).
• Action: Add disclaimer text clarifying presence of consent ≠ lawful
basis.

1. Open Issues and Next Steps
   • Action needed on:
   • MIME/media types feedback from IANA.
   • Incorporating consent lifecycle reference in draft.
   • Review extension naming model (QLog vs. type strings).
   • Continue Consent and Life Cycle discussions on list.
   • Define and implement Patched object in future work.
   • Confirm Amended naming and behavior.

Decisions Made
• Renamed “Appended” to Amended in Core.
• Deferred Patched to future extension draft.
• Deprecated version parameter in favor of extensions + critical model.

• Adopted Consent Attachment proposal; further refinements to be made.

• Contact Center extension accepted; additional values and feedback to
be incorporated.