Nico Matentzoglu

Implementing this is seriously too complicated. I think we should do something else: implement `ROBOT normalise` (https://github.com/ontodev/robot/issues/901), this way axioms like the ones causing this issue here would be merged...

We have had this for quite a long time: https://github.com/INCATools/ontology-development-kit/blob/master/CITATION.cff Please reopen in case you meant something else.

Or do you mean to the repo template? Reopeining

As this will probably take a couple of years @sierra-moxon: would you be interested in simpy developing a quick pipeline that pulls the OWL of all those ontologies and transform...

@cmungall yeah the guestimate was more for migrating all pipelines to a proper ODK like setup; having a JSON export is not as bad.. Unless there is no pipeline at...

@jamesaoverton and I discussed this and we will move this to a future version of ROBOT, maybe ROBOT 2.0 :P

Ok, indeed, this issue is solved when using the canonical Python name. FWIW, I would prefer we restrict the permissible lexical representation of the class name in linkml to whatever...

Wow this is also a good idea.. In fact, this could be both easier to use, and would save a lot of QC annotations in the ontology.. I like it!...

Ultimately, lazyness wont help them because what will count on OBO level is what OBO Dashboard deems as exclusion criteria - so if they exclude on ontology level, this wont...

The reason for this policy is that many of our users are using Protege and we need to avoid spurious diffs on GitHub... What would be the reason to update...