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
262
263
264
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>SiSU information Structuring Universe - Structured
information, Serialized Units - software for electronic texts,
documents, books, digital libraries in plaintext, html, xhtml, XML,
ODF (OpenDocument), LaTeX, pdf, SQL (PostgreSQL and SQLite), and
for search</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="dc.title" content=
"SiSU information Structuring Universe, Structured information Serialised Units, 2007" />
<meta name="dc.creator" content="Ralph Amissah" />
<meta name="dc.subject" content=
"ebook, publishing, pdf, LaTeX, XML, ODF, SQL, postgresql, sqlite, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search, digital library" />
<meta name="dc.publisher" content=
"SiSU http://www.jus.uio.no/sisu" />
<meta name="dc.language" content="en" />
<meta name="dc.rights" content="Copyright Ralph Amissah" />
<meta name="generator" content="SiSU 0.48.9 of 2007w01/1 (20070101) (n*x and Ruby!)" />
<link rel="generator" href="http://www.jus.uio.no/sisu/SiSU" />
<link rel="stylesheet" href="./_sisu/css/html.css" type="text/css" />
<link rel="shortcut icon" href="./_sisu/image/rb7.ico" />
</head>
<body>
<div id="top_band">
<p class="top_band_image">
<a href="http://www.jus.uio.no/sisu/SiSU" target="_top" >
<img border="0" src="./_sisu/image/sisu.png" alt="SiSU >>">
</a>
</p>
<h1 class="top_band">
SiSU information Structuring Universe
</h1>
<h2 class="top_band_tiny">
Structured information, Serialized Units
</h2>
<h2 class="top_band_tiny">
software for electronic texts, document collections, books, digital libraries, and search
</h2>
<h2 class="top_band_tiny">
with "atomic search" and text positioning system (shared text citation numbering: "<i>ocn</i>")
</h2>
<h2 class="top_band_tiny">
outputs include: plaintext, html, xhtml, XML, ODF (OpenDocument), LaTeX, pdf, SQL (PostgreSQL and SQLite)
</h2>
</div>
<div id="column_left">
<p class="bold">
<a href="http://www.jus.uio.no/sisu/SiSU" target="_top" >
SiSU
</a>
</p>
<p class="tiny">
---
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU/1.html#summary" target="_top" >
What does SiSU do? Summary
</a>
</p>
<p class="tiny">
---
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU/2.html" target="_top" >
Book Samples and Markup Examples
</a>
</p>
<p class="tiny">
---
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU/1.html#ocn" target="_top" >
Object Citation Numbering - <i>ocn</i>
</a>
</p>
<p class="tiny">(a text positioning system)</p>
<p class="tiny">
---
</p>
<p class="small">
<p>
<a href="http://www.jus.uio.no/sisu/SiSU/1.html#search" target="_top" >
Search - "<i>Atomic</i>"
</a>
</p>
<p class="tiny">
Of interest is the ease of streaming documents to a relational database, at an object (roughly paragraph) level and the potential for increased precision in the presentation of matches that results thereby. The ability to serialise html, LaTeX, XML, SQL, (whatever) is also inherent in / incidental to the design. For a description see the
<a href="http://www.jus.uio.no/sisu/sisu_provisional_patent_application_200408" target="_top" >
abandoned U.S. provisional patent application
</a>
</p>
<p class="tiny">
---
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU/download.html" target="_top" >
<b>Download</b>
</a>
</p>
<p class="tiny">
---
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU/changelog.html" target="_top" >
Changelog
</a>
</p>
<p class="tiny">
---
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU/license.html" target="_top" >
License
</a>
</p>
<p class="tiny">
Gnu / Linux / Unix
</p>
<p class="tiny">
=============
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/man" target="_top" >
sisu man pages
</a>
</p>
<p class="tiny">
---
</p>
<p class="tiny">
document preparation can be on any platform, in any editor:
(syntax highlight support currently for: vim, kate, write, gedit, diakonos)
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/syntax_highlight" target="_top" >
Syntax highlighting
</a>
</p>
<p class="tiny">
=============
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/SiSU" target="_top" >
* Composite document
</a>
</p>
<p class="tiny">
the composite document is a superset of the following documents:
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_description" target="_top" >
SiSU description
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_examples" target="_top" >
SiSU examples
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_chronology" target="_top" >
SiSU chronology
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_technical_info" target="_top" >
SiSU technical
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_faq" target="_top" >
SiSU FAQ
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_download" target="_top" >
SiSU download
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_changelog" target="_top" >
SiSU changelog
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_license" target="_top" >
SiSU license
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_standard" target="_top" >
SiSU standard
</a>
</p>
<p class="small">
<a href="http://www.jus.uio.no/sisu/sisu_provisional_patent_application_200408" target="_top" >
SiSU abandoned provisional patent
</a>
</p>
<p class="tiny">
Note: the placement of SiSU documents on the Net predate the release of SiSU.
</p>
</div>
<div id="column_center">
<p class="bold">
For less markup than the most elementary HTML you can have so much more.
</p>
<p><a href="http://www.jus.uio.no/sisu/SiSU" target="_top" ><b>SiSU</b> - Structured information, Serialized Units</a> for Electronic Documents, is an information structuring, transforming and publishing framework with the following features:</p>
<p><b>(i)</b> markup syntax: (a) simpler than html, (b) mnemonic, influenced by mail/messaging/wiki markup practices, (c) human readable, and easily writable,</p>
<p><b>(ii)</b> (a) minimal markup requirement, (b) single file marked up for multiple outputs,</p>
<p><b>(iii)</b> (a) multiple outputs include amongst others: html; pdf via LaTeX; (structured) XML; ODF (OpenDocument); sql - currently PostgreSQL (and SQLite); ascii, (also texinfo), (b) takes advantage of the strengths implicit in these very different output types, (e.g. pdfs produced using typsetting of LaTeX, databases populated with documents at an individual object/paragraph level, with implications for search possibilities...)</p>
<p><b>(iv)</b> provides a common object positioning and citation system for all outputs, which is human relevant and machine usable: <u><i>object citation numbering</i></u>, all objects (paragraphs, headings, verse, tables etc. and images) are numbered identically, for citation purposes, in all outputs (html, pdf, sql etc.),</p>
<p><b>(v)</b> use of Dublin Core and other meta-tags to permit the addition of some semantic information on documents, and making easy integration of rdf/rss feeds etc.,</p>
<p><b>(vi)</b> creates organised directory/file structure for (file-system) output, easily mapped with its clearly defined structure, with all text objects numbered, you know in advance where in each document output type, a bit of text will be found (eg. from an sql search, you know where to go to find the prepared html output or pdf etc.)... there is more; easy directory management and document associations, the document preparation (sub-)directory may be used to determine output (sub-)directory, the skin used, and the sql database used,</p>
<p><b>(vii)</b> search of document sets, at object/paragraph level, the relational database retains information on the document structure, and citation numbering makes it possible for example to present search matches as an index of documents and locations within the document where the match is found,</p>
<p><b>(viii)</b> "Concordance file" wordmap, consisting of all the words in a document and their (text/ object) locations within the text, (and the possibility of adding vocabularies),</p>
<p><b>(ix)</b> document content certification and comparison considerations: (a) the document and each object within it stamped with an md5 hash making it possible to easily check or guarantee that the substantive content of a document is unchanged, (b) version control, documents integrated with time based source control system, default RCS or CVS with use of $Id$ tag, which SiSU checks
<p><b>(x)</b> SiSU's minimalist markup makes for meaningful "diffing" of the substantive content of markup-files,</p>
<p><b>(xi)</b> easily skinnable, document appearance on a project/site wide, directory wide, or document instance level easily controlled/changed,</p>
<p><b>(xii)</b> in many cases a regular expression may be used (once in the document header) to define all or part of a documents structure obviating or reducing the need to provide structural markup within the document,</p>
<p><b>(xiii)</b> is a batch processor for handling large document sets, ... though once generated they need not be re-generated, unless changes are made to the desired presentation of a particular output type,</p>
<p><b>(xiv)</b> possible to pre-process, which permits: the easy creation of standard form documents, and templates/term-sheets, or; building of composite documents (master documents) from other sisu marked up documents, or marked up parts, i.e. import documents or parts of text into a main document should this be desired</p>
<p><b>(xv)</b> future proofing, a framework for adding further capability or updating existing capability as required: (a) modular, (thanks in no small part to Ruby) another output format required, write another module....(b) easy to update output formats (eg html, xhtml, latex/pdf produced can be updated in program and run against whole document set), (c) easy to add, modify, or have alternative syntax rules for input, should you need to,</p>
<p><b>(xvi)</b> scalability, dependent on your file-system (in my case Reiserfs) and on the relational database used (currently Postgresql and SQLite), and your hardware,</p>
<p><b>(xvii)</b> only marked up files need be backed up, to secure the larger document set produced,</p>
<p><b>(xviii)</b> document management,</p>
<p><b>(xix)</b> use your favourite editor, syntax highlighting files for markup, primarily (g)vim so far,</p>
<p><b>(xx)</b> remote operations: (a) run SiSU on a remote server, (having prepared sisu markup documents locally or on that server, i.e. this solution where sisu is installed on the remote server, would work whatever type of machine you chose to prepare your markup documents on), (b) alternatively, (assuming sisu is available to you locally but not installed on the remote server) configure sisu to securely copy (scp) its output to your remote host and run sisu locally, (c) request a remotely located sisu markup file and process it locally by identifying it by its' url.</p>
<br />
<p class="small">
More information on <a href="http://www.jus.uio.no/sisu/SiSU/"><b>SiSU</b></a> provided at <a href="http://www.jus.uio.no/sisu/SiSU/">www.jus.uio.no/sisu/SiSU</a></p>
</div>
<div id="column_right">
<p class="small">
More information on <a href="http://www.jus.uio.no/sisu/SiSU/"><b>SiSU</b></a> provided at:
<a href="http://www.jus.uio.no/sisu/SiSU/">
www.jus.uio.no/sisu/SiSU
</a>
<p class="tiny">
SiSU was developed in relation to legal documents, and is strong across a wide variety of texts (law, literature...(humanities, law and part of the social sciences)). SiSU handles images but is not suitable for formulae/ statistics, or for technical writing at this time.</p>
<p class="tiny">
SiSU has been developed and has been in use for several years. Requirements to cover a wide range of documents within its use domain have been explored.</p>
<p class="tiny">
Some modules are more mature than others, the most mature being Html and LaTeX / pdf. PostgreSQL and search functions are useable and together with <i>ocn</i> unique (to the best of my knowledge). The XML output document set is "well formed" but largely proof of concept, as is the OpenDocument output which is a limited SiSU feature set (SiSU is interested in a very limited ODF feature set).</p>
<p class="small">
<a href="mailto://ralph@amissah.com">
ralph@amissah.com
</a>
</p>
<p class="small">
<a href="mailto://ralph.amissah@gmail.com">
ralph.amissah@gmail.com
</a>
</p>
<p class="small">
2007
</p>
<p class="tiny">
w3 since October 3 1993
</p>
</div>
</body>
</html>
|
