diff options
author | Boud Roukema <boud@cosmo.torun.pl> | 2020-04-19 17:22:59 +0200 |
---|---|---|
committer | Boud Roukema <boud@cosmo.torun.pl> | 2020-04-19 17:22:59 +0200 |
commit | e8f5b6aed32fc7cf41c00216d0f18ef6c8e3a4d6 (patch) | |
tree | 6b962ec25b76d7231c1c335148a0e52ab6da2f4c | |
parent | 4e9e145afe79faac1cca38e86d5d7ffecdc1c91f (diff) |
Principles - P4 verifiable inputs and outputs
One superfluous word was removed.
-rw-r--r-- | paper.tex | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -258,7 +258,7 @@ However, designing a modular project needs to be encouraged and facilitated. Oth The project should contain automatic verification checks on its inputs (software source code and data) and outputs. When applied, expert knowledge will not be necessary to confirm the correct reproduction. -\emph{Comparison with existing:} Such verification is usually possible in most systems, but adding this is usually the responsibility of the user alone. +\emph{Comparison with existing:} Such verification is usually possible in most systems, but this is usually the responsibility of the user alone. Automatic verification of inputs is commonly implemented, but the outputs are much more rarely verified. \item \label{principle:history}\textbf{History and temporal provenance:} |