Jim Balhoff

I think the problem with the three triples that could not be parsed is that the ontology should not be using `owl:equivalentProperty` with annotation properties. These look like they're typed...

> @balhoff's theory is that `rdfs:label` (an annotation property, although it is very often used as a data property in instance data) is treated as an object property. AFAIK annotation...

Seems like this happened before (#196). But I have been loading this into Ubergraph for a long while, and it just disappeared in the last few weeks.

Thanks @jamesaoverton, that makes sense. Ubergraph is loading cob-base also, but I don't think it contains enough axioms, so I will load cob.owl. Unfortunately cob.owl will duplicate labels and definitions...

Okay! No rush. I am loading cob.owl for now. I think these axioms should just be included in cob-base.

I think if an axiom is provided by COB, and the axiom is not provided by some other ontology, then it should be in the base file. So if `PATO:1...

> where owl:Restriction are no longer “inlined” where they are needed, but instead declared separately as blank nodes and referenced where they are needed. > Not sure why this is...

> The following difference (in the same subsets/life-stages-core.obo file), however, is wrong This seems to be a problem in OWL API. ☹️ I find this with ROBOT as well. Input:...

That's good! I don't think the serializer should be making up prefixes for non-OBO namespaces, but it's good it can be worked around. So I'm guessing owltools needs to do...

It comes from MONDO: https://api.triplydb.com/s/ehseoJ7O0 Do you know anybody who works on that ontology? 😜