SiSU

Description

Ralph Amissah

Endnotes

 ^1. This information was first placed on the web 12 November 2002; with predating material taken from <http://www.jus.uio.no/lm/lm.information/toc.html> part of a site started and developed since 1993. See document metadata section <http://www.jus.uio.no/sisu/SiSU/metadata.html> for information on this version. Dates related to the development of SiSU are mostly contained within the Chronology section of this document, e.g. <http://www.jus.uio.no/sisu/sisu_chronology>

 ^2. also chosen for the meaning of the Finnish term "sisu".

 ^3. objects include: headings, paragraphs, verse, tables, images, but not footnotes/endnotes which are numbered separately and tied to the object from which they are referenced.

 ^4. pdf via LaTeX or lout

 ^5. currently html (two forms of html presentation one based on css the other on tables), and PHP; potentially structured XML

 ^6. any SQL - currently PostgreSQL and sqlite (for portability, testing and development)

 ^7. previously called "text object numbering"

 ^8. SiSU Sabaki, release version. Pre-release version SiSU Scribe, and version prior to that SiSU nicknamed Scribbler. Pre-release versions go back several years. Both Scribbler and Scribe (still maintained) made system calls to SiSU's various parts, instead of using libraries.

 ^9. A little universe it may be, but semantic you may have a hard time getting away with, given the meaning the word has taken on with markup. On a document wide basis semantic information may be provided, which can be really useful, (and meaningful, especially) if you have a large document set, and use this with rss feeds or in an sql database etc. On a markup level, I have little inclination to add semantic markup formally beyond references, title, author [Dublin Core entities? addresses?] etc. Actually this deserves a bit of thought possibly use letter tags (including letter alias/synonyms for font faces) to create a small set of default semantic tags, with the possibility for per document adjustments. Will seek to permit XML entity tagging, within SiSU markup and have that ignored/removed by the parts of the program that have no use for it.

 ^10. "Sisu refers not to the courage of optimism, but to a concept of life that says, 'I may not win, but I will gladly give my life for what I believe.'" Aini Rajanen, Of Finnish Ways, 1981, p. 10.
<http://www.humanlanguages.com/finnishenglish/rlfs.htm>
"Every Finn has his own pet definition. To me, sisu means patience without passion. But there are many varieties of sisu. Sisu can be a sudden outburst or it can be the kind that lasts. A man can have both kinds. It is outside reason. It is something in the soul. It comes from oneself. For instance, it makes a soldier do things because he himself must, not because he has been told." Paavo Nurmi
<http://personalweb.smcvt.edu/tmatikainen/finnishtraditions.htm>

 ^11. <http://www.perl.org/>

 ^12. <http://www.ruby-lang.org/en/>

 ^13. <http://www.debian.org/>

 ^14. where explicit structure is provided through the use of tagging headings, it could be reduced (still) further, for example by reducing the number of characters used to identify heading levels; but in many cases even that information is not required as regular expressions can be used to extract the implicit structure.

 ^15. This proved to be the easiest way to develop syntax, changes could be made, or alternatives provided for the markup syntax whilst the intermediate markup syntax was largely held constant. There is actually an optional second intermediate markup format in YAML <http://www.yaml.org/>

 ^16. objects include: headings, paragraphs, verse, tables, images, but not footnotes/endnotes which are numbered separately and tied to the object from which they are referenced.

 ^17. where explicit structure is provided through the use of tagging headings, it could be reduced (still) further, for example by reducing the number of characters used to identify heading levels; but in many cases even that information is not required as regular expressions can be used to extract the implicit structure.

 ^18. <http://www.jus.uio.no/sisu/sample/markup/un_contracts_international_sale_of_goods_convention_1980.sst> output provided as example in the next section

 ^19. <http://www.jus.uio.no/sisu/sample/syntax/un_contracts_international_sale_of_goods_convention_1980.sst.html> as it would appear with syntax highlighting (by vim)

 ^20. seems there are several "smart ASCIIs" available, primarily for ascii to html conversion, that make this, and reasonable looking ascii their goal
<http://webseitz.fluxent.com/wiki/SmartAscii>
<http://daringfireball.net/projects/markdown/>
<http://www.textism.com/tools/textile/>

 ^21. These include richly laid out and linked html (table or css variants), PHP, LaTeX (from which pdf portrait and landscape documents are produced), texinfo (for info files etc.), and PostgreSQL and/or SQLite. And the opportunity to fairly easily build additional modules, such as XML. See the examples provided in this document.

 ^22. <http://www.jus.uio.no/sisu/sample/markup/un_contracts_international_sale_of_goods_convention_1980.sst>

 ^23. <http://www.jus.uio.no/sisu/sample/syntax/un_contracts_international_sale_of_goods_convention_1980.sst.html>

 ^24. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/toc.html>

 ^25. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/doc.html>

 ^26. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/landscape.pdf>

 ^27. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/portrait.pdf>

 ^28. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/plain.txt>

 ^29. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/sax.xml>

 ^30. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/dom.xml>

 ^31. <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/concordance.html>

 ^32. discontinued for the time being

 ^33. SiSU markup syntax, an incomplete summary: <http://www.jus.uio.no/sisu/sisu_markup_table/doc.html#h200306>
Visual check of elementary font face modifiers: bold bold emphasis italics underscore strikethrough ^superscript _subscript

 ^34. the program that generates the documents

 ^35. <http://www.jus.uio.no/sisu/SiSU/1.html#search>

 ^36. <http://dublincore.org/>

 ^37. <http://www.w3.org/RDF/>

 ^38. The previous way was directory associations for file output were set up in the configuration file. The present system is a more natural way to work requireing less configuration.

 ^39. from a version control system such as CVS

 ^40. The version control system must be run, so the version number is obtained, prior to the SiSU document generation, and subsequent posting of the document.

 ^41. e.g. LaTeX (professional document typesetting, easy conversion to pdf or Postscript), XML (in this case, structural representation), SQL (e.g. document set searches; representation of the constituent parts of documents based on their structure, headings, chapters, paragraphs as desired; control of use)

 ^42. CISG <http://www.jus.uio.no/lm/un_contracts_international_sale_of_goods_convention_1980/doc>
The Unidroit Contract Principles <http://www.jus.uio.no/lm/unidroit.contract.principles.1994/doc> or
The Autonomous Contract <http://www.jus.uio.no/lm/autonomous.contract.2000.amissah/doc>

 ^43. Scrolling is not however necessarily confined to full length documents as you will have to scroll to get to the bottom of any long segment (eg. chapter) of a segmented text.

 ^44. CISG <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980>
The Unidroit Principles <http://www.jus.uio.no/lm/unidroit.contract.principles.1994>
The Autonomous Contract <http://www.jus.uio.no/sisu/the.autonomous.contract.2000.amissah> or
WTA 1994 <http://www.jus.uio.no/lm/wta.1994>

 ^45. formatting possibility still exists in code tree but maintenance has been largely discontinuted.

 ^46. <http://www.mozilla.org/products/firefox/>

 ^47. <http://kazehakase.sourceforge.jp/>

 ^48. <http://www.konqueror.org/>

 ^49. <http://www.mozilla.org/>

 ^50. <http://www.microsoft.com/windows/ie/default.asp>

 ^51. <http://home.netscape.com/comprod/mirror/client_download.html>

 ^52. <http://www.opera.com/>

 ^53. <http://www.dillo.org/>

 ^54. <http://www.gnome.org/projects/epiphany/>

 ^55. <http://galeon.sourceforge.net/>

 ^56. <http://elinks.or.cz/>

 ^57. <http://links.twibright.com/>

 ^58. <http://w3m.sourceforge.net/>

 ^59. LaTeX and pdf features introduced 18^th June 2001, Landscape and portrait pdfs introduced 7^th October 2001., Lout is a more recent addition 22^th April 2003

 ^60. <http://www.adobe.com/products/acrobat/readstep2.html>

 ^61. <http://www.gnome.org/projects/evince/>

 ^62. <http://www.foolabs.com/xpdf/>

 ^63. <http://www.postgresql.org/>
<http://advocacy.postgresql.org/>
<http://en.wikipedia.org/wiki/Postgresql>

 ^64. <http://www.hwaci.com/sw/sqlite/>
<http://en.wikipedia.org/wiki/Sqlite>

 ^65. Relational database features retaining document structure and citation introduced 15^th July 2002

 ^66. <http://search.sisudoc.org>

 ^67. (which could be extended further with current back-end). As regards scaling of the database, it is as scalable as the database (here Postgresql) and hardware allow.

 ^68. of this feature when demonstrated to an IBM software innovations evaluator in 2004 he said to paraphrase: this could be of interest to us. We have large document management systems, you can search hundreds of thousands of documents and we can tell you which documents meet your search criteria, but there is no way we can tell you without opening each document where within each your matches are found.

 ^69. OCN are provided for HTML, XML, pdf ... though currently omitted in plain-text and opendocument format output

 ^70. Concordance/ WordMaps introduced 15^th August 2002

 ^71. <http://www.vim.org/>

Output generated by SiSU 0.59.1 2007-09-25 (2007w39/2)
SiSU Copyright ^© Ralph Amissah 1997, current 2007. All Rights Reserved.
SiSU is software for document structuring, publishing and search,
www.jus.uio.no/sisu and www.sisudoc.org
w3 since October 3 1993 ralph@amissah.com

SiSU using:
Standard SiSU markup syntax,
Standard SiSU meta-markup syntax, and the
Standard SiSU object citation numbering and system, (object/text positioning system)
Copyright ^© Ralph Amissah 1997, current 2007. All Rights Reserved.

SiSU is released under GPLv3 or later, <http://www.gnu.org/licenses/gpl.html>

SiSU, developed using Ruby on Debian/Gnu/Linux software infrastructure, with the usual GPL (or OSS) suspects.
Better - "performance, reliability, scalability, security & total cost of ownership" [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libre.
Get With the Future Way Better!