[test] add shared-axioms module

[stap-m]

Summary of the discussion

See #1592.
I added a new module, which contains only intermodular axioms (currently only from information content artifact subclasses for testing).

Type of change (CHANGELOG.md)

Added

• Added a new class #

Updated

• Updated a definition #

Removed

• Removed a broken link #

Workflow checklist

Automation

Closes #

PR-Assignee

• 🐙 Follow the Pull Request Workflow
• 📝 Update the CHANGELOG.md
• 📙 Add #'s to term tracker item

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[stap-m]

I opend this PR to test, if the idea works. @l-emele @areleu couls you take a look please?
Any quick idea how to automate the term tracker item with robot?

[areleu]

I opend this PR to test, if the idea works. @l-emele @areleu couls you take a look please? Any quick idea how to automate the term tracker item with robot?

I think the robot annotate command should do the trick. What exactly do you want to annotate, do you want to add info about the axiom changes? this is changed in each of the classes involved isnt it? I can try to do a proposal tomorrow

[areleu]

This is trickier as I thought with ROBOT, what I can do is build a solution using https://github.com/jannahastings/py-horned-owl, the only problem is that is a hassle to use the tool in windows ( I already have it set up but, I am worried about reproducibility). One has to build the binaries from source etc. So it would be nice if @jannahastings adds the binaries for windows that are built with the pipeline I implemented last year, afaik these should be working up to python 3.10 in Linux, Windows and MacOS.

What do you think @stap-m? should I implement this solution or do something a little more hackier that does not use the mentioned library?

[stap-m]

Thanks for checking @areleu Let's discuss on monday which solution is worthwhile.

[jannahastings]

Yes I would like to help! Please give me a reminder what specifically I need to do -- should I do a new release of py-horned-owl ?

[areleu]

Yes I would like to help! Please give me a reminder what specifically I need to do -- should I do a new release of py-horned-owl ?

That would be great, I made a pull request ontology-tools/py-horned-owl#12 to update the horned-owl dependency because the old one was causing issues when building. The steps would be, once the PR is merged to first count up the release version, then wait for the binaries to be built and then upload them to pypi as part of the release. It would also be nice to have the release on GitHub.

The Binaries are found in Actions > All workflows (panel on the right) > Build(for windows/MacOS)/manylinux(for linux) > latest successful job > Artifacts > wheels

I know its a lot of clicking, theoretically we could set up a github job that pushes to pypi whenever the version number is raised.

[jannahastings]

Super. I'm on it... !

[jannahastings]

I tried to upload py-horned-owl v. 0.2.2. -- @areleu can you check if it works for you? Thanks!

[areleu]

I tried to upload py-horned-owl v. 0.2.2. -- @areleu can you check if it works for you? Thanks!

Working wonderfully, at least on windows systems.

[stap-m]

See #1649