From 4e0d9137b7b48382e452ad792c5874f0db61d5e3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Je=C5=BEek?= Date: Mon, 16 Jan 2023 14:21:32 +0100 Subject: [PATCH] Update website/docs/dev_colorspace.md Co-authored-by: Roy Nieterau --- website/docs/dev_colorspace.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/docs/dev_colorspace.md b/website/docs/dev_colorspace.md index bfc7e0e328..c844c1932f 100644 --- a/website/docs/dev_colorspace.md +++ b/website/docs/dev_colorspace.md @@ -15,7 +15,11 @@ Adding the `imagio` settings schema is required for any host or module which is ::: ## Data model -The *colorspaceData* are stored at root of representation dictionary during publishing. Once they are integrated into representation db document they are stored as *representation_doc.data["colorspaceData"]* +Published representations that are extracted with color managed data store a **colorspaceData** entry in its data: `representation_doc["data"]["colorspaceData"]`. + +It's up to the Host implementation to pre-configure the application or workfile to have the correct OCIO config applied. +It's up to the Extractors to set these values for the representation during publishing. +It's up to the Loaders to read these values and apply the correct expected color space. ### Keys - **colorspace** - string value used in other publish plugins and loaders