2.1.2 comments Katerina

tables/continuous.tex

@@ -47,6 +47,6 @@
       \bottomrule
     \end{tabular}%
   }%
-  \caption{Continuous data observation of (a)~microdata, and corresponding (b)~statistics at multiple timestamps.}
+  \caption{Continuous data observation \kat{continuous data observation sounds like an action.. better say directly microdata and statistics gathered in consequent timestamps?} of (a)~microdata, and (b)~corresponding statistics at multiple timestamps.}
   \label{tab:continuous}
 \end{table}

text/preliminaries/data.tex

@@ -34,7 +34,7 @@ Depending on the span of the observation, we distinguish the following categorie
 
 \end{example}
 
-\kat{Why isn't here the presentation of sequential and incremental in bullets?}
+\kat{Why isn't next the presentation of sequential and incremental in bullets, as for the categories before?}
 
 We further define two sub-categories applicable to both finite and infinite data: \emph{sequential} and \emph{incremental} data; these two subcategories are not exhaustive, i.e.,~not all data sets belong to the one or the other category.
 In sequential data, the value of the observed variable changes, depending on its previous value.
@@ -46,11 +46,11 @@ For example, trajectories can be considered as incremental data, when at each ti
 \subsection{Data processing and publishing}
 \label{subsec:data-publishing}
 
-We categorize data processing and publishing based on the implemented scheme, as:
+We categorize data processing and publishing based on the implemented scheme \kat{what does the implemented scheme refer to?}, as:
 
 \begin{itemize}
-  \item \emph{Global}---data are collected, processed and privacy-protected, and then published by a central (trusted) entity, e.g.,~\cite{mcsherry2009privacy, blocki2013differentially, johnson2018towards}.
-  \item \emph{Local}---data are stored, processed and privacy-protected on the side of data generators before sending them to any intermediate or final entity, e.g.,~\cite{andres2013geo, erlingsson2014rappor, katsomallos2017open}.
+  \item \emph{Global}---data are collected, processed and privacy-protected, and then published by a central (trusted) entity, as for instance in~\cite{mcsherry2009privacy, blocki2013differentially, johnson2018towards}.
+  \item \emph{Local}---data are stored, processed and privacy-protected on the side of data generators before sending them to any intermediate or final entity, as for instance in~\cite{andres2013geo, erlingsson2014rappor, katsomallos2017open}.
 \end{itemize}
 
 \begin{figure}[htp]
@@ -65,10 +65,11 @@ We categorize data processing and publishing based on the implemented scheme, as
   \label{fig:privacy-schemes}
 \end{figure}
 
-In the case of location data privacy, the existing literature is divided in
+In the case of location data privacy, the existing literature\kat{do not say literature, but sth related to the data processing and publishing} is divided in
 \emph{service-} and \emph{data-}centric methods~\cite{chow2011trajectory}.
 The service-centric methods correspond to scenarios where individuals share their privacy-protected location with a service to get some relevant information (local publishing scheme).
 The data-centric methods relate to the publishing of user-generated data to data consumers (global publishing scheme).
+\kat{I do not get the data-centric methods.. Can't data-centric be also service centric ?  E.g., we publish our data to get back some service? Moreover, what is exactly the link between local and global and service and data centric? One to one ?}
 
 There is a long-standing debate whether the local or the global architectural scheme is more efficient with respect to not only privacy, but also organizational, economic, and security factors~\cite{king1983centralized}.
 On the one hand, in the global privacy scheme (Figure~\ref{fig:scheme-global}), the dependence on third-party entities poses the risk of arbitrary privacy leakage from a compromised data publisher.