Proximity Measure of Information Object Features for Solving the Problem of Their Identification in Information Systems

This paper proposes a novel quantitative-qualitative proximity measure that utilizes probabilistic and possibility-based approaches to identify information objects from multiple independent sources without requiring feature value transformation, while accounting for determination errors and satisfying necessary axiomatic requirements.

Volodymyr Yuzefovych

Published 2026-04-08
📖 4 min read☕ Coffee break read

Imagine you are the manager of a massive, chaotic detective agency. Your job is to track down "suspects" (physical objects like cars, people, or ships) based on reports coming in from different sources.

Here is the problem: You have two detectives, Detective Bob and Detective Alice. They are both looking at the same suspect, a red car.

  • Bob is using a high-tech laser scanner. He reports: "The car is at mile marker 100.2."
  • Alice is using a cheap, old map. She reports: "The car is at mile marker 100.5."

In your current system, the computer thinks these are two different cars because the numbers don't match perfectly. So, you end up with two files for one car. This clutters your database, wastes memory, and confuses your team.

This paper proposes a new, smarter way to decide if two reports are actually about the same object, even when the data isn't perfect.

The Old Way: The "Rigid Ruler"

Previously, systems used a "Rigid Ruler" approach.

  • If the numbers were exactly the same, it was a match.
  • If they were even slightly different, it was a mismatch.
  • The Flaw: This ignores reality. No measurement is perfect. A ruler might be slightly bent, or a human might misread a scale. The old system couldn't handle "close enough."

The New Way: The "Fuzzy Detective"

The author, V.V. Yuzefovych, suggests we stop looking for exact matches and start looking for probability. Think of it like this:

1. The Quantitative Clues (The Numbers)

Imagine you are trying to guess the temperature.

  • Detective Bob says: "It's 20°C." He is very confident (his thermometer is precise).
  • Detective Alice says: "It's 22°C." She is less confident (her thermometer is shaky).

Instead of saying "20 is not 22," the new method asks: "What is the chance that the real temperature is somewhere in the middle?"

  • It draws a "cloud of uncertainty" around Bob's number (a small, tight cloud because he's precise).
  • It draws a "foggy cloud" around Alice's number (a big, wide cloud because she's shaky).
  • If these clouds overlap, the system says, "Hey, there's a good chance they are talking about the same temperature!"
  • The Magic: The system calculates the probability that the overlap is real. The more the clouds overlap, the higher the chance it's the same object.

2. The Qualitative Clues (The Descriptions)

Now, imagine the clues aren't numbers, but descriptions.

  • Bob says: "The car is Red."
  • Alice says: "The car is Dark Red."

Old systems would say, "Red is not Dark Red. Mismatch!"
The new system uses Fuzzy Logic (think of it as a dimmer switch rather than an on/off light).

  • It treats "Red" and "Dark Red" not as separate boxes, but as shades on a spectrum.
  • It asks: "How much does 'Dark Red' look like 'Red'?"
  • If Alice is unsure about her description (she says, "I think it's Red, but I'm not 100% sure"), the system accounts for that doubt. It widens the "fog" around her description, making it easier to match with Bob's.

The Final Verdict: The "All-or-Nothing" Rule

Once the system checks every clue (location, color, speed, type), it needs to make a final decision.

The paper suggests using a Multiplicative Rule (like a chain).

  • Imagine a chain where every link represents a clue.
  • If one link is broken (e.g., the car is definitely Red in one report and definitely Blue in another), the whole chain breaks.
  • Even if the location and speed match perfectly, if the color is totally wrong, the system concludes: "These are two different cars."

This prevents the system from accidentally merging two totally different objects just because they happened to be in the same neighborhood.

Why This Matters

This new method is like upgrading your detective agency from a rigid robot to a wise human investigator.

  1. No More Clutter: It stops the system from creating duplicate files for the same object.
  2. Handles Mistakes: It understands that humans and machines make errors, and it doesn't panic when data isn't perfect.
  3. Better Decisions: By knowing which objects are truly the same, the system can give you a clearer picture of the world, leading to better decisions.

In short: The paper teaches computers how to say, "These two reports aren't exactly the same, but given the mistakes we know happen, they are almost certainly talking about the same thing."

Get papers like this in your inbox

Personalized daily or weekly digests matching your interests. Gists or technical summaries, in your language.

Try Digest →