Description
Check hyphenated UUID shape and compare its version nibble with an expected value.
Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.
Check hyphenated UUID shape and compare its version nibble with an expected value.
When to use this tool
Use Uuid Version Nibble Consistency when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.
How to use the tool and how it works
- Enter uuid, expected. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, version, matches. Inspect valid, matches before interpreting the associated values.
Require expected from zero through 15. Check canonical hyphenated UUID hexadecimal shape, extract the version nibble at zero-based position 14 when shaped correctly, and return matches when it equals expected.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| uuid | Uuid | Required. Text; maximum UTF-16 length 8192. |
| expected | Expected | Required. Safe integer; minimum 0; maximum 15. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
| version | Parsed version nibble or zero placeholder when valid is false. | Required. Safe integer. |
| matches | Whether the supplied values match under the particular stated rule. | Required. Boolean. |
{
"input": {
"uuid": "550e8400-e29b-41d4-a716-446655440000",
"expected": 4
},
"output": {
"valid": true,
"version": 4,
"matches": true
}
}Limitations and assumptions
- Malformed UUID spelling returns valid false and version zero, so zero is not evidence of a parsed version. Variant bits, reserved values, UUID generation, and identifier assignment are not validated.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.
References
Similar or alternative tools
- Uuid Variant Bit Pattern Check
Classify an integer octet from zero through 255 by leading bits: below 128 as ncs, below 192 as rfc, below 224 as microsoft, and the remainder as future.
- Ark Qualifier Leading Separator Check
Return valid when qualifier is empty or starts with slash or dot.