17 situation as supercategory for state and process

[AlexU75]

No description provided.

[KonradHoeffner]

The automatic check fails because the imported GFO core ontology https://onto-med.github.io/gfo-light/gfo-core/2025-10-01/gfo-core.owl cannot be found, is this related to the PR or should I open a separate issue? I'm not sure how that file is supposed to be published there after looking at the GitHub action for the release.

[KonradHoeffner]

I could successfully load it in Protégé after resolving the missing import and it looks good to me but I'm not a GFO expert.
Can you clarify how to input is supposed to work?
https://w3id.org/gfo-core/release/2025-10-01 resolves to https://onto-med.github.io/gfo-light/gfo-core/2025-10-01/gfo-core.owl which does not exist, will that be automatically created once this PR is merged?

[ChristophB]

The automatic check fails because the imported GFO core ontology https://onto-med.github.io/gfo-light/gfo-core/2025-10-01/gfo-core.owl cannot be found, is this related to the PR or should I open a separate issue? I'm not sure how that file is supposed to be published there after looking at the GitHub action for the release.

The file is published to that location once a release has been created. However, the test tries to load the imported ontology remotely, before a release.

robot report is used in the test and there is no way to specify import locations other than by providing a catalog-v001.xml file. This means that the XML file must be updated whenever gfo-core is modified in a pull request. Unfortunately, I am not aware of an elegant way to overcome this issue.

[KonradHoeffner]

From the point of view of a domain expert that wants to update their domain ontology fundation, I think it would be really helpful to give a short migration guide so that one can see at a glance, whether one has to update anything or not.
To that end I added a revision history section to the README, feel free to check this for correctness and completeness and maybe add a sentence on whether and if yes what a user has to change.

[KonradHoeffner]

I really like the changelog as a a separate file. Now it doesn't clutter the README and gives actionable migration advice.

[KonradHoeffner]

I don't have Arial on my system but it still looks correct on both Firefox Developer Edition 146.0b9 (64-bit), Eye of Gnome and Inkscape, so it seems to have some adequate fallback mechanism even though I can't figure out which font it is actually using.

[KonradHoeffner]

Firefox falls back to NimbusSans-Regular, fc-match Arial returns LiberationSans-Regular.ttf: "Liberation Sans" "Regular".
So it seems at least on my system the lack of Arial is not a problem as both those fonts are sans serif, look similar and seem to have similar spacing.