When a repository is initialized (or updated with update_repo), the seeding process automatically creates a src/ontology/imports/{imp.id}_import.owl file (containing a boilerplate RDF/XML header) for each id import declared in the ODK configuration file.
Problem is that it does that even when use_base_merging is True, even though in that case those individual import modules are actually never needed (what’s needed instead is a single src/ontology/imports/merged-import.owl module).
The _dynamic_files.jinja2 template should be updated to take into account the use_base_merging parameter when creating the placeholder import modules, so that it creates only the merged-import.owl module when use_base_merging is True.
When a repository is initialized (or updated with
update_repo), the seeding process automatically creates asrc/ontology/imports/{imp.id}_import.owlfile (containing a boilerplate RDF/XML header) for each id import declared in the ODK configuration file.Problem is that it does that even when
use_base_mergingis True, even though in that case those individual import modules are actually never needed (what’s needed instead is a singlesrc/ontology/imports/merged-import.owlmodule).The
_dynamic_files.jinja2template should be updated to take into account theuse_base_mergingparameter when creating the placeholder import modules, so that it creates only themerged-import.owlmodule whenuse_base_mergingis True.