Open GoogleCodeExporter opened 9 years ago
Note that relabeled obsolete classes is purely a convention to make up for
limitations in Protege (it gets confused if there are multiple classes with the
same label). The GO has many obsolete classes that share the label of a
non-obsolete class (but it is never the case that two non-obsolete classes will
share a label). Oort enforces this.
Having said that, we are now using Protege as the primary editing environment
for CL so we should probably do a mass relabeling of obsolete terms (sigh).
Original comment by cmung...@gmail.com
on 30 Jul 2013 at 8:21
Chris- is this something I could help do manually?
Original comment by vasil...@ohsu.edu
on 2 Dec 2014 at 7:15
Can you prefix label for the obsolete IRI above with "obsolete "
Original comment by cmung...@gmail.com
on 2 Dec 2014 at 7:43
Original issue reported on code.google.com by
zhengj2...@gmail.com
on 12 Jul 2013 at 5:20