OGMS missing "versionIRI"

[sivaramarabandi]

As OGMS is being updated and released, we need to be able to use/refer to each version specifically. OWL has versionIRI tag just for this purpose.

[BAevermann]

Thanks! I will look into using the versionIRI in the current release and for future releases.

[BAevermann]

Tracking releases via github release functionality. Hopefully that will suffice.

[sivaramarabandi]

Afraid that totally misses the point 😕

On Mon, Mar 4, 2019 at 2:50 PM Brian Aevermann ***@***.***> wrote: Closed #119 <#119>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#119 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHg_F7hOyLuJJ6gHS5Uj9nZUHVWD2CZQks5vTYcCgaJpZM4VNqrU> .

--

…

______________________ Sivaram Arabandi, MD, MS ONTOPRO W: http://ontopro.com/ Ph: 832.726.2322 Think Semantics. Tame Silos.

[cmungall]

Agree with @sivaramarabandi versionIRI should be present in release, see ODK for examples

[BAevermann]

I can add the URL to the v2018 as the IRI in the OWL file. Would that work?
it would look like:

https://github.com/OGMS/ogms/releases/tag/v2018

[zhengj2007]

@BAevermann If you use ROBOT tool to make the release file, the versionIRI will be added. It will be something like: http://purl.obolibrary.org/obo/ogms/2018-09-20/ogms.owl, which is following OBO Foundry guideline.