A validated data state is a SWEET data state reached after a validation process has acted on the data.12
SWEET restricts the class to things that had a process of type Validation, and it places Validation under Verification.12 In Earth observation, CEOS defines validation as the process of assessing, by independent means, the quality of the data products derived from system outputs.3
That independence separates validation from calibration, which CEOS describes as defining a system’s response to known and controlled signal inputs.3 Retained sources do not reconcile this sense with the validation set of machine-learning workflows, so the page does not equate them.3
Retained sources do not say that a validated state implies a quantified accuracy or a passed threshold. They do not define a pass criterion, so the term records that validation was carried out, not that it succeeded.
Footnotes
-
ESIP Federation, “SWEET ontology, state data processing module”. https://raw.githubusercontent.com/ESIPFed/sweet/master/src/stateDataProcessing.ttl ↩ ↩2
-
ESIP Federation, “SWEET ontology, representation data service validation module”. https://raw.githubusercontent.com/ESIPFed/sweet/master/src/reprDataServiceValidation.ttl ↩ ↩2
-
Committee on Earth Observation Satellites, “Working Group on Calibration and Validation”. https://ceos.org/ourwork/workinggroups/wgcv/ ↩ ↩2 ↩3