Description
Check token for exactly one percent sign and two hexadecimal digits.
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 token for exactly one percent sign and two hexadecimal digits.
When to use this tool
Use URI Percent Triplet Ascii Check 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 token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, octet, ascii. Inspect valid, ascii before interpreting the associated values.
Check token for exactly one percent sign and two hexadecimal digits. Return its octet when valid and zero otherwise; ascii requires a valid triplet with octet no greater than 127.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
| octet | Decoded byte or zero placeholder for malformed token. | Required. Safe integer. |
| ascii | Ascii | Required. Boolean. |
{
"input": {
"token": "%41"
},
"output": {
"valid": true,
"octet": 65,
"ascii": true
}
}Limitations and assumptions
- The zero octet is a placeholder when valid is false. This checks one escape token, not UTF-8 decoding, a complete URI, or whether the byte is allowed in a particular component.
- 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
- Ark Qualifier Leading Separator Check
Return valid when qualifier is empty or starts with slash or dot.
- Barcode Quiet Zone Explicit Margin
Quiet-zone slack in modules using an explicit supplied requirement, without selecting a barcode standard.