Allyson, thank you!
We've been using SWO with great success now
for a month. I have one major issue / question:
SWO defines the class "software" (
http://www.ebi.ac.uk/swo/SWO_0000001) as a subclass of IAO:information content entity (
http://purl.obolibrary.org/obo/IAO_0000030)
URI =
http://www.ebi.ac.uk/swo/SWO_0000001def = Computer software, or generally just software, is any set of machine-readable instructions (most often in the form of a computer program) that conform to a given syntax (sometimes referred to as a language) that is interpretable by a given processor and that directs a computer's processor to perform specific operations.
This class seems redundant with IAO:Software (
http://purl.obolibrary.org/obo/IAO_0000010)
class hierarchy = information content entity / directive information entity / plan specification / Software
URI =
http://purl.obolibrary.org/obo/IAO_0000010def = Software is a plan specification composed of a series of instructions that can be interpreted by or directly executed by a processing unit.
Should SWO:Software be deleted and it's subclasses moved under IAO:Software to maximize ontology reuse, maintain clean separation between upper / middle / domain ontologies, and to minimize confusion and redundancy?
Note, this is not just a theoretical problem. It is causing some unintended negative consequences in our data processing pipeline.
Thanks!
-joe