Open joeflack4 opened 2 years ago
In this case, shouldnt your code be robust enough to understand that a resulting value is a curie or not (there are methods in the various curie packages for that), and if it is not, use the mondo prefix map to handle? We can never be sure that all files we use have the correct RDF prefixes in them..
Yes, it is easy to handle, and will be handled in this case.
I haven't checked all of the other .owl
files in his way; maybe it's not just OMIM.
I suppose that I would have been using prefix_map
anyway for this filtering, but I haven't gotten that far in my code yet. Mostly spent time yesterday on OAK issues.
So I wouldn't say that this issue is a hold up for any of my work. I am just imagining that something is probably wrong here. The generation of the .owl
files seems lossy in this way in that it is not retaining prefixes. Probably would be useful if we can fix that.
Its a big disconnect between the RDF world and the rest of the world - in RDF prefixes mean nothing, they are pure syntactic sugar:
...
@prefix CHR: <http://purl.obolibrary.org/obo/CHR_> .
CHR:123 rdfs:label "label"
is identical (equal) to:
@prefix ZORRO: <http://purl.obolibrary.org/obo/CHR_> .
ZORRO:123 rdfs:label "label"
and the same with:
<http://purl.obolibrary.org/obo/CHR_123> rdfs:label "label"
(I repeat, no difference between all three all the same).
Only in database - bioinformatics-land is their any difference between these three, because they perceive a CURIE as an identifier.
Ah, yes. This jives with my understanding.
Still probably want to retain this information though, I would imagine.
Overview
I was working in Python and looking at the entities that OAK queried for me. It returns a list of terms as CURIEs if the prefixes are available in the file, and otherwise shows the whole URI. When I split on
:
and got a unique set, this is all that came back:{'RO', 'CHR', 'https', 'SO'}
Details
components/omim.owl
prefixes I noticed thatOMIM
andOMIMPS
don't appear:omim.ttl
from OMIM ingest They do appear here:Possible causes
I think that we haven't set up the OMIM ingest to update the PURL from the latest release.
How do we do that? I know now that our PURL for Mondo gets updated when a latest release gets published there. Is this a manual or automated process?
Related
Also outdated: #58