OM
OM copied to clipboard
HajoRijgersberg
Setup Basic Release Pipeline
It would be beneficial for the development process to make a separation between the place of the ontology under development and the released ontology. The current situation has some disadvantages:
- regular manual commits to update version number and date
- versions with unreleased changes contain the last version number in the metadata
This could be improved by
- removing the version number and date in the ontology under development and
- by adding a release pipeline (Github action), e.g. based on ROBOT, to generate a version with version number, if a commit is tagged with
v*.*.*(e.g.v2.0.47).
Based on the tag and the generated ontology version (pipeline artifact), a release can be generated.
This pipeline could later get extended to add e.g. automated generation scripts, quality checks or deployment scripts.
Also, alternative release versions would be possible:
- different serialization formats
- different OWL profiles
- alternative xsd:float backward compatibility version
Sorry for my late reply Jan Martin, but this sounds good. Thanx so much for your initiative!
Just came across this issue and the discussion in PR #92
Will this PR also solve that the website serving http://www.ontology-of-units-of-measure.org/resource/om-2/ will be updated based on the current version of the om-2.0.rdf from this repo?
I e.g. saw that in this repo there is the unit wattHour, but this is missing at http://www.ontology-of-units-of-measure.org/resource/om-2/wattHour
Or did I understand that wrongly?
Hi, Thanx for your attention. No, that will not be updated automatically. That would be great idea, but apart from that it would be good if I could update the ontology on that website at all. Because of limited time I can not dive into that right now, but I am planning to do that soon. Best, Hajo