DataProcessing is not a SoftwareElement

[akleinau]

Description of the issue

DataProcessing is a subclass of SoftwareElement right now. It's more likely a process. And needs a def.

Is DataProcessing a Transformation? Transformatioon is defined as a process that transforms one or more inputs into at least one output, so I'd say yes.

A def would be: DataProcessing is a Transformation of data.

Ideas of solution

Workflow checklist

• [x] I discussed the issue with someone else than me before working on a solution
• [x] I already read the latest version of the workflow for this repository
• [x] The goal of this ontology is clear to me

I am aware that

• [x] every entry in the ontology should have an annotation
• [x] classes should arise from concepts rather than from words
• [x] class or property names should follow the UpperCamelCase

[akleinau]

as discussed in february ontohack:

• reclassify as transformation
• has_participant data item
• def: data processing is a transformation which has the relation: 'has participant' 'data item'

[akleinau]

I tried to implement this and found a problem:

• we have classes DataPostprocessing and Postprocessing
• we have classes DataPreprocessing and Preprocessing

for me they seem identical so I'd propose to delete Postprocessing and Preprocessing.

[akleinau]

@jannahastings do you agree?

[jannahastings]

I agree, we don't need the generic 'postprocessing' or 'preprocessing' of anything, in this domain the more useful classes are specific to data.