Skip to content

Main content

Historical Unit Symbol Token Tool

Inspect a symbol within caller-supplied historical-unit vocabulary without inventing conversion factors.

Loading tool…

Description

Return literal membership and its zero-based index, or index -1 when absent.

Source-scoped cultural and historical records preserve an edition, naming convention, or local identifier. Literal agreement is useful bookkeeping but does not establish interpretation, authenticity, or authority.

Return literal membership and its zero-based index, or index -1 when absent.

When to use this tool

Use Historical Unit Symbol Token when you need a precise source-token or range consistency check.

How to use the tool and how it works

  1. Enter symbol, suppliedSymbols, suppliedNamespace. 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 namespace, recognized, index. Inspect recognized before interpreting the associated values.

Require nonempty suppliedNamespace and distinct suppliedSymbols. Return literal membership and its zero-based index, or index -1 when absent.1

Input fieldMeaning and unitsAccepted input
symbolSymbolRequired. Text; maximum UTF-16 length 8192.
suppliedSymbolsSupplied SymbolsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
suppliedNamespaceSupplied NamespaceRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
namespaceNamespaceRequired. Text; maximum UTF-16 length 8192.
recognizedWhether the token matches the supplied vocabulary or supported mapping.Required. Boolean.
indexZero-based position under the stated lookup convention, including any -1 sentinel.Required. Safe integer.
json
{
  "input": {
    "symbol": "ell",
    "suppliedSymbols": [
      "ell",
      "yard"
    ],
    "suppliedNamespace": "archive-A"
  },
  "output": {
    "namespace": "archive-A",
    "recognized": true,
    "index": 0
  }
}

Limitations and assumptions

  • Symbols and namespace are supplied rather than an authoritative historical-unit registry; recognition does not establish a conversion factor or quantity meaning.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Consult the source edition and relevant community or scholarly guidance before interpreting or reusing the material.

References

  1. Calculation and input contract: history/historical-unit-symbol-token — tool.io

Similar or alternative tools