From d6cbfe1b9aaa54441b89d5e18676c5417b3bb36f Mon Sep 17 00:00:00 2001
From: Sebastian Wick <sebastian@sebastianwick.net>
Date: Tue, 8 Sep 2020 03:39:35 +0200
Subject: [PATCH] color management: require compositors to understand all EOTF,
 ...

... chromaticity and whitepoint names from the protocol

Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>
---
 unstable/color-management/color-management-unstable-v1.xml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/unstable/color-management/color-management-unstable-v1.xml b/unstable/color-management/color-management-unstable-v1.xml
index 7d32bd3..7406818 100644
--- a/unstable/color-management/color-management-unstable-v1.xml
+++ b/unstable/color-management/color-management-unstable-v1.xml
@@ -39,7 +39,6 @@
     </description>
 
     <enum name="eotf_names">
-      <!-- FIXME How does a client know what server supports? -->
       <description summary="well-known EOTF names">
 	Names that describe a well-known EOTF
       </description>
@@ -48,7 +47,6 @@
     </enum>
 
     <enum name="chromaticity_names">
-      <!-- FIXME How does a client know what server supports? -->
       <description summary="well-known chromaticity names">
 	Names that describe well-known chromaticities
       </description>
@@ -57,7 +55,6 @@
     </enum>
 
     <enum name="whitepoint_names">
-      <!-- FIXME How does a client know what server supports? -->
       <description summary="well-known whitepoint names">
 	Names that describe well-known whitepoints
       </description>