Right now cdao:AlignmentProcedure, cdao:TreeProcedure, miapa:'Manual procedure', miapa:'Software procedure', and edam:Operation are all siblings and asserted subclasses of prov:Activity. This could be reduced by one by making cdao:AlignmentProcedure, cdao:TreeProcedure, miapa:'Manual procedure', and miapa:'Software procedure' children of edam:Operation.
Note that instances for annotation would still have to be asserted to two classes in order to both assert what kind of procedure, and whether a manual or software procedure.
Right now cdao:AlignmentProcedure, cdao:TreeProcedure, miapa:'Manual procedure', miapa:'Software procedure', and edam:Operation are all siblings and asserted subclasses of prov:Activity. This could be reduced by one by making cdao:AlignmentProcedure, cdao:TreeProcedure, miapa:'Manual procedure', and miapa:'Software procedure' children of edam:Operation.
Note that instances for annotation would still have to be asserted to two classes in order to both assert what kind of procedure, and whether a manual or software procedure.