Ontology: how should conceptual differences between existing ontologies be represented?
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 领域
- data
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Is there a planned mechanism to represent or absorb such definitional differences between ontologies?
- Is the Ontology WG the right place to discuss this, or is it covered elsewhere (e.g. #108)?
- 主要语言
- Python
- 星标
- 2.7k
- 派生
- 353
- 平均合并
- 3 天 19 小时
- 30 天内合并 PR
- 86
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
apache/ossie 的其他 Issue
-
needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 52/100
维护者通常 1 天内回复
-
validation: field reference resolution is case-insensitive but name uniqueness is case-sensitive可能已有人在做 @MikeNitsenko 于 6 天前认领。 未关闭needs-triage
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
needs-triage
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
needs-triage
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
mohanraj00/entelos#200 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
-
sweep
难度 2/5 1-3 小时 新手友好度 85/100
bketelsen/truenas-mcp#77 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
sandbox-quantum/switch#2163 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
openedx/xblock-lti-consumer#765 ·
维护者通常 1 天内回复