Re: [Obo-format] Issue 21 in oboformat: Generate deprecate OWL class when converting merged terms

[<obo...@go...>]

Comment #7 on issue 21 by mcour...@gmail.com: Generate deprecate OWL class  
when converting merged terms
http://code.google.com/p/oboformat/issues/detail?id=21


I was suggesting to not delete the term in the OWL conversion, which is  
what happens when you replace a class definition by an alt_id annotation  
property.

To address David's point, we could imagine keeping the alt_id property, and  
ask the script to do both: when merging PATO_0001237 with PATO_0001241, we  
would deprecate the former (adding an obsolescence reason "term merged" and  
a term replaced by annotation property pointing to PATO_0001241) and add  
its ID as an alt_id on the latter.
Is there a drawback doing so?

Finally, if we can reach agreement, I would suggest to formally specify  
that behavior, so that tool developers (whether MIREOT or else) can build  
scripts based on a known specification.