diff options
Diffstat (limited to 'mockup/what_is_ousia.osml')
| -rw-r--r-- | mockup/what_is_ousia.osml | 165 |
1 files changed, 165 insertions, 0 deletions
diff --git a/mockup/what_is_ousia.osml b/mockup/what_is_ousia.osml new file mode 100644 index 0000000..c8b6eb8 --- /dev/null +++ b/mockup/what_is_ousia.osml @@ -0,0 +1,165 @@ +\import[ontology]{./article.osml} + +\begin{article}{What is the Ousía Framework} + +\begin{definitions} + % Abbreviations + \abbr#OSML{!Ousía Semantic Markup Language} + \abbr#OSXML{!Ousía Semantic XML} + \abbr#OWL{!Web Ontology Language} + \abbr#RDF{!Resource Description Framework} + \abbr#XSLT{!Extensible Stylesheet Language Transformations} + \abbr#SPARQL{!SPARQL Protocol And RDF Query Language} +\end{definitions} + +\begin{figure#school_of_athens} + \img{ + \src{../media/Raffael_058.jpg} + \title{The School of Athens} + \artist{Raphael} + \date{1509-1510} + \source{ + \href{http://commons.wikimedia.org/wiki/File:Kizil_Hauzen_Bridge_2013.jpg}{Wikimedia Commons} + } + } + \caption{Ousía (οὐσία) originally is a term used by ancient greek philosophers to describe <<The entirety of constant features, based on which objects can be defined>>.} +\end{figure} + +Let's start with the mandatory one-sentence sales-pitch answer to the above question: + +\quote{Ousía is a framework for representing documents in a user extensible markup language, allowing transformation to a a variety of output formats.} + +Still confused and unsure what Ousía is and what you can do with it? So are we. Read on to be enlightened! + + +\section{What Ousía is <\em not\>} + +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. + +To avoid any misconceptions, let's start answering the easier question: What Ousia is <\em not\>. If you don't know the technologies we refer to here, you can safely skip the corresponding sections. + + +\subsection{Ousía is not LaTeX} + +\aside{Ousía is not a typesetter. Instead of styling it lets you define the meaning of your document.} + +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. + +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 done manually for centuries\cite{wiki_typesetting}. And LaTeX is a bunch of macros for authoring TeX documents in a less awkward way. + +Ousía knows nothing about typesetting. It doesn't even know what medium (Webpage, Paper, E-Book) your document will end up on. Ousía can be used to describe the content of your document and that's just about it. + + +\subsection{Ousía is not an editor} + +Ousía is not an editor application. Ousía documents are written in one of two markup languages $OSML and $OSXML which basically are plain text files. These files are then handed to an application called `ousia` that will parse them, check for errors and transform them to another format. + +There may be special editors that help you writing Ousía documents or that use the underlying program library `libousia` to provide a more convenient editing experience, but this doesn't change the bigger picture. + + +\subsection{Ousía does not replace Semantic Web technologies} + +\begin{figure#kizil_hauzen_bridge} + \img{../media/Kizil_Hauzen_Bridge_2013.jpg} + \meta{ + \title{Kizil Hauzen Bridge} + \location{Iran} + \date{2013} + } + \caption{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.} +\end{figure} + +\aside{Ousía makes the Semantic Web approachable for muggles.} + +It is possible (though unlikely, they are a rare species) that you are a Semantic Web expert: You know all three dialects of $OWL, write your love-letters in $RDF and transform vegetables into supper using $XSLT, just to devour it with your $SPARQL powers. + +In that case you'll very likely say: <<I have everything I need! Leave my standards alone! They are mine, all mine! My precious!>> + +Well, fear not! We're here 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. + + +\section{Semantic Markup unleashed} + +In this section we will skim over a few examples of how Ousía can be used, +giving you a quick impression. + + +\subsection{Express what you mean} + +One aspect of Ousía is its document markup language. It allows you to write the text of your document while attaching additonal information to the text using special commands. + +Let's assume you wanted to write a book (e.g. \href{https://www.gutenberg.org/ebooks/74}{The Adventures of Tom Sawyer} by Samuel Langhorne Clemens alias Mark Twain). You could start writing it down like this: + +\begin{code}[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. +\end{code} + +\begin{code} +\\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 instance name ("hashtag") + \\begin\{characters\} + \\def#huck\{ + \\name{ + \\first\{Huckleberry\} + \\first[short]\{Huck\} + \\last\{Finn\} + \} + \} + \\def#tom\{ + \\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. + ::\{huck\}Huck Finn:: is drawn from life; ::\{tom\}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} +\end{code} + +\end{article} |