Scior allows the user to have as result classes partially classified (i.e., classes that are known to be or not to be of certain types, but that do not specialize the leaf possibilities - e.g., Scior may classify a class only as RigidType and not as Kind, Subkind, or Category).
Desired situation:
The authors of gUFO designed its types' hierarchy for having its leaf classes specialized. I.e., their superclasses are supposed to be "abstract".
How to achieve it:
By the end of the execution, Scior could present the partially known classes to the user, displaying its possible classifications, and ask the user to insert the information.
Scior also could enter this last stage when receiving a specific argument (e.g., "-f").
Current situation:
Scior allows the user to have as result classes partially classified (i.e., classes that are known to be or not to be of certain types, but that do not specialize the leaf possibilities - e.g., Scior may classify a class only as RigidType and not as Kind, Subkind, or Category).
Desired situation:
The authors of gUFO designed its types' hierarchy for having its leaf classes specialized. I.e., their superclasses are supposed to be "abstract".
How to achieve it:
By the end of the execution, Scior could present the partially known classes to the user, displaying its possible classifications, and ask the user to insert the information.
Scior also could enter this last stage when receiving a specific argument (e.g., "-f").