Token Overlap Multiplicity Policy Tool

Description

Count token intersection and union by minimum and maximum multiplicities when multiset, or by distinct presence otherwise.

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.

Count token intersection and union by minimum and maximum multiplicities when multiset, or by distinct presence otherwise.

When to use this tool

Use Token Overlap Multiplicity Policy 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

Enter left, right, multiset. Keep parallel arrays aligned. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read intersection, union. Use the output convention below.

Count token intersection and union by minimum and maximum multiplicities when multiset, or by distinct presence otherwise.^[1]

Input field	Meaning and units	Accepted input
left	Left	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
right	Right	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
multiset	Multiset	Required. Boolean.

Output field	Interpretation	Returned shape
intersection	Intersection	Required. Safe integer.
union	Union	Required. Safe integer.

json

{
  "input": {
    "left": [
      "a",
      "a"
    ],
    "right": [
      "a"
    ],
    "multiset": true
  },
  "output": {
    "intersection": 1,
    "union": 2
  }
}

Limitations and assumptions

Tokens use exact string equality without normalization. Counts alone do not include a similarity ratio, tokenize source text, or decide whether duplicate occurrences should matter.
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

Calculation and input contract: similarity/token-overlap-multiplicity-policy — tool.io

Similar or alternative tools

Similarity: Overlap Coefficient Empty Min Policy
Compute overlap coefficient from consistent finite-set cardinalities with an explicit empty-minimum convention and retained defined status.
Weighted Overlap Missing Feature Policy
Return overlap=sum(weights[i]*min(left[i],right[i])) after replacing exact missing sentinel minus one by missingValue.