The two different IDs for the gamut reference transform are causing vendor friction, and our documentation currently contradicts itself:
Our RGC Implementation Guide states the new one.
Our RGC Specification still states the old one.
To add to the confusion, the new one (ReferenceGamutCompress.a1.v1.0) visually reads as an older version compared to the old one (GamutCompress.a1.3.0). We need to unify these references across all documentation to ensure vendors know exactly which transformId to track in their AMF implementations.
The two different IDs for the gamut reference transform are causing vendor friction, and our documentation currently contradicts itself:
Our RGC Implementation Guide states the new one.
Our RGC Specification still states the old one.
To add to the confusion, the new one (ReferenceGamutCompress.a1.v1.0) visually reads as an older version compared to the old one (GamutCompress.a1.3.0). We need to unify these references across all documentation to ensure vendors know exactly which transformId to track in their AMF implementations.