[Vcon] Re: Reviews needed for vCon core I-D

[Scott Godin <[e-mail]>]

Hi Dan,

Looks great.

I have reviewed the entire draft and here are my review comments - some
comments are not specific to the new work:

   - 1.1 Awkward wording:  "This abstraction simplifies data exchange,
   apply AI-driven analysis, as well as model training and    testing."
   Suggested rewording: "This abstraction simplifies data exchange, enables
   AI-driven analysis, and supports model training and testing."
   - 4.1.1    The draft version 03 being different from the vcon version
   string 0.4.0 threw me off for a bit, before I realized they weren't really
   coupled.  Could add clarifying text.  Not very important.
   - 4.3 - text is already transcribable: Media-based Dialog Objects (type
   text and recording) SHOULD contain only media that is transcribable.  My
   first read of this confused me - why would you need to transcribe text?  I
   think it was referring to extracting text from an image, but wasn't that
   obvious.  Could add clarifying text earlier in the paragraph.
   - 4.3.1 - Dialog type - I think this section would benefit from a
   distinct subsection for each defined type
   - 4.3.4 - parties - typo - "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."
   - 4.3.5 originator - who is the originator in the case of a meeting
   recording?  The creator of the meeting?
   - 4.3.6 - recordings array pointer - consider removing this, since
   recordings point back to their set.  If left in, we have integrity issues
   that need to be resolved, ie: a recording is listed in the recording_set
   recordings array but has a pointer back to a different recording_set.
   - 4.3.16 - "string" should be "String" like elsewhere
   - Once accepted, might be good to add recording-set example to the
   appendix

Best Regards,
Scott Godin



On Sat, Jul 11, 2026 at 2:25 PM Dan Petrie <[e-mail]> wrote:

> Was: New Version Notification for draft-ietf-vcon-vcon-core-03.txt
>
> Folks:
> I have addressed ALL of the open issues that I am aware of.  In Vienna, I
> will present the fixes made to the 03 I-D and I will discuss a few open
> nits with these changes.  I think that those will result in just a few
> lines of text changes. My goal is to get this to Working Group last call
> with those last small edits.
>
> I need YOU to review this (03) version of the I-D so that it only takes
> one more iteration of edits to get this to Working Group Last Call!
>
> Cheers,
> Dan
>
> On Tuesday, June 30, 2026 at 11:39:51 PM EDT, <[e-mail]>
> wrote:
>
>
> A new version of Internet-Draft draft-ietf-vcon-vcon-core-03.txt has been
> successfully submitted by Daniel Petrie and posted to the
> IETF repository.
>
> Name:    draft-ietf-vcon-vcon-core
> Revision: 03
> Title:    The JSON format for vCon - Conversation Data Container
> Date:    2026-07-01
> Group:    vcon
> Pages:    130
> URL:      https://www.ietf.org/archive/id/draft-ietf-vcon-vcon-core-03.txt
> Status:  https://datatracker.ietf.org/doc/draft-ietf-vcon-vcon-core/
> HTML:    https://www.ietf.org/archive/id/draft-ietf-vcon-vcon-core-03.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-vcon-vcon-core
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-vcon-vcon-core-03
>
> 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 Secretariat
>
>
>