-This figure differs from the presented \gls{IOT} architecture because one describes the software architecture and the other a software development model.
-Though some concepts can be mapped upon eachother.
-Applying the concepts of \gls{LSOC} to \gls{IOT} systems can be done in two ways.
-Firstly, edge devices can be seen as simple resources, thus accessed through the resource access layer.
-The second view is that edge devices contain miniature \gls{LSOC} systems in itself as well.
-In \gls{TOSD} the same can be applied.
-The individual components in the miniature systems, the tasks, the \glspl{SDS}, are connected to the main system.
-\todo{legt dit de link goed genoeg uit?}
-
-\Citet{steenvoorden_tophat_2022} distinguishes two instruments for \gls{TOP}: \gls{TOP} languages and \gls{TOP} engines.
-The language is the \emph{formal} language for specifying interactive systems.
-The engine is the software or hardware that executes these specifications as a ready-for-work application.
-\todo{uit\-brei\-den, ver\-wij\-de\-ren?}
-
-\subsection{\texorpdfstring{\Gls{ITASK}}{ITask}}
-The concept of \gls{TOP} originated from the \gls{ITASK} framework, a declarative interactive systems language and \gls{TOP} engine for defining multi-user distributed web applications implemented as an \gls{EDSL} in the lazy pure \gls{FP} language \gls{CLEAN} \citep{plasmeijer_itasks:_2007,plasmeijer_task-oriented_2012}.
-From the structural properties of the data types, the entire user interface is automatically generated.
-Browsers are powering \gls{ITASK}'s perception layer.
+\Cref{fig:tosd} differs from the presented \gls{IOT} architecture shown in \cref{fig:iot-layers} because they represent different concepts.
+The \gls{IOT} architecture is an execution architecture whereas \gls{TOSD} is a software development model.
+E.g.\ from a software development perspective, a task is a task, whether it is executed on a microcontroller, a server, or a client.
+Only when a task is executed, the location of the execution becomes important, but this is taken care of by the system.
+Some concepts from the \gls{TOSD} model can be mapped upon the \gls{IOT} architecture in two ways.
+Firstly, edge devices can be seen as simple resources, thus accessed through \glspl{SDS}.
+The second view is that edge devices contain miniature \gls{TOP} systems in itself.
+The individual components in the miniature systems, the tasks, the \glspl{SDS}, are, in the eventual execution, connected to the main system.
+
+\subsection{The \texorpdfstring{\gls{ITASK}}{iTask} system}
+The concept of \gls{TOP} originated from the \gls{ITASK} framework, a declarative language and \gls{TOP} engine for defining interactive multi-user distributed web applications.
+The \gls{ITASK} system is implemented as an \gls{EDSL} in the programming language \gls{CLEAN}\footnote{\Cref{chp:clean_for_haskell_programmers} contains a guide for \gls{CLEAN} tailored to \gls{HASKELL} programmers.} \citep{plasmeijer_itasks:_2007,plasmeijer_task-oriented_2012}.
+From the structural properties of the data types and the current status of the work to be done, the entire \gls{UI} is automatically generated.
+Browsers are powering \gls{ITASK}'s presentation layer.