ProcessParameterSet (target values)

[hoffmannmic]

The question is how to handle target values (concept of a process parameter set in the kdb-framework)?

Option 1: Process Profiles

"[...] then there is something in each of the two processes which is – not numerically but qualitatively – ‘the same’. This something which the two processes share in common we shall refer to in what follows to as a process profile." from https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3718480/pdf/nihms399452.pdf

Process profile is tightly connected to a temporal region and basically all examples are about some (measured) quality during a process.

Option 2: PERFORMANCE SPECIFICATION

"The Modal Relation Ontology (MRO) provides a way of representing states of affairs that are prescribed (e.g., an action prescribed by a plan or some functionality prescribed by an artifact’s design specification), but which do not exist yet, or may never exist." from https://www.nist.gov/system/files/documents/2021/10/14/nist-ai-rfi-cubrc_inc_004.pdf

Here performance specification is an Information Content Entity and not a measured quantitiy. That is we could distinguish between the planned parameter and the actual measured one.

[ThHanke]

Following Image Copied out of the common core ontology documentation illustates how that is supposed to work. I think it is a straight forward example. Lets discuss this...

[hoffmannmic]

Based on my limited experience,

• using "process profile" would solve cases like "the sample was tempered at 150°C for 1 hour before measurement"

• the "PERFORMANCE SPECIFICATION" part could solve the issue "actual performance can diverge from the
  performance"; so something like "I have a process parameter set/plan, like temper the sample at 150°C, but the actual measured value during tempering is 145°C"