summaryrefslogtreecommitdiffstats
path: root/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi
diff options
context:
space:
mode:
authorRalph Amissah <ralph@amissah.com>2013-05-10 02:21:33 +0000
committerRalph Amissah <ralph@amissah.com>2013-05-10 02:21:33 +0000
commit879a4e6cbe97721bbc6cd18b324524159b4807ef (patch)
treefd9cde1516e36545626ed06dee71edc4342b84d2 /data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi
parentv4: cgi script for sample search form, minor fixes (diff)
downloadsisu-879a4e6cbe97721bbc6cd18b324524159b4807ef.zip
sisu-879a4e6cbe97721bbc6cd18b324524159b4807ef.tar.xz
v5 dev branch opened (starts as copy of v4 stable branch); v3 branch closedsisu_4.1.0
* 5.0.0 dev opened * 4.1.0 stable * 3.* branch gone
Diffstat (limited to 'data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi')
-rw-r--r--data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi26
1 files changed, 26 insertions, 0 deletions
diff --git a/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi b/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi
new file mode 100644
index 0000000..3372bcd
--- /dev/null
+++ b/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi
@@ -0,0 +1,26 @@
+% SiSU 2.0
+
+@title: SiSU
+ :subtitle: How Does SiSU Work?
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? Description
+
+1~sisu_how How does sisu work?
+
+SiSU markup is fairly minimalistic, it consists of: a (largely optional) document header, made up of information about the document (such as when it was published, who authored it, and granting what rights) and any processing instructions; and markup within the substantive text of the document, which is related to document structure and typeface. SiSU must be able to discern the structure of a document, (text headings and their levels in relation to each other), either from information provided in the document header or from markup within the text (or from a combination of both). Processing is done against an abstraction of the document comprising of information on the document's structure and its objects,[2] which the program serializes (providing the object numbers) and which are assigned hash sum values based on their content. This abstraction of information about document structure, objects, (and hash sums), provides considerable flexibility in representing documents different ways and for different purposes (e.g. search, document layout, publishing, content certification, concordance etc.), and makes it possible to take advantage of some of the strengths of established ways of representing documents, (or indeed to create new ones).