Rec.2020 Coverage Note Lookup
Rec.2020 coverage semantics, no fabricated universal gamut-coverage fraction. Explicit declared color space/reference and caller applicability; not spectral equivalence, pigment mixing, press readiness or accessibility certification.
Description
A color gamut specifies a range of representable chromaticities under a declared model.
A color gamut specifies a range of representable chromaticities under a declared model.1
A wider set of primaries alone does not determine content coverage or an HDR luminance range. Use Rec.2020 Coverage Note Lookup to read a supported reference-card topic.
When to use Rec.2020 Coverage Note Lookup
Use Rec.2020 Coverage Note Lookup to read a supported reference-card topic. Choose an exact supported token from the table, preserving punctuation and capitalization.
How to use Rec.2020 Coverage Note Lookup and understand its results
- Choose an exact supported token from the table, preserving punctuation and capitalization.
- Enter Coverage question using the field table and validation rules below, then run the tool.
- Read Meaning; interpret the units, signs, ordering and unknown-value placeholders described below.
- Read the selected stored entry in the context described below. The tool does not retrieve additional source material; correct unsupported tokens before rerunning.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| coverageQuestion | Coverage question | string | Required; constraints below |
Enter one of the exact supported coverageQuestion tokens listed below. The implementation performs a case-sensitive own-key lookup and returns the stored text unchanged. It does not fetch the cited books, search a corpus or inspect current policy. Unsupported tokens and added whitespace are input errors. The entries are stored summaries rather than retrieved source passages; read the stated scope and assumptions alongside the selected topic. This bounded card is not a complete reference database.
returned text = storedTable[exactSupportedToken] Use the field order, units and branch conditions described above.
| Exact supported token | Stored reference text |
|---|---|
| rec 2020-versus-srgb | Rec.2020 specifies different RGB primaries; gamut inclusion is not a content coverage percentage |
| coverage-percent | A percentage requires a declared color volume/area metric, white point and sampled gamut boundary |
| hdr | Rec.2020 primaries do not by themselves establish an HDR transfer function or luminance range |
| Output field | Meaning | Value type |
|---|---|---|
| meaning | Stored explanation for the exact supported token. | string |
{
"input": {
"coverageQuestion": "coverage-percent"
},
"output": {
"meaning": "A percentage requires a declared color volume/area metric, white point and sampled gamut boundary"
}
}Limitations and assumptions
A wider set of primaries alone does not determine content coverage or an HDR luminance range. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use D50 vs D65 White Point Delta E for a related task: Color differences need coordinates expressed under one comparable reference convention.
Use Spectral Band Name From nm Lookup for a related task: Wavelength-band names depend on an explicitly chosen range convention.
References
-
Rec.2020 Coverage Note Lookup — tool.io
Similar or alternative tools
- D50 vs D65 White Point Delta E
Color differences need coordinates expressed under one comparable reference convention.
- Spectral Band Name From nm Lookup
Wavelength-band names depend on an explicitly chosen range convention.