Open matentzn opened 7 months ago
Having it in the ODK would be great, but it can’t be the only distribution medium. People must be able to get that map without having to “exfiltrate” it out of the ODK image.
My thoughts for now (ideas only, nothing definitive or (too) opinionated):
sssom-py
repository, not in the ODK repository, etc. If needed, such a repository of “OBO-wide resources” should be created if none already exists (“OBO-commons” or something like that).http://purl.obolibrary.org/obo/obocommons/obo.epm.json
. Alternatively, somewhere on the OBOFoundry website, but that would seem strange to me (“why must I download all OBO products on purl.obolibrary.org
, but the EPM on obofoundry.org
?”)./resources/epms/obo.epm.json
).Yes, this makes sense. I will make an issue to see if OBO foundry would be open to host such a context.
From @gouttegd
https://github.com/obophenotype/uberon/pull/3141#issuecomment-1853891911
We should make a plan on how to best synchronise this extended prefix map (EPM) across resources. Right now we sync it in sssom-py. The reason for this is that I want to review every single change to the EPM myself, so I can go and intervene if I don't like something (say, the expansion of a new prefix being added).
The question is where this "protected" epm should live ideally. ODK is certainly an option!