1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
%{
Ousía Homepage
(c) Andreas Stöckel, Benjamin Paaßen 2015
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0
International License. <http://creativecommons.org/licenses/by-sa/4.0/>
}%
\import[ontology]{ontology/webpage}
\begin{webpage}{Ousía Framework - About}
\begin{masthead}
\title{Ousía}
\subtitle{Extensible Semantic Markup Framework}
\begin{pitch}
\paragraph
\ipa{ˈuːziə}{Ousía} represents documents in purely semantic markup with
user definable structure.
\paragraph
Documents are parsed into an universal intermediate representation,
ready to be converted to any format using XSLT
\footnote{Sticking to XML and XSLT is not our plan. We intend to provide
a scriptable output pipeline. But we're not quiet there yet.}.
\end{pitch}
\begin{nav}
\button#btn_download[href=download.html]{Download the Source Code (pre-alpha)}
\end{nav}
\end{masthead}
\section{Features}
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. Features include:
\dl{
\item{LaTeX-esque markup language (OSML)}
Ousía implements an expressive and consistent LaTeX-esque markup language
which can be used for both document markup and writing ontology descriptions.
\item{Command line interface}
As reference implementation we provide a command line application written in
C++.
\item{Serialization to XML}
Documents can be dumped as XML, ready to be converted to another format
using XSLT.
\item{Structure and Annotations}
Ousía allows to include both: Document structure and flexible, possibly
overlapping annotations.
}
\section{About}
Ousía Framework aims at coupling Semantic Web techniques with structured data.
This is not only of interest to the research community but to the end user as
well, due to:
\dl{
\item{Re-usability}
Allow to reuse of content, concepts and styles across documents
\item{Separation of Presentation and Content}
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.
\item{Collaborative and concurrent document creation}
Graphical document structure provides well-defined parts that can be
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}
|
