small changes

OpenCCE.aux

@@ -5,4 +5,4 @@
 \@writefile{toc}{\contentsline {subsection}{\numberline {3.1}Usage examples}{1}}
 \@writefile{toc}{\contentsline {subsection}{\numberline {3.2}Rules}{2}}
 \@writefile{toc}{\contentsline {section}{\numberline {4}Algorithms Model}{2}}
-\@writefile{toc}{\contentsline {section}{\numberline {5}Questions for initilization}{2}}
+\@writefile{toc}{\contentsline {section}{\numberline {5}Questions for initialization}{2}}

OpenCCE.log

@@ -1,12 +1,11 @@
-This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) (preloaded format=latex 2016.7.6)  28 JUL 2016 11:32
+This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) (preloaded format=pdflatex 2016.8.15)  12 SEP 2016 11:31
 entering extended mode
  restricted \write18 enabled.
- file:line:error style messages enabled.
  %&-line parsing enabled.
 **OpenCCE.tex
 (./OpenCCE.tex
 LaTeX2e <2016/03/31>
-Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
+Babel <3.9r> and hyphenation patterns for 8 language(s) loaded.
 (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
 Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
 (/usr/share/texlive/texmf-dist/tex/latex/base/size11.clo
@@ -85,15 +84,30 @@ LaTeX Font Info:    Font shape `OMS/cmr/m/n' in size <10.95> not available
 File: lstlang1.sty 2015/06/04 1.6 listings language file
 ) [1
 
-] [2]
-(./OpenCCE.aux) ) 
+{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
+LaTeX Font Info:    External font `cmex10' loaded for size
+(Font)              <10.95> on input line 53.
+ [2] (./OpenCCE.aux) ) 
 Here is how much of TeX's memory you used:
- 1574 strings out of 494947
- 22110 string characters out of 6181067
- 98332 words of memory out of 5000000
- 4920 multiletter control sequences out of 15000+600000
- 8490 words of font info for 30 fonts, out of 8000000 for 9000
+ 1579 strings out of 494894
+ 22180 string characters out of 6178680
+ 99575 words of memory out of 5000000
+ 4939 multiletter control sequences out of 15000+600000
+ 9157 words of font info for 32 fonts, out of 8000000 for 9000
  14 hyphenation exceptions out of 8191
- 26i,6n,40p,162b,952s stack positions out of 5000i,500n,10000p,200000b,80000s
+ 26i,6n,40p,231b,952s stack positions out of 5000i,500n,10000p,200000b,80000s
+</usr/share/texlive/texmf-dist/fonts/type1/public/amsfont
+s/cm/cmbx10.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/c
+mbx12.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi10.
+pfb></usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb></u
+sr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb></usr/shar
+e/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb></usr/share/texli
+ve/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/texlive/tex
+mf-dist/fonts/type1/public/amsfonts/cm/cmti10.pfb>
+Output written on OpenCCE.pdf (2 pages, 103053 bytes).
+PDF statistics:
+ 43 PDF objects out of 1000 (max. 8388607)
+ 30 compressed objects within 1 object stream
+ 0 named destinations out of 1000 (max. 500000)
+ 1 words of extra memory for PDF output out of 10000 (max. 10000000)
 
-Output written on OpenCCE.dvi (2 pages, 5552 bytes).

OpenCCE.tex

@@ -4,22 +4,22 @@
 
 \begin{document}
 \title{Integrating CertainTrust into OpenCCE}
-\author{Nikolaos Alexpoulos, CROSSING S1}
+\author{Nikolaos Alexopoulos, CROSSING S1}
 \date{August 2016}
 
 \maketitle
 
 \section{About CertainTrust}
-CertainTrust is a robust Bayesian Computational Trust model for user and agents.
+CertainTrust is a robust Bayesian Computational Trust model for users and agents.
 It offers a mathematically sound implementation of a Bayesian probability model in order to assess the 
 trustworthiness of agents in multi-agent systems. The system can calculate the expected trustworthiness of 
-agents based on its prior experience and can also combine evidence provided by other sources in statistically 
+agents based on prior experience and can also combine evidence provided by other sources in statistically 
 sound ways. (Finally, it also offers a user interface to visualize trust when user involvement is needed.)
 By providing CertainTrust as a task to OpenCCE we want to enable users and devices to enhance their security 
 in high-risk environments.
 
 \section{Implementation}
-We have implemented OpenCCE as a Java project. More specifically, the whole fuctionality is encompassed in a 
+We have implemented OpenCCE as a Java project. More specifically, the whole functionality is encompassed in a 
 single class (CertainTrust.java). 
 The remainder of our classes support a graphical user interface intended to visualize trust in a user-friendly 
 way.
@@ -33,7 +33,7 @@ After the constructor, the main and presumably more regularly used functionaliti
 implemented by the functions \textit{addR}, \textit{addS} and \textit{addU} that respectively add positive, 
 negative and neutral 
 evidence to the statistical model. Furthermore, there are a number of ways to combine CertainTrust objects 
-by choosing a function from the set \{\textit{OR, AND, wFusion, cFusion}\}.
+by choosing a CertainLogic operator implemented in the functions from the set \{\textit{OR, AND, wFusion, cFusion}\}.
 \medskip \\
 A typical example of the use of the task could be the creation of a computational trust object and then the 
 incorporation of evidence in the statistical model that leads to an extracted expectation value for 
@@ -50,7 +50,7 @@ expectation = trustObject.getExpectation()
 \subsection{Rules}
 Rules regarding the use of CertainTrust address the correctness of the model and are provided as comments to 
 each function implemented in the class. They are normally handled by exceptions, but a static analysis 
-could have some benefit.
+could have some benefit. Specifically, values t,c and f represent probabilities and so $\in[0,1]$.
 
 \section{Algorithms Model}
 CertainTrust in its current form does not offer any variability. The task, which could be named 
@@ -58,10 +58,16 @@ CertainTrust in its current form does not offer any variability. The task, which
 tasks for each operation on the trust objects and grouping them together could be an option, but 
 is not considered practical at this point.
 
-\section{Questions for initilization}
+\section{Questions for initialization}
 The main user choices during the initialization of the task concern the arguments of the 
 \textit{createfromRS} and \textit{createfromTC}. More specifically, the user should be able to 
-choose the name of the object, an initial (prior) trust value as well as the number N of adequate evidence.
-
+choose the name of the object, an initial (prior) trust value as well as the number N of adequate evidence. A detailed list follows:
+\medskip
+\begin{enumerate}
+	\item Give the \textbf{name} of the object (e.g. ``John'', ``Bank'', etc.)
+	\item Give your perceived \textbf{initial trust value (t)} for the subject (default: t=0,5) - could be low/med/high or visualization. Its effect dissolves while experiences are collected.
+	\item Give the \textbf{maximal expected number of evidence (N)}. That is the number of evidence that suffice to provide total certainty in the trust assessment. This parameter highly depends on the 
+		context and the security assurances needed.
+\end{enumerate}
 
 \end{document}

OpenCCE.tex.bak

@@ -0,0 +1,73 @@
+\documentclass[11pt,twoside,a4paper]{article}
+
+\usepackage{listings}             % Include the listings-package
+
+\begin{document}
+\title{Integrating CertainTrust into OpenCCE}
+\author{Nikolaos Alexpoulos, CROSSING S1}
+\date{August 2016}
+
+\maketitle
+
+\section{About CertainTrust}
+CertainTrust is a robust Bayesian Computational Trust model for users and agents.
+It offers a mathematically sound implementation of a Bayesian probability model in order to assess the 
+trustworthiness of agents in multi-agent systems. The system can calculate the expected trustworthiness of 
+agents based on prior experience and can also combine evidence provided by other sources in statistically 
+sound ways. (Finally, it also offers a user interface to visualize trust when user involvement is needed.)
+By providing CertainTrust as a task to OpenCCE we want to enable users and devices to enhance their security 
+in high-risk environments.
+
+\section{Implementation}
+We have implemented OpenCCE as a Java project. More specifically, the whole fuctionality is encompassed in a 
+single class (CertainTrust.java). 
+The remainder of our classes support a graphical user interface intended to visualize trust in a user-friendly 
+way.
+
+\section{Usage examples and rules}
+\subsection{Usage examples}
+The proposed use of our task consists of a CertainTrust object constructed to handle a single trust 
+relationship. The constructor is reached by calling one of the \textit{createfromRS} or 
+\textit{createfromTC} functions. 
+After the constructor, the main and presumably more regularly used functionalities are 
+implemented by the functions \textit{addR}, \textit{addS} and \textit{addU} that respectively add positive, 
+negative and neutral 
+evidence to the statistical model. Furthermore, there are a number of ways to combine CertainTrust objects 
+by choosing a CertainLogic operator implemented in the functions from the set \{\textit{OR, AND, wFusion, cFusion}\}.
+\medskip \\
+A typical example of the use of the task could be the creation of a computational trust object and then the 
+incorporation of evidence in the statistical model that leads to an extracted expectation value for 
+the trustworthiness of the given agent. A small snippet is found below:
+\medskip
+\lstset{language=java}
+\begin{lstlisting}[frame=single]
+trustObject = CertainTrust.createDefault(N, name)
+trustObject.addR(posEvidence)
+trustObject.addS(negEvidence)
+expectation = trustObject.getExpectation()
+\end{lstlisting}
+
+\subsection{Rules}
+Rules regarding the use of CertainTrust address the correctness of the model and are provided as comments to 
+each function implemented in the class. They are normally handled by exceptions, but a static analysis 
+could have some benefit. Specifically, values t,c and f represent probabilities and so $\in[0,1]$.
+
+\section{Algorithms Model}
+CertainTrust in its current form does not offer any variability. The task, which could be named 
+``Initialize CertainTrust Object'' is self-contained in the Java class of the same name. Providing different 
+tasks for each operation on the trust objects and grouping them together could be an option, but 
+is not considered practical at this point.
+
+\section{Questions for initialization}
+The main user choices during the initialization of the task concern the arguments of the 
+\textit{createfromRS} and \textit{createfromTC}. More specifically, the user should be able to 
+choose the name of the object, an initial (prior) trust value as well as the number N of adequate evidence. A detailed list follows:
+\medskip
+\begin{enumerate}
+	\item Give the \textbf{name} of the oject (e.g. ``John'', ``Bank'', etc.)
+	\item Give your perceived \textbf{initial trust value (t)} for the subject (default: t=0,5) - could be low/med/high or visualisation. Its effect dissolves while experiences are collected.
+	\item Give the \textbf{maximal expected number of evidence (N)}. That is the number of evidence that suffice to provide total certainty in the trust assessment. This parameter highly depends on the 
+		context and the security assurances needed.
+\end{enumerate}
+
+\end{document}