<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sisudoc-ocda-lib/org, branch claude-main-prepare-fix</title>
<subtitle>SiSU Spine: tools</subtitle>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-ocda-lib/'/>
<entry>
<title>the abstraction as a library &amp; a discovered defect</title>
<updated>2026-10-21T22:04:01+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-09-25T20:34:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-ocda-lib/commit/?id=daba9810984b2924c28f5bedf838535f8711e669'/>
<id>daba9810984b2924c28f5bedf838535f8711e669</id>
<content type='text'>
The readers each read one serialisation and print.  A writer needs
neither: it needs the document. So the model and both loaders live
here, and a writer cannot tell which serialisation it was handed,
exactly as spine own writers cannot.

ocda.model imports nothing, which is the property that makes writers
possible: they depend on the model and on neither loader. The model
and the .ssp loader are the ssp-reader code, moved and renamed to the
level they belong to: the model is neither the .ssp nor the .ocda.db.
ocda.load_db is new, and returns the same value from sqlite that
load_ssp returns from text. ocda.load is the one place that decides
what a path is.

The claim is only true if the two loaders agree, so test/agree.d asks:
load a document both ways and compare the models object by object.

It found a real defect on its first run. Eight of thirty-six
disagreed, and the cause was the .ssp loader, not the formats: an
object whose first text line is blank lost it, the loader having
decided whether to start a new line by asking whether the accumulated
text was empty, which is a different question from whether a line has
been seen. Seven documents of the sample set have verse opening on a
blank line and every one of them was wrong.

Nothing else had caught it: the two .ssp readers were compared on
section counts, which the bug does not disturb.  It took loading one
document two ways and comparing the objects. Fixed here, and in
ssp-reader/dlang which carried the same code. All documents in the
markup sample set now agree.

(assisted by Claude-Code)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The readers each read one serialisation and print.  A writer needs
neither: it needs the document. So the model and both loaders live
here, and a writer cannot tell which serialisation it was handed,
exactly as spine own writers cannot.

ocda.model imports nothing, which is the property that makes writers
possible: they depend on the model and on neither loader. The model
and the .ssp loader are the ssp-reader code, moved and renamed to the
level they belong to: the model is neither the .ssp nor the .ocda.db.
ocda.load_db is new, and returns the same value from sqlite that
load_ssp returns from text. ocda.load is the one place that decides
what a path is.

The claim is only true if the two loaders agree, so test/agree.d asks:
load a document both ways and compare the models object by object.

It found a real defect on its first run. Eight of thirty-six
disagreed, and the cause was the .ssp loader, not the formats: an
object whose first text line is blank lost it, the loader having
decided whether to start a new line by asking whether the accumulated
text was empty, which is a different question from whether a line has
been seen. Seven documents of the sample set have verse opening on a
blank line and every one of them was wrong.

Nothing else had caught it: the two .ssp readers were compared on
section counts, which the bug does not disturb.  It took loading one
document two ways and comparing the objects. Fixed here, and in
ssp-reader/dlang which carried the same code. All documents in the
markup sample set now agree.

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