Nico Matentzoglu

I answered in detail on your [ROBOt](https://github.com/ontodev/robot/issues/1001) issue.

There is no urgent need to parse OBO files as all OBO (Foundry, at least) ontologies are required to provide a primary RDF/XML release!

It is incomplete, but for most purposes (that's what we use for the [OBO Dashboard](http://dashboard.obofoundry.org/dashboard/index.html) ELK is sufficient. ELK 0.5 if you managed to get it to work even more...

I was just informed about this issue - it seems very relevant to all of us, maybe move ticket here https://github.com/information-artifact-ontology/ontology-metadata/issues?

Lets first sort out on OBO Foundry level if we go with adoption or not.. There is a bit of a burden on James and the OBO PURL system if...

@zhengj2007 correct me if I am wrong, but should this request not be added here: https://github.com/information-artifact-ontology/ontology-metadata/issues/new

https://github.com/blazegraph/database/wiki/Reification_Done_Right

To be clear, `Orphanet:377788` is already excluded from the rare disease subset - this issue is about explicitly excluding it from the rare subset pipeline. Thanks @joeflack4, will take care...

This commit fixes it, and the PR around it will eventually close this issue, when it is merged: https://github.com/monarch-initiative/mondo/commit/4e98177428ee9ea5f4b4f5945c643e951a34edbc

The change [is in](https://github.com/mapping-commons/sssom-py/blob/91d08b8c096fe987b8bee7155b0731a53009331f/src/sssom/obo.epm.json#L3473) but it needs an ODK update which we are working on right now.