Add preliminary roadmap.

1 files changed, 43 insertions, 4 deletions

diff --git a/index.osml b/index.osml
index 02510f2..549f749 100644
--- a/index.osml
+++ b/index.osml
@@ -36,7 +36,7 @@
 
 Ousía is a research project and not suitable for end-users yet. However, we
 provide a developer preview for those who want to try out the current state of
-development. Current features include:
+development. Features include:
 
 \dl{
 	\item{LaTeX-esque markup language (OSML)}
@@ -66,9 +66,9 @@ well, due to:
 	Allow to reuse of content, concepts and styles across documents
 
 	\item{Separation of Presentation and Content}
-	Document Layout can be created based on ontologies only allowing authors to
-	focus on content rather than form.
-	
+	Layout is indepentend of the document, allowing authors to focus on content
+	rather than form.
+
 	\item{Conversion to other formats}
 	Ontologies as common interface layer facilitate the construction of
 	converters and support re-using modules of other converters.
@@ -78,7 +78,46 @@ well, due to:
 	changed independently of other users.
 }
 
+\section{Roadmap}
 
+Ousía Framework is far from being finished. This list contains several tasks and
+features we plan to implement in the coming months and years (without any particular
+order, highly incomplete and subject to change):
+\dl{
+	\item{Documentation}
+	Write a tutorial on how to use Ousía and provide reference documentation for
+	the OSML and OSXML formats.
+
+	\item{Standard Ontology Library}
+	Based on the experience of writing this website and the documentation build
+	a sane standard ontology library for Books, Articles, Websites and Metadata.
+
+	\item{JavaScript API}
+	Internally we already maintain method and property information about
+	“managed” objects in the document graph. Additionally, a prototype binding
+	to MozJs already exists. Time to stick the two together and – in a first
+	step – allowing user defined parsing and validation functions for
+	structures. This can e.g. be used to parse and verify E-Mail addresses, BICs
+	or IBANs.
+
+	\item{Ontology Metadata}
+	Allow users to write documentation for their ontologies (like JavaDoc or
+	Doxygen). Allow to create an Ousía document from this documentation and
+	publish the current version on this Website.
+
+	\item{Output transformation}
+	Implement the output transformation pipeline. This goal is as of now
+	somewhat fuzzy, but the goals are to have an API that allows partial
+	template matching as in XSLT to allow online updating of the output,
+	chaining of transformations and both a C++ and JavaScript API.
+
+	\item{Stylesheets}
+	Allow transformations to define style properties that can be used in
+	CSS-like stylesheets. Apply style information to the document graph, allow
+	inheritance of the style information along the ontology graph to escape
+	the combinatorial explosion that results from having user-defined ontologies
+	and user-defined transformations.
+}
 
 \end{webpage}