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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" type="text/css" href="../style/style.css">
<title>Ousía Framework - About</title>
</head>
<body lang="en">
<main>
<!--<header>
<section>
<h1>Ousía Framework</h1>
<nav>
<ul>
<li><a href="index.html">About</a></li>
<li><a href="download.html">Download</a></li>
</ul>
</nav>
</section>
</header>-->
<section class="chapter">
<h1>What is the Ousía Framework?</h1>
<figure>
<img src="../media/Raffael_058.jpg"/>
<figcaption>
<span class="source">The School of Athens by Raphael, 1509-1510 <a href="http://commons.wikimedia.org/wiki/File:Raffael_058.jpg" rel="external">(Wikimedia Commons)</a></span>
Ousía (οὐσία) is a term used by ancient greek philosophers to
describe <q>The entirety of constant features, based on which
objects can be defined</q>.</figcaption>
</figure>
<p>Let's start with the mandatory one-sentence sales-pitch answer to
the above question:</p>
<blockquote>Ousía is a framework for representing documents in a
user extensible markup language, allowing transformation to a
a variety of output formats.</blockquote>
<p>There you go!</p>
<p>Still confused and unsure what Ousía is and what you can do with
it? So are we. Read on to be enlightened!</p>
<h2>What Ousía is <em>not</em></h2>
<p>Whenever we're asked what Ousía is, we have a hard time
giving a short and precise answer. This is not because Ousía is
overly complicated – the answer just very much depends on the
direction from which you look at Ousía.</p>
<p>To avoid any misconceptions, let's start answering the easier
question: What Ousia is <em>not</em>. If you don't know the
technologies we refer to here, you can safely skip these sections.
</p>
<section class="subsection">
<h3>Ousía is not LaTeX</h3>
<aside>Ousía is not a typesetter. It lets you define the meaning of
your document, and not what it looks like.</aside>
<p>You may have seen examples of documents written in the Ousía
Markup Language and thought “Well, that's just LaTeX!”. Rest
assured, Ousía is nothing like that. Yes, one of our formats looks a
little bit like TeX, but, you know, any resemblance to real persons,
living or dead, is purely coincidential.</p>
<p>TeX is a typesetter. It is a programming language aimed at
controlling how text is fitted onto a printed page, merely
automating a job that has been
<a rel="external" href="http://en.wikipedia.org/wiki/Typesetting">done manually for
centuries</a>. And LaTeX is a bunch of macros for authoring TeX
documents in a less awkward way.</p>
<p>Ousía knows nothing about typesetting. It doesn't even know what
medium your document will end up on. Ousía is for describing the
content of your document. Nothing more.</p>
</section>
<section class="subsection">
<h3>Ousía is not an editor</h3>
<p>Ousía is not an editor application. Ousía documents are written
in one of two markup languages (<abbr title="Ousía Semantic Markup Language">OSML</abbr> or <abbr title="Ousía Semantic XML">OSXML</abbr>) which
basically are plain text files. These files are then handed to an
application called <code class="language-bash">ousia</code> that
will parse them, check for errors and transform them to another
format.</p>
<p>There may be special editors that help you writing Ousía
documents or that use the underlying program library
<code>libousia</code> to provide a more convenient editing
experience, but this doesn't change the bigger picture.</p>
</section>
<section class="subsection">
<h3>Ousía does not replace Semantic Web technologies</h3>
<figure>
<img src="../media/Kizil_Hauzen_Bridge_2013.jpg"/>
<figcaption>
<span class="source">Kizil Hauzen Bridge, Iran, 2013 <a href="http://commons.wikimedia.org/wiki/File:Kizil_Hauzen_Bridge_2013.jpg" rel="external">(Wikimedia Commons)</a></span>
We aim at building a bridge to end the seperation of the
ordinary user from the the power of the Semantic Web, there,
awaiting them on the other side.</figcaption>
</figure>
<aside>Ousía makes the Semantic Web approachable for muggles.</aside>
<p>It is possible (though unlikely, they are a rare species)
that you are a Semantic Web expert: You know all three dialects of
<abbr title="Web Ontology Language">OWL</abbr>, write your
love-letters in <abbr title="Resource Description Framework">RDF</abbr>
and transform vegetables into supper using <abbr title="Extensible Stylesheet Language Transformations">XSLT</abbr>, just to devour it with your
SPARQL powers.</p>
<p>In that case you'll very likely say: <q>I have everything I need!
Leave my standards alone! They are mine, all mine! My precious!</q></p>
<p>Well, fear not! We're there to help. We too believe the Semantic
Web is great, but we want to allow everyone to write documents
with semantic markup. We've designed Ousía to be as simple as
possible for the end-user. It will be possible to export Ousía
ontologies and documents to all those shiny, complex,
incomprehensibly powerful W3C standards. Promised.</p>
</section>
<section class="section">
<h2>Semantic Markup unleashed</h2>
<p>In this section we will skim over a few examples of how Ousía can
be used, giving you a quick impression.</p>
<section class="subsection">
<h3>Express what you mean</h3>
<p>One aspect of Ousía is its <dfn>document markup language</dfn>.
It allows you to write the text of your document while attaching
additonal information to the text using special <dfn>commands</dfn>.
</p>
<p>Let's assume you wanted to write a book (e.g. <a rel="external" href="https://www.gutenberg.org/ebooks/74">The Adventures of Tom Sawyer</a> by Samuel Langhorne Clemens alias Mark Twain). You could start writing it down like this:</p>
<pre><code class="language-osml">
THE ADVENTURES OF TOM SAWYER
by
Mark Twain
(Samuel Langhorne Clemens)
PREFACE
Most of the adventures recorded in this book really occurred;
one or two were experiences of my own, the rest those of boys
who were schoolmates of mine. Huck Finn is drawn from life;
Tom Sawyer also, but not from an individual—he is a
combination of the characteristics of three boys whom I knew,
and therefore belongs to the composite order of architecture.
</code></pre>
<pre><code class="language-osml">
\import[ontology]{book} % We want to write a book
\import[ontology]{novel} % We want to do some novel writing
\begin{book}[lang=en]{The Adventures of Tom Sawyer}
% Add some meta-information about the book at hand
\begin{meta}
\author[realname]{
\name{
\first{Samuel}
\middle{Langhorne}
\last{Clemens}
}
\name[alias]{
\first{Mark}
\last{Twain}
}
}
\published{1876}
\end{meta}
% Define the characters that occur in the book -- we can
% later reference them by their name ("hashtag")
\begin{characters}
\def#hf{
\name{
\first{Huckleberry}
\first[short]{Huck}
\last{Finn}
}
}
\def#ts{
\name{
\first{Thomas}
\first[short]{Tom}
\last{Sawyer}
}
}
\end{characters}
% Start of the actual content -- we can annotate certain
% parts of the document to reference one of the characters
% defined above
\begin{preface}
Most of the adventures recorded in this book really
occurred; one or two were experiences of my own, the
rest those of boys who were schoolmates of mine.
::{hf}Huck Finn:: is drawn from life; ::{ts}Tom
Sawyer:: also, but not from an individual—he is a
combination of the characteristics of three boys whom
I knew, and therefore belongs to the composite order
of architecture.
\end{preface}
\end{book}
</code></pre>
</section>
</section>
</section>
</main>
<!--<footer>
<section>
<nav>
<ul>
<li>
<h3>Learn</h3>
<ul>
<li><a href="index.html">About</a></li>
</ul>
</li>
<li>
<h3>Get Ousía</h3>
<ul>
<li><a href="download.html">Download</a></li>
</ul>
</li>
<li>
<h3>Develop</h3>
<ul>
<li><a href="https://gitlab.com/ousia-framework/ousia">GitLab</a></li>
<li><a href="https://gitlab.com/ousia-framework/ousia/tree/master">Browse source</a></li>
<li><a href="https://gitlab.com/ousia-framework/ousia/issues">Bug tracker</a></li>
</ul>
</li>
<li>
<h3>Legal</h3>
<ul>
<li><a href="impressum.html">Impressum</a></li>
<li><a href="license.html">License</a></li>
</ul>
</li>
</ul>
</nav>
</section>
<section id="copyright">
<p>Ousía – Extensible Semantic Markup Framework (c) 2015 Andreas Stöckel, Benjamin Paaßen</p>
<p>Unless noted otherwise the content of this website (including, but not limited to text, images, markup and stylesheets) is licensed under the <a href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>. The uncompiled source code of the website is available <a href="download.html">here</a>.</p>
<p>This website was made using <a href="http://git-scm.com/">git</a>, <a href="http://lesscss.org/">Less</a>, <a href="http://ousia-framework.org/">Ousía</a> and <a href="http://xmlsoft.org/libxslt/">xsltproc</a>.</p>
</section>
</footer>-->
<script src="../script/ousia.js"></script>
</body>
</html>
|
