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

Aperta
#483 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
data

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)?
Lingua principale
Python
Stelle
2.7k
Fork
353
Merge medio
3g 19h
PR unite (30g)
86

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/ossie

Tutte le issue di apache/ossie

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.