# Color Model Parsing
Colorimetry parses the color model representations when creating a new instance of the Color class to give you an accurate representation of the color. This is important for any color manipulation that your application does. Expand a section to get started.
Supported color model specifiers
In addition to Colorimetry supporting RGB color model, you can also use the CMYK and other color models when creating the color instances, provided that their specifiers that you must use are:
| Syntax | Condition |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `` | `` should be of the range between 0 and 255 |
| | If `` is positive and larger than 255, it describes the color code from 256 up to 16777215 for true color instances, and anything higher than it will be wrapped to `0;0;0` and counting. |
| `` | Color name from either the `ConsoleColors` enumeration or the `ConsoleColor` enumeration |
| `#000000` | Hexadecimal representation of the color for HTML fans. |
| `;;` | ``, ``, and `` should be of the range between 0 and 255 |
| `cmyk:;;;` | ``, ``, ``, and `` should be of the range between 0 and 100 |
| `cmy:;;` | ``, ``, and `` should be of the range between 0 and 100 |
| `hsl:;;` | `` should be of the range between 0 and 360 in degrees and not radians |
| | `` and `` should be of the range between 0 and 100 |
| `hsv:;;` | `` should be of the range between 0 and 360 in degrees and not radians |
| | `` and `` should be of the range between 0 and 100 |
| `hwb:;;` | `` should be of the range between 0 and 360 in degrees and not radians |
| | `` and `` should be of the range between 0 and 100 |
| `ryb:;;` | ``, ``, and `` should be of the range between 0 and 255, just like RGB. |
| `yiq:;;` | ``, ``, and `` should be of the range between 0 and 255 |
| `yuv:;;` | ``, ``, and `` should be of the range between 0 and 255 |
| `xyz:;;` | ``, ``, and `` should be of the range between 0 and 100 in floating point units |
| `yxy:;;` | The first `<``yyy>` should be of the range between 0 and 100 in floating point units |
| | `` and the second `` should be of the range between 0 and 1 in floating point units |
| `hunterlab:;;` | `` should be of the range between 0 and 100 in floating point units |
| | `` and `` should be of the range between -128 and 127 in floating point units |
| `cielab:;;` | `` should be of the range between 0 and 100 in floating point units |
| | `` and `` should be of the range between -128 and 127 in floating point units |
| `cielab:;;;;` | Same as above, but with o and i notations. See the tip below. |
| `cieluv:;;` | `` should be of the range between 0 and 100 in floating point units |
| | `` should be of the range between -134 and 220 in floating point units |
| | `` should be of the range between -140 and 122 in floating point units |
| `cieluv:;;;;` | Same as above, but with o and i notations. See the tip below. |
| `cielch:;;` | `` should be of the range between 0 and 100 in floating point units |
| | `` should be of the range between 0 and 131 in floating point units |
| | `` should be of the range between 0 and 230 in floating point units. It should be an angle at degrees, not radians. |
| `cielch:;;;;` | Same as above, but with o and i notations. See the tip below. |
{% hint style="info" %}
The `o` and `i` notations represent the observer (2 or 10 degrees) and the illuminant number starting from zero. These two notations will be used to get the 3D reference values (`X`, `Y`, and `Z`) used for calculation. This is returned by the `GetIlluminantReferences()` function in `IlluminanceTools`.
{% endhint %}
***
## How to parse a color model specifier
To get a color instance from just the specifiers mentioned above, follow the below steps:
{% stepper %}
{% step %}
### Pick a source specifier
You'll have to pick a source specifier. For example, if you want an RGB color instance from HSV's specifier, you must have a string that holds the HSV color specifier as mentioned above.
{% endstep %}
{% step %}
### Parse the specifier
Call the `ParsingTools`'s `ParseSpecifier()` function, passing it that specifier, to get an RGB instance.
{% endstep %}
{% step %}
### Convert, if needed
You can convert the RGB instance that you obtained from the previous step to HSV using the available conversion tools that you can consult in the below page.
{% content-ref url="color-model-conversions" %}
[color-model-conversions](https://aptivi.gitbook.io/aptivi/colorimetry-manual/usage/color-sequences/color-model-conversions)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}
{% hint style="info" %}
For parsing, you have two options if you don't want to rely on exceptions:
* For boolean-based checks, you can rely on the output of the `IsSpecifierValidRgbHash()`, `IsSpecifierConsoleColors()`, and `IsSpecifierValid()` on `ParsingTools`.
* If you want to also check the values, you can consult the `...AndValueValid()` sibling functions.
You can also use the color-model-specific `IsSpecifierValid()` function, such as `RedYellowBlue`.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://aptivi.gitbook.io/aptivi/colorimetry-manual/usage/color-sequences/color-model-parsing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.