diff --git a/ActiveDocs.PNG b/ActiveDocs.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..fdfaba2a3f755e5bad67024f3f231deb7fc47df5
Binary files /dev/null and b/ActiveDocs.PNG differ
diff --git a/ActiveDocumentsOverview.tex b/ActiveDocumentsOverview.tex
new file mode 100644
index 0000000000000000000000000000000000000000..826c40c9b226b0237025662acb0d46211ab0d95e
--- /dev/null
+++ b/ActiveDocumentsOverview.tex
@@ -0,0 +1,70 @@
+\documentclass{report}
+\usepackage[style=alphabetic,backend=bibtex]{biblatex}
+\addbibresource{kwarc.bib}
+\addbibresource{rest.bib}
+\usepackage[show]{ed}
+\usepackage{hyperref}
+\usepackage{enumitem}
+\usepackage{graphicx}
+\graphicspath{ {} }
+\newcommand\tab[1][1cm]{\hspace*{#1}}
+
+
+\begin{document}
+
+\section{What is there?}\label{sec:intro}
+
+\section{What they want to do?}
+\label{sec:jupyther}
+
+\section{Active Documents}
+
+\subsection{Introduction}
+
+\tab A framework that allows papers to be executable, give
+access to provenance and copyright/licensing information, and support various forms of validation. We contend that
+these challenges can be realized based on semantically annotated documents together with semantic background
+ontologies, which we call the content commons. This information can then be used by user-visible, interactive
+services like program execution, computation, visualization, navigation, information aggregation and information
+retrieval. Finally a document player application can embed these services to make documents executable. We call this
+framework the Active Documents Paradigm (ADP), since documents can also actively adapt to user preferences and
+environment rather than only executing services upon user request. \\
+
+\begin{figure}[h]
+	\centering
+	Figure 5: Active Documents
+    \includegraphics{ActiveDocs.png}
+\end{figure} 
+
+\tab We present the ADP with a focus on three distinct annotation levels, "presentation structure", "semantic",
+and "formal".
+
+\subsection{Presentation Structure}
+
+\tab The importance of the presentation structure level is that an active document player (1) can turn legacy documents into active documents by transforming them into XHTML+MathML+SVG-encoded documents with semantic annotations in RDFa. \\
+\tab We have transformed over half a million articles from the Cornell ePrint arXiv to XHTML+MathML with La-TeXML, preserving properties like document and formula structures and embedded them into an instance the Planetary System, an active documents player. \\
+
+\tab The document structure can then be exploited for a FoldingBar service (see on the left in Figure 6) and for
+localizing discussions about document content to document structures and subformulae – e.g. for questions/answers,
+or reviewers’ comments. In the situation in Figure 1 we have clicked on formula (1), which pops up the IconMenu with three options: reporting errors in the content (bug icon), asking/answering a question (question mark icon), and accessing the discussion threads of this element (balloons icon). Here, a click on the question mark icon allowed us to pose a question and hope for an anser by other users in the forum. Figure 6 also shows the Planetary InfoBar
+with information markers on the right, which indicate the availability and state of the discussion threads pertaining to information objects in the line they are horizontally aligned with. Clicking them will highlight all items that have discussions. Localized discussions have proven a very valuable tool for community-based validation of papers,
+especially if they are coupled with a discussion subscription/trackback system for readers and personal notification system for authors. \\
+
+\begin{figure}[h]
+	\centering
+	Figure 5: Interacting with an article
+    \includegraphics{PresentationStructure.png}
+\end{figure} 
+
+\subsection{Semantic Level}
+
+\tab We can considerably improve the user experience by extending the depth of semantic annotations. For this we employ OMDoc (Open Mathematical Documents), an XML-based content-oriented, semiformal representation format for scientific and technical documents.
+
+\subsection{Formal Level}
+
+\section{Next Steps}\label{sec:steps}
+
+\section{Conclusion}\label{sec:conc}
+
+
+\end{document}
\ No newline at end of file
diff --git a/PresentationStructure.PNG b/PresentationStructure.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..85964f6f367dd90eef2d64de0700303e00d2421d
Binary files /dev/null and b/PresentationStructure.PNG differ