Capability
type: Class
subclass of: Support
comment: any datanode which provides capabilities to the program, including pre-existing modules, functions, libraries

Constant
type: Class
subclass of: Datanode
comment: Changing this does not affect the rationale of the journey. E.g.: the configuration path to the folder where to save the results.

Input
type: Class
subclass of: Datanode
comment: a pre-existing data object served to the program for consumption and manipulation

Journey
type: Class
comment: Many Journeys in 1 ontology 1 Journey (can be) 1 named graph Journey subClassOf foaf:Document How to compare / link journeys -> by shared nodes (imports, constants) How to compare / link datanodes -> by their Types
comment: Wraps all datanodes?

Output
type: Class
subclass of: Datanode
comment: a datanode produced by the program

Parameter
type: Class
subclass of: Datanode
comment: any datanode which is not supposed to be modified by the program but is needed to tune the behaviour of the process. For example, a data source is split in 2 parts, 20% for the test set and 80\% for the training set. 2, 20%, and 80% are all parameters.

Reference
type: Class
subclass of: Support
comment: Any datanode used as background knowledge by the program, for example, a lookup service or a knowledge graph. Such datanode pre-exists the program and is external to the program.

Reuse
type: Class
subclass of: Activity
comment: as in python module import

Support
type: Class
subclass of: Datanode
comment: Also documentation/comments can be considered support
comment: To include objects such as libraries, functions, etc...