deletions | additions       diff --git a/chapter_The_USAR_Ontology_The__.tex b/chapter_The_USAR_Ontology_The__.tex  index a505e18..7881b37 100644  --- a/chapter_The_USAR_Ontology_The__.tex  +++ b/chapter_The_USAR_Ontology_The__.tex 
...
\item Modular ontology design  As seen already from the previous discussion, such an USAR Ontology has many perspectives, and from each different perspective requires different types of data to be captures and correctly represented for reasoning purposes. Hence, we propose a modular ontology design, that would be able to plug in all domains and aspects needed in TRADR into one ontology, fulfilling the level of specificity for each module as needed. E.g:for the domain of disasters and disaster response we are only interested in the urban search and rescue operations, but from the team perspective, the team module could fit any other operational team in another domain.  \begin{itemize} \begin{enumerate}  \item Domain ontology  \end{itemize} The domain ontology captures the domain of Urban Search and Rescue.  \item HL - Situation awareness, human perspective  \item User model  \item Teamwork model  From the team perspective every actor (human or robot) in the mission is a team member with a specific role, activity status, a set of capabilities, and a list of assigned tasks. Some properties will be clearly human-specific: level of cognitive overload, physical tiredness, etc., and some robot-specific: battery level, . But from the team perspective they are viewed as equal, with different and varying properties.   \end{enumerate}  \item LL - Sensor data, robot 
...
\end{itemize}