Skip to content

Main content

Validation: Ror Base32 Identifier Alphabet Check Tool

Check the nine-character ROR local-id lexical form: leading zero, six restricted base32 characters and two decimal checksum digits; checksum and registry are not evaluated.

Loading tool…

Description

Check the nine-character ROR local-id lexical form: leading zero, six restricted base32 characters and two decimal checksum digits; checksum and registry are not evaluated.

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 the nine-character ROR local-id lexical form: leading zero, six restricted base32 characters and two decimal checksum digits; checksum and registry are not evaluated.

When to use this tool

Use Validation: Ror Base32 Identifier Alphabet 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

  1. Enter identifier. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Check identifier against the implemented nine-character ROR alphabet and digit-ending shape, returning lexicallyValid and checksumChecked false inside result.1

Input fieldMeaning and unitsAccepted input
identifierIdentifierRequired. Text.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
json
{
  "input": {
    "identifier": "03yrm5c26"
  },
  "output": {
    "result": {
      "lexicallyValid": true,
      "checksumChecked": false
    }
  }
}

Limitations and assumptions

  • An accepted spelling is not a checksum-valid or assigned ROR identifier. No registry lookup, organization matching, normalization, or URL parsing is performed.
  • 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

  1. Calculation and input contract: validate/ror-base32-identifier-alphabet-check — tool.io

Similar or alternative tools