...
Applications should use standard roles for appropriate color space assignment when possible. If a role for a specific use case in the app doesn’t exist, the app should support an app-specific custom role. App-specific roles should adhere to the naming convention:
| Code Block | ||
|---|---|---|
| ||
<app name>_<use/task> (e.g. “mari_blending”) |
...
App-specific roles should default to inheriting their color space from a standard role. This default should be clearly documented in a role table. Example: https://learn.foundry.com/mari/Content/user_guide/managing_colors/color_management.html
Undefined Roles
If a config does not define a given role, it is an indication to the application that it may ask the user to select one of the color spaces from the config. Typically a config authored by a facility color scientist for a specific show will chose a specific role, but generic configs (e.g. those produced by the OCIO working group) may omit the roles in cases where there is more than one viable solution depending on the details of a specific workflow.
...