Adding or Deleting Asserted Subclasses: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
   See [[Ontology_Editors_Daily_Workflow]] for creating branches and basic Protégé instructions.
   See [[Ontology_Editors_Daily_Workflow]] for creating branches and basic Protégé instructions.


* Asserted '''is_a parents''' do not need to be retained as entries in the '''SubClass of''' section of the Description window in Protege if the logical definition for a term results in their inference.
* Asserted '''is_a parents''' do not need to be retained as entries in the '''SubClass of''' section of the Description window in Protege if the logical definition for a term results in their inference.

Revision as of 20:06, 7 June 2018

 See Ontology_Editors_Daily_Workflow for creating branches and basic Protégé instructions.
  • Asserted is_a parents do not need to be retained as entries in the SubClass of section of the Description window in Protege if the logical definition for a term results in their inference.
  • If you have created a logical definition for your term, you can delete the asserted is_a parent by clicking on the X to the right term.
  • Once you synchronize the Reasoner, you will see the reasoned classification of your new term, including the inferred is_a parent(s).
  • If the inferred classification does not contain the correct parentage, or doesn’t make sense, then you will need to modify the logical definition.
  • If an existing term contains a logical definition and still shows an asserted is_a parent in the ‘SubClass of’ section, you may delete that asserted parent, as well.
  • Make sure to run the Reasoner to check that the asserted parent is now replaced with the correct reasoned parent(s).
 See Ontology_Editors_Daily_Workflow for commit, push and merge instructions.

Review Status

Last reviewed: June 7, 2018 Back to: Ontology Editing Guide