diff options
| -rw-r--r-- | flake.lock | 14 | ||||
| -rw-r--r-- | markup/sisudoc-spine-bespoke-output/html/homepage.index.html | 23 | ||||
| -rw-r--r-- | org/spine-bespoke-output-homepage-html.org | 23 |
3 files changed, 35 insertions, 25 deletions
@@ -22,11 +22,11 @@ }, "nixpkgs": { "locked": { - "lastModified": 1779414690, - "narHash": "sha256-gOTcX/9MZVMUE0Xvb4IEcv+0TQJkZFNEnL757ljU360=", + "lastModified": 1779877693, + "narHash": "sha256-NOF9NAREhxr50bbBfVcVOq+ArCMSoe8dP79Pk2uyARk=", "owner": "NixOS", "repo": "nixpkgs", - "rev": "6dedf69f94d03cbe7bdde106f2d4c23ae2a853bf", + "rev": "4100e830e085863741bc69b156ec4ccd53ab5be0", "type": "github" }, "original": { @@ -50,11 +50,11 @@ ] }, "locked": { - "lastModified": 1779478968, - "narHash": "sha256-ypwRe6EWHkHrmUpoH2am7HPGQ0d81ThlwP5eI89+CPM=", + "lastModified": 1779726098, + "narHash": "sha256-64JZ1RMAx+LuGOp0dQgolCU8++GJJGsXj4q+LR+5WII=", "ref": "refs/heads/main", - "rev": "2cb20ea0436e4f0180716ff8440a686d5347ee8f", - "revCount": 744, + "rev": "6ce2e8efb3a81b724840c06d62d5c8379992f7f0", + "revCount": 752, "type": "git", "url": "git://git.sisudoc.org/software/sisudoc-spine" }, 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 & 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 → HTML" diff --git a/org/spine-bespoke-output-homepage-html.org b/org/spine-bespoke-output-homepage-html.org index 7baa474..8e9c5ea 100644 --- a/org/spine-bespoke-output-homepage-html.org +++ b/org/spine-bespoke-output-homepage-html.org @@ -36,9 +36,9 @@ multiple outputs & 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> @@ -50,12 +50,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 → HTML" |