Description
Split prefix on dots and return components plus valid when every component is a nonempty ASCII digit sequence.
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.
Split prefix on dots and return components plus valid when every component is a nonempty ASCII digit sequence.
When to use this tool
Use Handle Prefix Dot Component 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 prefix. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, components. Inspect valid before interpreting the associated values.
Split prefix on dots and return components plus valid when every component is a nonempty ASCII digit sequence.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| prefix | Prefix | 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. |
| components | Components | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
{
"input": {
"prefix": "20.500.123"
},
"output": {
"valid": true,
"components": [
"20",
"500",
"123"
]
}
}Limitations and assumptions
- Leading zeros are preserved, while empty components fail. This is a Handle-prefix spelling subset, not a prefix registration, authority, resolution, or complete identifier check.
- 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
- Validation: DOI Prefix Single Field Check
Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.
- DOI URL Prefix Versus Identifier Tag
Recognize an optional case-insensitive https://doi.org/ or https://dx.doi.org/ resolver prefix.