[Vcon] Re: vCon JSON Schema

[Rohan Mahy <[e-mail]>]

One very positive consequence of having a JSON Schema now is that we can
get rid of IANA registration of non-standards track extension points, and
greatly reduce the number of registries that need to be maintained.
IANA registering every field was not maintainable for implementers.
Thanks,
-rohan


On Wed, 21 Jan 2026, 01:53 Daniel Petrie, <[e-mail]> wrote:

> Hi Rob:
> Thank you so much for reviewing and testing the vCon JSON schema!
>
> I have merged in you PR and the Schema is now included in Appendix B of
> the I-D (in the repo, not yet submitted).
>
> WRT the versioning and the version URL, we had some extensive in meeting
> and side bar discussions on this at IETF 122 and 123.  I think that the
> named extensions construct is the consensus of those discussions (defined
> in section 1.2 and 2.5) and solves this problem in the best way.  I am
> happy to discuss if folks want to reopen this.
>
> Cheers,
> Dan
>
> On Friday, November 28, 2025 at 11:31:07 AM EST, Rob Sliwa <
> [e-mail]> wrote:
>
>
> Dan,
>
> I run this schema through the validator of my Go vCon implementation, and
> it worked beautifully.  I did notice two minor issues in the Dialog
> definition and submitted a PR to address them:
> https://github.com/ietf-wg-vcon/draft-ietf-vcon-vcon-core/pull/23
>
> BTW, for versioning, would it make sense to adopt URL based pattern and
> publish schema versions accordingly?  For example,
>
>
> https://github.com/ietf-wg-vcon/draft-ietf-vcon-vcon-core/blob/main/vcon-0.4.0.json_schema.json
>
> https://github.com/ietf-wg-vcon/draft-ietf-vcon-vcon-core/blob/main/vcon-0.5.0.json_schema.json
>
> Thanks,
> Rob
>
> *From: *Daniel Petrie <[e-mail]>
> *Date: *Wednesday, November 26, 2025 at 3:15 PM
> *To: *VCon WG <[e-mail]>
> *Subject: *[Vcon] vCon JSON Schema
>
> Hi Folks:
> I have received requests for the JSON Schema for vCon in person, via email
> and at the Montreal WG meeting.  I have taken a first pass at putting one
> together.  I have not tested it or verified it in any way.  I have only
> validated that it is a valid JSON document.  I have not yet researched or
> picked my tools to do so.  I am putting this out for folks to review.
> Please provide PRs.  I asked for your help with this at the Montreal WG
> meeting.  This is where you step up.
>
> I may have missed a few things.  I am not sure what to do yet with the
> vcon/version property yet.
>
>
> https://github.com/ietf-wg-vcon/draft-ietf-vcon-vcon-core/blob/main/vcon_json_schema.json
>
> If you are in the US, have a Happy Thanksgiving!
> If you are in the Northern Hemisphere, Happy Fall Harvest!
> If you are in the Southern Hemisphere, Happy Spring!
>
> Cheers,
> Dan
>
>
> --
> 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]
>