aboutsummaryrefslogtreecommitdiffhomepage
path: root/markup
diff options
context:
space:
mode:
Diffstat (limited to 'markup')
-rw-r--r--markup/sisudoc-spine-bespoke-output/html/homepage.index.html23
1 files changed, 14 insertions, 9 deletions
diff --git a/markup/sisudoc-spine-bespoke-output/html/homepage.index.html b/markup/sisudoc-spine-bespoke-output/html/homepage.index.html
index 601cba8..c5ba045 100644
--- a/markup/sisudoc-spine-bespoke-output/html/homepage.index.html
+++ b/markup/sisudoc-spine-bespoke-output/html/homepage.index.html
@@ -15,9 +15,9 @@ multiple outputs &amp; search</h1>
SiSU parses a lightweight-markup source into an abstract document object
model. Every substantive element (paragraph, heading, table, verse, image)
becomes a typed object carrying its position in the document's sequence
-and hierarchy, and a stable citation number. From that single abstraction
-it emits multiple output formats - HTML (segmented and scroll), EPUB3,
-LaTeX (then PDF via xelatex), ODT, plain text, and an SQLite full-text
+and in its heading hierarchy, and a stable citation number. From that single
+abstraction it emits multiple output formats - HTML (segmented and scroll),
+EPUB3, LaTeX (then PDF via xelatex), ODT, plain text, and an SQLite full-text
search database. Each object's number stays stable across every output
format and across translations of the same document.
</p>
@@ -29,12 +29,17 @@ output</b>.
<p>
<b>Object-Centric Document Abstraction</b>. The abstraction stage builds an
-in-memory object model: every paragraph, heading, table, footnote and so on is a
-numbered object that carries its own parent / sibling / type metadata, known as
-OCN (Object Citation Numbering). Every output format is generated from that
-single abstraction, so all formats share the same object identifiers. The
-abstraction can also be written out as a human-readable, PEG-parsable text
-format (<code>.ssp</code>) that other tools can consume directly.
+in-memory object model along two bound dimensions: <b>document structure</b>
+(the heading hierarchy - title, section, part, chapter, sub-headings) and
+<b>document objects</b> (every paragraph, heading, table, footnote and so on,
+as a typed unit). The two are mapped to each other - each object knows its
+place in the heading hierarchy, and each structural node knows the objects
+that belong to it. Substantive objects also carry a stable citation number
+(OCN, Object Citation Numbering). Every output format is generated from this
+single abstraction, so all formats share the same object identifiers and the
+same structural shape. The abstraction can also be written out as a
+human-readable, PEG-parsable text format (<code>.ssp</code>) that other tools
+can consume directly.
</p>
<h2>ℹ - How this differs from a typical "markup &#8594; HTML"