Description
Parse one human-readable GS1 application-identifier parenthesis token of two through four digits; does not validate AI allocation, payload or barcode encoding.
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.
Parse one human-readable GS1 application-identifier parenthesis token of two through four digits; does not validate AI allocation, payload or barcode encoding.
When to use this tool
Use Validation: Gs1 AI Single Parenthesis Token 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 result. Expand result to inspect the returned fields.
Require a parenthesized token containing two through four ASCII digits. Return its applicationIdentifier without parentheses and semanticRegistryChecked false inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"token": "(01)"
},
"output": {
"result": {
"applicationIdentifier": "01",
"semanticRegistryChecked": false
}
}
}Limitations and assumptions
- This is human-readable token shape only. It does not verify that the identifier is assigned, validate associated data, or serialize parentheses into a barcode element string.
- Outputs are nested inside result. 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
- GS1 AI Date Day Zero Policy
Validate a supplied-century YYMMDD token and optionally interpret day 00 as the final day of its month.
- GS1 AI Fixed Field Leading Zero Preserver
Preserve a supplied field verbatim while checking numeric fixed width and counting its leading zeros.