use todonotes package

[skm-ma-ws1314.git] / main.tex

diff --git a/main.tex b/main.tex
index 51d61f4..b2681ad 100644 (file)
--- a/main.tex
+++ b/main.tex
@@ -5,12 +5,13 @@
 \usepackage{color}
 \usepackage{graphicx}
 \usepackage{wrapfig}
-\usepackage{hyperref}
-
+\usepackage[hidelinks=true]{hyperref}
+\usepackage{todonotes}
+\usepackage{tikz}
+\usetikzlibrary{arrows}
 \urlstyle{sf}
 
 \newcommand{\pages}[1]{\marginpar{#1 pages}}
-\newcommand{\todo}[1][]{\textcolor{red}{TODO #1} \\}
 \newcommand{\term}[1]{\emph{#1}}
 \newcommand{\code}[1]{\textsf{#1}}
 
@@ -24,17 +25,20 @@ Masses with XMPP}
 
 %% Introduction
 \section{Introduction}
-\todo
+\todo{asdf}
 \pages{0-1}
-short overview, not too long: what do we want, what are we
-going to do
+short overview, not too long: what do we want, what are we going to do?
+
+how do we talk to our smart home?
 
-basically: how do we talk to our smart home?
-\paragraph{Human-to-Machine Communication:} especiall in the Internet of Things,
-       Chatty Things need to be accessible for the user and should be easy to talk
-       to.
-\paragraph{Interoperability} integration into already existing
-infrastructure.
+what are the challenges? (interoperability, H2M interface, self-configuration,
+information filtering to prevent information overflow)
+
+%\paragraph{Human-to-Machine Communication:} especiall in the Internet of Things,
+       %Chatty Things need to be accessible for the user and should be easy to talk
+       %to.
+%\paragraph{Interoperability} integration into already existing
+%infrastructure.
 
 %% Prerequisites
 \section{Prerequisites}
@@ -47,50 +51,7 @@ overview to the techniques used in the paper by Klauk and Kirsche
 \input{sec-dns-extensions.tex}
 \input{sec-xmpp.tex}
 \input{sec-chatty-things.tex}
-
-\section{Related Approaches}
-\todo
-\pages{3}
-Middleware, Application protocol gateways:
-\begin{itemize}
-       \item Constrained Application Protocol \cite{draft-ietf-core-coap-18}
-       \begin{itemize}
-               \item machine-to-machine
-               \item everything-built-in
-               \item discovery over multicast, service discovery over /.well-known
-                       entry-point
-               \item maps to HTTP => stateless => relies on application gateway
-               \item low protocol overhead and parsing complexity (binary messages)
-               \item only draft status
-               \item UDP with Ack and IDs instead of TCP... (limited state machine)
-               \item proxies
-               \item asynchronous messages
-       \end{itemize}
-       \item MQ Telemetry Transport \cite{mqtt}
-       \begin{itemize}
-               \item TCP/IP
-               \item small overhead: 2 byte header + variable header length
-               \item publish-subscribe with topic names
-               \item binary protocol => application-level gateway
-               \item discovery?
-       \end{itemize}
-       \item Devices Profile for Web Services \cite{zeeb-moritz-ws4d}
-       \begin{itemize}
-               \item TCP/IP -> HTTP -> SOAP -> Web Services. Overhead!
-               \item but very extendable and composable
-               \item discovery as a service
-               \item focused on multiple platforms, deeply embedded and servers
-               \item IPv6 partly experimental
-               \item ROM usage of uDPWS: 45 kByte
-       \end{itemize}
-
-\end{itemize}
-
-\section{Discussion}
-\todo
-comparison of mentioned approaches
-
-\pages{1-2}
+\input{sec-discussion.tex}
 
 \bibliographystyle{plain}
 \bibliography{biblio}