4.3 Software Capabilities
59
Fig. 4.1 Fragment of VISO showing its upper and intermediate classes and their connection to
EVMPO and external assets; the diagram was generated using the OWLViz protégé plugin; grey
arrows labelled “is-a” denote subsumption (), i.e. rdfs:subClassOf
especially focus on its AM branch, which deals with molecular models and particlebased methods; for more details on the other branches, we refer the reader to [31]
and to a recent VIMMP ontology release [32, 33].
Accordingly, selected major concepts from viso-general are:
• viso:software: a computer program. Its direct (mutually disjoint) subclasses are:
viso:software_tool, viso:compiler, viso:operating_system.
• viso:programming_language: a language that can be used to write software.
• viso:software_tool_feature ≡ (viso:model_feature viso:solver_feature): a
capability of a software tool, intended as either a model aspect that can be
addressed (viso:model_feature) or as a numerical algorithm which is implemented
(viso:solver_feature). Following the approach from RoMM [30], these two classes
are disjoint.
• viso:model_type: a classification of the model, intended as in RoMM [30].
• viso:model_object: the type of object entering the model and carrying degrees of
freedom. Its subclasses in the AM branch (cf. Fig. 4.2) include viso-am:interaction_
site, viso-am:interaction_surface, viso-am:connected_object.
• viso:software_update: it describes (as text) the changes between versions of a
software. In particular, its subclass viso:software_tool_update allows to describe
the addition/removal of features from a tool.
• viso:software_interface: an interface between a software and a user or a client
(i.e. a program or device). Some subclasses of this class are taken from the SWO
software interface class (swo:SWO_9000050) [10].
• viso:license: a regulation of the right to use, modify and distribute something, in
this case software. It is declared to be equivalent to the Software Licence class
from SWO (swo:SWO_0000002), cf. Malone et al. [10].
• viso:license_clause: it is equivalent to the Licence clause class from SWO
(swo:SWO_9000005), cf. Malone et al. [10].
Selected relations (object properties) from VISO are:
• viso:has_feature points to a (model or solver) feature of a tool. Domain: viso:
software_tool; range: viso:software_tool_feature.
59
Fig. 4.1 Fragment of VISO showing its upper and intermediate classes and their connection to
EVMPO and external assets; the diagram was generated using the OWLViz protégé plugin; grey
arrows labelled “is-a” denote subsumption (), i.e. rdfs:subClassOf
especially focus on its AM branch, which deals with molecular models and particlebased methods; for more details on the other branches, we refer the reader to [31]
and to a recent VIMMP ontology release [32, 33].
Accordingly, selected major concepts from viso-general are:
• viso:software: a computer program. Its direct (mutually disjoint) subclasses are:
viso:software_tool, viso:compiler, viso:operating_system.
• viso:programming_language: a language that can be used to write software.
• viso:software_tool_feature ≡ (viso:model_feature viso:solver_feature): a
capability of a software tool, intended as either a model aspect that can be
addressed (viso:model_feature) or as a numerical algorithm which is implemented
(viso:solver_feature). Following the approach from RoMM [30], these two classes
are disjoint.
• viso:model_type: a classification of the model, intended as in RoMM [30].
• viso:model_object: the type of object entering the model and carrying degrees of
freedom. Its subclasses in the AM branch (cf. Fig. 4.2) include viso-am:interaction_
site, viso-am:interaction_surface, viso-am:connected_object.
• viso:software_update: it describes (as text) the changes between versions of a
software. In particular, its subclass viso:software_tool_update allows to describe
the addition/removal of features from a tool.
• viso:software_interface: an interface between a software and a user or a client
(i.e. a program or device). Some subclasses of this class are taken from the SWO
software interface class (swo:SWO_9000050) [10].
• viso:license: a regulation of the right to use, modify and distribute something, in
this case software. It is declared to be equivalent to the Software Licence class
from SWO (swo:SWO_0000002), cf. Malone et al. [10].
• viso:license_clause: it is equivalent to the Licence clause class from SWO
(swo:SWO_9000005), cf. Malone et al. [10].
Selected relations (object properties) from VISO are:
• viso:has_feature points to a (model or solver) feature of a tool. Domain: viso:
software_tool; range: viso:software_tool_feature.