Integrate ENERO Foundry ontologies into Semantic-SQL
评估
调研方向
从 src/semsql/builder/registry/ontologies.yaml 开始，尤其检查现有的 oeo 条目，并审核候选 ENERO 本体的发布 URL、序列化、imports 和许可。使用 rdftab 和 relation-graph 从干净的 checkout 中验证选定条目，然后检查至少有一个除 oeo 之外的本体能够成功构建，并且新的 ID 已有文档记录。
由索引模型根据 Issue 内容生成。
描述
Summary
Add first-class support for ENERO Foundry ontologies in Semantic-SQL so they can be built and downloaded the same way we handle other non-OBO ontologies.
The ENERO Foundry is positioning itself as a coordination layer for interoperable energy-domain ontologies, with early ontologies including OEO, CEPO, MENO, MUNO, OTO, and CHIO. Semantic-SQL already has a partial oeo entry in src/semsql/builder/registry/ontologies.yaml, but the broader ENERO set is not yet modeled here in a consistent way.
Why
- Energy ontologies are increasingly relevant for FAIR research data workflows.
- ENERO is explicitly trying to make these ontologies interoperable, which aligns well with SemSQL's SQL view layer over OWL/RDF.
- The repo already supports a curated registry of non-OBO ontologies, so ENERO onboarding fits the existing architecture.
Proposed scope
- Audit candidate ENERO ontologies for stable release URLs, serialization, imports, and licensing.
- Decide which ontologies should be added to
src/semsql/builder/registry/ontologies.yaml. - Add registry entries,
prefixmaps, and any necessarybuild_commandoverrides. - Validate that each selected ontology can be turned into a working SemSQL SQLite build.
- Add focused tests or documented smoke-test commands for the new entries.
- Update user-facing docs so the new ontology IDs are discoverable.
Candidate ontologies
oeo(already present, likely needs validation/refresh)cepomenomunootochio
Open questions
- Which ENERO ontologies publish stable machine-readable release artifacts today?
- Do any require non-default preprocessing before
rdftab/relation-graph? - Should we stage this as
oeohardening first, then add the rest incrementally? - Are there any energy-adjacent artifacts we should explicitly exclude because they are not OWL reference ontologies in the SemSQL sense?
Acceptance criteria
- At least one additional ENERO ontology beyond
oeois integrated end-to-end in the registry. - The
oeoentry is verified or corrected against the current upstream release layout. - New entries are documented and reproducible from a clean checkout.
- 主要语言
- Python
- 星标
- 70
- 派生
- 7
- 平均合并
- 4 小时 18 分钟
- 30 天内合并 PR
- 1
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
INCATools/semantic-sql 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 52/100
INCATools/semantic-sql#124 ·
-
Migrate direct raw-S3 bbop-sqlite consumers to the semanticsql CDN可能重新可做 @caufieldjh 于 92 天前认领，目前没有进行中的 PR。 未关闭help wanted
INCATools/semantic-sql#115 · 7 条评论 · 已指派 1 人 ·
-
[bot] Cut a semsql release including the semanticsql.berkeleybop.io default可能重新可做 @caufieldjh 于 92 天前认领，目前没有进行中的 PR。 未关闭enhancement
INCATools/semantic-sql#114 · 2 条评论 · 1 个 reaction · 已指派 1 人 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
INCATools/semantic-sql#111 · 1 条评论 ·
-
documentation
难度 3/5 1-2 天 新手友好度 45/100
INCATools/semantic-sql#106 · 3 条评论 ·
查看 INCATools/semantic-sql 的全部 Issue
相似的 Issue
-
documentation pkg: sphinx-needs
难度 1/5 1 小时以内 新手友好度 82/100
useblocks/sphinx-needs#2255 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
home-assistant/core#186538 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
btclib-org/btclib-secp256k1#1181 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
pyrite-wiki/pyrite#917 ·
维护者通常 1 天内回复