<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sisudoc-ssp-reader/gleam/src, branch main</title>
<subtitle>SiSU Spine: tools</subtitle>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/projects/sisudoc-ssp-reader/'/>
<entry>
<title>format 2.1: .ocn_range is one of the properties</title>
<updated>2026-09-29T18:09:17+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-29T18:09:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/projects/sisudoc-ssp-reader/commit/?id=8b3b995b6aff5c15ba31692fd29113db3c42517f'/>
<id>8b3b995b6aff5c15ba31692fd29113db3c42517f</id>
<content type='text'>
Format 2.1 adds .ocn_range, the first and last ocn a container holds,
emitted after .last_descendant: a poem, which now carries ocn 0 and
comes before its verses, is cited as the range of them. Both readers
now know it as the forty-third property, so --validate accepts a 2.1
file and --report-unknown does not list it. The validator's message
counts the list rather than naming a number.

Every document-language of the markup document samples written by
spine at 2.1 validates; neither reader uses the property, which
within a major version is conforming.

(assisted by Claude-Code)

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Format 2.1 adds .ocn_range, the first and last ocn a container holds,
emitted after .last_descendant: a poem, which now carries ocn 0 and
comes before its verses, is cited as the range of them. Both readers
now know it as the forty-third property, so --validate accepts a 2.1
file and --report-unknown does not list it. The validator's message
counts the list rather than naming a number.

Every document-language of the markup document samples written by
spine at 2.1 validates; neither reader uses the property, which
within a major version is conforming.

(assisted by Claude-Code)

</pre>
</div>
</content>
</entry>
<entry>
<title>a blank first text line was being lost</title>
<updated>2026-09-26T00:49:49+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-26T00:49:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/projects/sisudoc-ssp-reader/commit/?id=ead2f79ee41db99a292d763fe41f0613a74ef7b3'/>
<id>ead2f79ee41db99a292d763fe41f0613a74ef7b3</id>
<content type='text'>
An object whose first text line is blank lost it. The parser decided
whether to start a new line by asking whether the accumulated text
was empty, which is not the same question as whether a text line has
been seen: for an object opening on a blank line the first line left
the text empty and the second overwrote it rather than appending.

Seven documents of the markup document samples have verse opening on a
blank line, and in every one of them the blank was dropped, so the html,
the plain text and the JSONL chunks all began the verse a line early.
Spine's own text output has the blank line; this now matches.

Found by loading one document as .ssp and as .ocda.db and comparing
the two models object by object, which is what sisudoc-ocda-lib exists
to do. The comparison between the two .ssp readers had not caught it,
being on section counts, which the defect does not disturb.

Also: the repository is named sisudoc-ssp-reader, prefixed as every
repository of this project's own is (binary, package and module names
are unchanged), and the sources follow the specification directory's
name, sisudoc-abstraction-format. And the /+ ↓ +/ comment arrows in
ssp_parser.d, double-encoded by the in-place edit that applied the
fix, are restored; comment text only.

(assisted by Claude-Code)

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
An object whose first text line is blank lost it. The parser decided
whether to start a new line by asking whether the accumulated text
was empty, which is not the same question as whether a text line has
been seen: for an object opening on a blank line the first line left
the text empty and the second overwrote it rather than appending.

Seven documents of the markup document samples have verse opening on a
blank line, and in every one of them the blank was dropped, so the html,
the plain text and the JSONL chunks all began the verse a line early.
Spine's own text output has the blank line; this now matches.

Found by loading one document as .ssp and as .ocda.db and comparing
the two models object by object, which is what sisudoc-ocda-lib exists
to do. The comparison between the two .ssp readers had not caught it,
being on section counts, which the defect does not disturb.

Also: the repository is named sisudoc-ssp-reader, prefixed as every
repository of this project's own is (binary, package and module names
are unchanged), and the sources follow the specification directory's
name, sisudoc-abstraction-format. And the /+ ↓ +/ comment arrows in
ssp_parser.d, double-encoded by the in-place edit that applied the
fix, are restored; comment text only.

(assisted by Claude-Code)

</pre>
</div>
</content>
</entry>
<entry>
<title>--validate, and a second reader, in Gleam</title>
<updated>2026-09-24T20:33:53+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-24T20:33:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/projects/sisudoc-ssp-reader/commit/?id=bbe505c8d48e822c012c9820dfe93b83dc61bcab'/>
<id>bbe505c8d48e822c012c9820dfe93b83dc61bcab</id>
<content type='text'>
--validate: the specification, executed. A validator written from
ssp-format-specification.md and from nothing else, so that a file can
be held against the document rather than against an implementation.
Each finding names the specification section it comes from, so a
disagreement can be taken back to the text.

It checks the version banner and its major part, the file shape and
the order of the preamble blocks and the nine sections, the two
spaces of a preamble pair, the object declaration and its sixteen
kinds and eight heading levels, that a property is one of the 42 and
in the emitted order, that text lines carry their prefix, the ten
keys of doc_has, and that no line is of a shape the specification
does not define.

Every .ssp of the markup document samples validates clean. Five
classes of deliberate breakage are caught: an unknown major version, a
property that is not one of the 42, a property out of order, a kind
that is not one of the sixteen, and a block that is neither preamble
nor section. Writing it found two rules the specification implied
and did not state (repeated properties are consecutive; no property
follows the text), and both were written into it.

One repository, a reader per language. The readers are not separate
tools that share a name. They are the same specification implemented
more than once, and the interesting thing about them is that they
agree, so they are published as one thing with that claim at the top
of it. The D reader moves to dlang/; the Gleam reader arrives at
gleam/. The language directory is named for the language and not
for the tool: gleam refuses a hyphenated package name, so ssp-reader
cannot be a gleam package and must be ssp_reader.

A .gitignore for the repository, denying everything and whitelisting
what belongs, covering both languages.

Both build under nix, sandboxed and without network. There is no gleam
builder in nixpkgs and gleam build fetches from Hex, so the Gleam build
uses nix-gleam's builder, kept in gleam/nix-gleam/ (MIT), which fetches
each Hex package by the checksum manifest.toml already carries, with no
hash to maintain; the result is an escript wrapped with erlang. The D
reader depends on nothing beyond phobos, so --skip-registry=all is the
whole of what it takes: ldc by default, dmd available as ssp-reader-dmd
(given gcc14, GCC 15 having introduced nullptr in headers dmd's ImportC
does not yet parse).

(assisted by Claude-Code)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
--validate: the specification, executed. A validator written from
ssp-format-specification.md and from nothing else, so that a file can
be held against the document rather than against an implementation.
Each finding names the specification section it comes from, so a
disagreement can be taken back to the text.

It checks the version banner and its major part, the file shape and
the order of the preamble blocks and the nine sections, the two
spaces of a preamble pair, the object declaration and its sixteen
kinds and eight heading levels, that a property is one of the 42 and
in the emitted order, that text lines carry their prefix, the ten
keys of doc_has, and that no line is of a shape the specification
does not define.

Every .ssp of the markup document samples validates clean. Five
classes of deliberate breakage are caught: an unknown major version, a
property that is not one of the 42, a property out of order, a kind
that is not one of the sixteen, and a block that is neither preamble
nor section. Writing it found two rules the specification implied
and did not state (repeated properties are consecutive; no property
follows the text), and both were written into it.

One repository, a reader per language. The readers are not separate
tools that share a name. They are the same specification implemented
more than once, and the interesting thing about them is that they
agree, so they are published as one thing with that claim at the top
of it. The D reader moves to dlang/; the Gleam reader arrives at
gleam/. The language directory is named for the language and not
for the tool: gleam refuses a hyphenated package name, so ssp-reader
cannot be a gleam package and must be ssp_reader.

A .gitignore for the repository, denying everything and whitelisting
what belongs, covering both languages.

Both build under nix, sandboxed and without network. There is no gleam
builder in nixpkgs and gleam build fetches from Hex, so the Gleam build
uses nix-gleam's builder, kept in gleam/nix-gleam/ (MIT), which fetches
each Hex package by the checksum manifest.toml already carries, with no
hash to maintain; the result is an escript wrapped with erlang. The D
reader depends on nothing beyond phobos, so --skip-registry=all is the
whole of what it takes: ldc by default, dmd available as ssp-reader-dmd
(given gcc14, GCC 15 having introduced nullptr in headers dmd's ImportC
does not yet parse).

(assisted by Claude-Code)
</pre>
</div>
</content>
</entry>
<entry>
<title>commencement: a reader for the .ssp</title>
<updated>2026-04-22T20:30:13+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-04-22T20:30:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/projects/sisudoc-ssp-reader/commit/?id=b7d9c3b1c01573ce6499e1b031556c3863df57e7'/>
<id>b7d9c3b1c01573ce6499e1b031556c3863df57e7</id>
<content type='text'>
Work on a reader for spine's .ssp began on this date: a parser of the
text form and outputs from it (a heading tree, html), to show that the
abstraction carries what is needed to present a document without the
markup it was made from.

The reader's versions for the formats before 2.0 are not carried. The
reader as published begins at format 2.0, in the next commit, dated
when it reached 2.0.

(assisted by Claude-Code)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Work on a reader for spine's .ssp began on this date: a parser of the
text form and outputs from it (a heading tree, html), to show that the
abstraction carries what is needed to present a document without the
markup it was made from.

The reader's versions for the formats before 2.0 are not carried. The
reader as published begins at format 2.0, in the next commit, dated
when it reached 2.0.

(assisted by Claude-Code)
</pre>
</div>
</content>
</entry>
</feed>
