Skip to content

Main content

Token Match Case Fold Policy Pair Tool

Compare two tokens with an explicit ASCII-only case-folding policy.

Loading tool…

Description

Compare two tokens with an explicit ASCII-only case-folding policy.

A similarity term depends on the comparison universe, missing-value policy, treatment of repeated features, and normalization. A score can also have a caller-selected value when its mathematical denominator vanishes. Those conventions matter before interpreting a threshold or comparing methods.

Compare two tokens with an explicit ASCII-only case-folding policy.

When to use this tool

Use Token Match Case Fold Policy Pair when you need this particular comparison term, normalization, domain condition, or empty-result policy in a larger matching workflow.

How to use the tool and how it works

  1. Enter left, right, ignoreAsciiCase. 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 match. Inspect match before interpreting the associated values.

Compare ASCII-only left and right exactly or after lowercasing when ignoreAsciiCase. Return match.1

Input fieldMeaning and unitsAccepted input
leftLeftRequired. Text; maximum UTF-16 length 8192.
rightRightRequired. Text; maximum UTF-16 length 8192.
ignoreAsciiCaseIgnore Ascii CaseRequired. Boolean.
Output fieldInterpretationReturned shape
matchMatchRequired. Boolean.
json
{
  "input": {
    "left": "Alpha",
    "right": "alpha",
    "ignoreAsciiCase": true
  },
  "output": {
    "match": true
  }
}

Limitations and assumptions

  • ASCII controls are permitted by the input subset. The comparison is not Unicode case folding, text normalization, tokenization, or a complete identifier or security 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.

Alternative or Complementary methods

Compare methods only after aligning feature definitions, missingness, empty policies, multiplicities, and normalizers. Use a complete comparison when the tool returns only one contribution or count check.

References

  1. Calculation and input contract: similarity/token-match-case-fold-policy-pair — tool.io

Similar or alternative tools

  • Similarity: Cosine Zero Norm Policy

    Compute cosine similarity with an explicit reject/zero undefined-norm policy and a retained defined flag; zero is not silently treated as a measured cosine.

  • Dice Weighted Match One Term

    Return contribution=2*matchWeight/(firstTotal+secondTotal), requiring nonnegative totals, match weight within both, and positive combined total.