search

OBOFoundry / Operations-Committee-RETIRED

Automatically exported from code.google.com/p/obo-foundry-operations-committee
1 stars 0 forks source link

Ambiguity of versioned PURL for main artifact #197

Closed alanruttenberg closed 6 years ago

alanruttenberg commented 7 years ago

Situation: Your repository has foo.owl which imports other files. During release you generate a merged foo.owl served at

http://purl.obolibrary.org/obo/foo.owl and http://purl.obolibrary.org/obo/foo/<date>/foo.owl

You want to import the unmerged version? What's it's PURL?

Proposal: have the convention either be to have the versioned IRI for the merged file be

http://purl.obolibrary.org/obo/foo/<date>/foo-merged.owl

or for the stated/unmerged/unreasoned

http://purl.obolibrary.org/obo/foo/<date>/foo-stated.owl

Implicit here is that release of a merged/reasoned version of the ontology should not preclude also publishing the original source - there are legitimate reasons one might want that.

jamesaoverton commented 6 years ago

We've been discussing this again recently. I'm closing this issue in favour of https://github.com/OBOFoundry/OBOFoundry.github.io/issues/560