Further purging “model” as per yarik...

publishing/article/discussion.tex

@@ -14,10 +14,10 @@ \subsection{Reexecutability}
 Further, reexecutability is a far more scalable process, allowing the reliable estimation of the intrinsic variability of a research workflow.
 
 We demonstrate the feasibility of full research output reexecution by integrating cutting-edge technological capabilities, and publish all resources for open access, adaptation, inspection, and re-use.
-The article reexecution model which we produced isolates data and original resources, and does not make assumptions about the internal structure of a reexecutable article, and is of course, not domain-specific.
+The article reexecution system which we produced isolates data and original resources, and does not make assumptions about the internal structure of a reexecutable article, and is of course, not domain-specific.
 In particular, the code of the original article is managed as a sumbodule, and triggered via a freely configurable and lightweight Bash script.
 This means that given any Bash entry point, any article could be substituted for the present article in our topology.
-Our model also supports version tracking for all required resources, thus offering perfect transparency into what instructions and which external data is used in article reexecution.
+Our system also supports version tracking for all required resources, thus offering perfect transparency into what instructions and which external data is used in article reexecution.
 In particular, we rely heavily on DataLad, a technology which renders the versioning capabilities of Git usable in the context of large binary data.
 
 \subsection{Reproducibility}
@@ -60,7 +60,7 @@ \subsection{Challenges}
 \subsection{Outlook}
 
 We propose a few key considerations for the further development of the present technology.
-However, we note that practical reuse of our model might better identify promising enhancements better than theoretical analysis.
+However, we note that practical reuse of our new system might better identify promising enhancements better than theoretical analysis.
 
 In particular, we find that reexecutable article debugging in a container environment is a significant challenge, and one which will only be more severe if such an environment is already implemented in an incipient state of the article, when analysis processes are not fully fleshed out.
 To alleviate this we consider two possible solutions.
@@ -85,7 +85,7 @@ \subsection{Outlook}
 For this purpose our workflow also produces and records all of the top-level data (statistical maps, data tables, etc.) from which the article extracts elements relevant to its statements.
 
 Lastly, we highlight the relevance of automated workflows for reuse and adaptation.
-This includes both the reexecution model published herein, and the internal workflow of the original article
+This includes both the reexecution system published herein, and the internal workflow of the original article
 A key strength of reexecutability is that workflows can easily be derived, with a reliable starting point with respect to successful process execution.
 This refers not only to reuse for novel or derived studies, but also reuse for the inspection of specific parameter modifications.
 In view of this we recommend a practical approach to the work described herein, whereby the tools can all be considered to be immediately and freely available for inspection and personal use of the reader.