Description
Set separatorRequired when fixedLength is false and finalField is false.
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.
Set separatorRequired when fixedLength is false and finalField is false.
When to use this tool
Use GS1 AI Variable Length Separator Flag 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 fixedLength, finalField. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read separatorRequired, separator. Inspect separatorRequired before interpreting the associated values.
Set separatorRequired when fixedLength is false and finalField is false. Return the ASCII group-separator character U+001D in that case, otherwise an empty separator.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| fixedLength | Fixed Length | Required. Boolean. |
| finalField | Final Field | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| separatorRequired | Separator Required | Required. Boolean. |
| separator | U+001D when required; empty otherwise. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"fixedLength": false,
"finalField": false
},
"output": {
"separatorRequired": true,
"separator": "\u001d"
}
}Limitations and assumptions
- The length and field-position flags are supplied. The tool does not consult an application-identifier registry, parse barcode data, or establish that the returned transport character is the correct encoding for a particular carrier.
- 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 Fixed Length Padding Check
Check a digit field's supplied fixed length and report any missing character count without padding it.
- GS1 AI Date Day Zero Policy
Validate a supplied-century YYMMDD token and optionally interpret day 00 as the final day of its month.