Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Circular references in chameo imports/ update of imports #17

Open
SArndt-TIB opened this issue Sep 25, 2024 · 0 comments
Open

Circular references in chameo imports/ update of imports #17

SArndt-TIB opened this issue Sep 25, 2024 · 0 comments

Comments

@SArndt-TIB
Copy link

Hi everyone,

we are running a terminology service where we would like to ingest the BattInfo ontology which is associated and using the different EMMO ontologies - CHAMEO being one of them.

We have trouble doing so with our OLS4-based system. The ingest of battinfo from https://raw.githubusercontent.com/BIG-MAP/BattINFO/master/battinfo.ttl is stopping because of the imports. As I was told from our devs, there is a loop. I tried to localize it and I hope I got it right.

BattInfo imports https://w3id.org/emmo/domain/battery/0.13.0-beta/battery which imports https://w3id.org/emmo/domain/electrochemistry/0.22.0-beta/electrochemistry (both latest releases/ tags) which imports https://w3id.org/emmo/domain/characterisation-methodology/chameo which resolves to https://raw.githubusercontent.com/emmo-repo/domain-characterisation-methodology/master/chameo.ttl.

And in there I find imports

These two are both not the latest releases and also contain a circular reference, importing each other over and over again. In the latest releases this seems to be fixed: https://github.com/emmo-repo/EMMO/blob/v1.0.0-rc1/disciplines/computerscience.ttl is imported by https://github.com/emmo-repo/EMMO/blob/v1.0.0-rc1/disciplines/models.ttl but not vice versa.

My question to you would now be, whether it would be possible for you to update the references in your imports, so that we can test (upstream) whether this changes our problems with BattInfo?

I also saw that BattInfo is referring to your master branch, even though several beta branches are available (the latest of which seems to import even older versions of models.ttl and computerscience.ttl). In other EMMO-associated repos I saw that they are working with releases which is not the case here - have you thought about that? Or is it still too early? For an outsider, this really would improve the transparency - especially in a more complex ontology setup as I find here with 6 or more levels of direct and indirect imports.

Thanks for considering and all the best

Susanne

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant