/
2026-06-08 TSC Meeting notes

2026-06-08 TSC Meeting notes

June 8, 2026

Host: Doug Walker

Secretary: Doug Walker

Attendees: 

  • Doug Walker (TSC Chief Architect) - Autodesk

  • Kevin Wheatley (TSC) - Framestore

  • Mark Titchener (TSC) - Foundry

  • Zach Lewis (TSC)

  • Sean Cooper (TSC) - Skydance Animation

  • Cuneyt Ozdas (TSC) - Autodesk

  • Scott Dyer - AMPAS

  • Chris Davies - Imageworks

Apologies:

  • Carol Payne

  • Michael Dolan

OCIO TSC Meeting Notes

  • Roadmap Updates

    • Doug reviewed the updates to the roadmap. In addition, a GitHub milestone was created to track OCIO 2.6 development.

  • Possible 2.5.3 Release

    • Based on the currently known defects, the TSC decided that a 2.5.3 release is not warranted at this time.

  • Interop ID Remaining Issues

    • Doug summarized the remaining issues that need to be resolved to finalize the Interop ID spec. We discussed this proposal. The goal is to be able to finalize this at next week’s CIF meeting.

    • Zach: The concept of having two types of namespaces (optional and non-optional) seems reasonable.

    • Kevin: The burden for the optional namespaces would be paid by the library (search with and without). For the non-optional namespaces, the burden should be on those that create them. For example, if in the future the ID changes, they would need to keep both forms as aliases.

  • “Unknown” Handling for OpenEXR Spec

    • Doug summarized that he had made another commit to the OpenEXR document based on the areas of agreement at last week’s working group meeting.

    • Zach: What was added looks good. However, would still like to see a way to handle both the unknown and unspecified situations.

    • Doug: I’m open to do that as long as we don’t change the meaning of the existing Unknown ID that is already in an issued CIF recommendation.

    • Action Item: Zach to work on a proposal for circulation prior to next week’s CIF meeting.

  • Single String Color Transform Proposal

    • Doug reviewed a proposal to create way of specifying various OCIO transforms in a single string. This came up in the recent OpenTimelineIO discussion and elsewhere.

    • Kevin: Is it necessary to specify both source and destination? For example, the proposed ColorSpaceTransform item only has one side. Doug: The thinking was that the other side would typically be known from the context, but agreed that it should be one of the values that could be included in the flexible form of the syntax.

    • Kevin: This proposal overlaps with the Interop ID. E.g., specifying the source for a ColorSpaceTransform and an InteropID are conceptually very similar. And even syntactically, the proposed flexible syntax looks very similar to an InteropID. Doug: The difference is that Interop ID is declaring what something is whereas the color transform syntax is declaring how to transform something. But agreed that there are both conceptual and syntactical similarities that warrant further consideration.

    • Zach: I think LookTransform should be added as one of the possible transform types. For example, it’s often useful to invert a plate-specific look or a gamut compression transform for compositing. Kevin: I generally bake the transform stack out as a CTF, but agree that a LookTransform option would be useful. Doug: I’ll add that to the proposal.

    • There was some discussion about the flexible syntax. Doug will give some thought to providing either a Json or Yaml version of the flexible syntax proposal.