Ontology: how should conceptual differences between existing ontologies be represented?

Open
#483 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
data

Research direction

Start by reading the roadmap context, issue #22, and the referenced #108, then review how converters such as palantir_to_ossie and iri are currently described. The Ontology WG discussion should determine whether definitional differences need a new mechanism or belong elsewhere; done should be an agreed direction captured in the specification or a follow-up issue.

Written by the indexing model from the issue text.

Description

needs-triage
Background

The roadmap says Ossie already solves structural interoperability, but "does not yet solve conceptual interoperability, where different models may describe the same business concept using different names or structures." It lists cross-model conceptual alignment as a goal, and #22 names ontology-based systems such as Palantir and Goldman Sachs Legend as targets.

What we see today

If we understand correctly, two mechanisms are available today:

  • Converters (e.g. palantir_to_ossie), which translate an existing ontology into the Ossie format. If two ontologies are converted, the result is two separate Ossie ontologies.
  • iri, which lets two ontologies declare that a concept is the same as an externally defined one.

In practice, concepts from different systems are often related but not equivalent.
For example, "Customer" in one system may include anyone with an account, while "Customer" in another may include only contracted parties. Across organizations the differences are larger still: "water level" might mean height above each gauge station's zero point in one organization and height above the national datum in another.

With only iri, the options are to declare these concepts equivalent, which is wrong, or to leave them unlinked. The difference itself can only be carried in free-text description.

Questions
  1. Is there a planned mechanism to represent or absorb such definitional differences between ontologies?
  2. Is the Ontology WG the right place to discuss this, or is it covered elsewhere (e.g. #108)?
Dominant language
Python
Stars
2.7k
Forks
353
Avg merge
3d 19h
Merged PRs (30d)
86

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/ossie

All issues in apache/ossie

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.