[Vcon] Parties Vs Terminals?

["Ed Guy (BLOOMBERG/ 919 3RD A)" <[e-mail]>]

"""
4.3.4. parties
The party(s) which generated the text or recording for this piece of dialog are indicated in the parties parameter.
*parties: "UnsignedInt" | "UnsignedInt[]" | ("UnsignedInt" | "UnsignedInt[]")[]
Single channel recordings should have a parties value of the form: "UnisignedInt" or "UnsignedInt[]" where the integer value or array of integer values are the indices to the Party Object(s) in the parties array that contributed to the mix for the single channel recording. The index for the Party Object SHOULD be included even if the indicated party was silent the entire piece of dialog.Multi-channel recordings MUST have a parties value that is an array of the same size as the number of channels in the recording. The values in that array are either an integer or an array of integers which are the indices to the parties that contributed to the mix for the associated channel of the recording. The index for Party Objects SHOULD be included even if the party was silent the entire conversation.
"""

Seems to me that we are confusing "Parties" and "Terminals."  We frequently have multiple speakers in a conference room using one speakerphone.  Stream analysis / diarisation individually identifies them on that Terminal which would be very difficult to have a separate channel for each speaker.  Edge cases may even have a Speaker migrating between channels during a conversation, e.g., leaving a conference room and hopping on a mobile phone.

Do we need a 'terminal" object so that channels may be mapped to sets of speakers? 


From: [e-mail] At: 01/26/26 17:04:29 UTC-5:00To:  [e-mail],  [e-mail]
Subject: [Vcon] Re: I-D Action: draft-ietf-vcon-vcon-core-02.txt

         
Hi Folks:
I am sorry, I forgot to do run spell check before submitting the 02 version.  Please know that I have already corrected these in the repo.
https://ietf-wg-vcon.github.io/draft-ietf-vcon-vcon-core/#go.draft-ietf-vcon-vcon-core.html

Cheers,
Dan

                 
            
                                 
                    On Wednesday, January 21, 2026 at 10:12:59 PM EST, Daniel Petrie <[e-mail]> wrote:                                  

                 

                 
         
Hi Folks:
I have updated the vCon core I-D with all of the issues that we resolved at the IETF 124 WG meeting.  There remains half a dozen fairly simple open issues to discuss at the interim vCon WG meeting next week: Jan 27 12:00 US Eastern time.  These are mostly issues of deciding which of more than one way to resolve the thing should we use.  I will prepare slides for the resolved issues and the issues to be decided.  However I am not sure these will be available much before the interim as I am doing a bunch of travel between now and then.

Happy reading and no reason wait for the interim to bring up any issues while you are reviewing.  Submit them to the list.

I hope to see you all on Tuesday next week!

Cheers,
Dan

                 
            
                                 
                    On Wednesday, January 21, 2026 at 10:03:03 PM EST,  <[e-mail]> wrote:                                  

                 

                 
Internet-Draft draft-ietf-vcon-vcon-core-02.txt is now available. It is a work
item of the Virtualized Conversations (VCON) WG of the IETF.

   Title:   The JSON format for vCon - Conversation Data Container
   Author:  Daniel G Petrie
   Name:    draft-ietf-vcon-vcon-core-02.txt
   Pages:   125
   Dates:   2026-01-21

Abstract:

   vCon is a standardized framework for the exchange of conversational
   data.  Conversations, which may involve one or more participants,
   occur across a wide variety of modes and application platforms.  This
   document defines a JSON format for representing conversational data,
   encompassing metadata, conversation media, related documents, and
   analysis.  The goal of this standard is to provide an abstracted,
   platform-independent data format for conversations, regardless of the
   mode or application platform.  By doing so, it facilitates the
   integration and seamless exchange of conversational data across
   application platforms, enterprises, and trust boundaries.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-vcon-vcon-core/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-vcon-vcon-core-02.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-vcon-vcon-core-02

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


-- 
Vcon mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]
                    
-- 
Vcon mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]
                             -- 
Vcon mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]