<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sisudoc-abstraction-format/.gitignore, branch main-prepare</title>
<subtitle>SiSU Spine: specs</subtitle>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/'/>
<entry>
<title>sisudoc-abstraction-format 2.0: ocda-model &amp; .ssp</title>
<updated>2026-10-03T17:59:49+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-04-19T00:28:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=346a4c36f53fb8a60aa63b19e149938b6bc406d9'/>
<id>346a4c36f53fb8a60aa63b19e149938b6bc406d9</id>
<content type='text'>
In an age of malleable, replaceable, improvable text, we continue to
seek to represent set text in a fixed, determinate way.

This is an effort, using an LLM (Anthropic's Claude Code), to extract
and state the specification of the document abstraction of the
program spine:

- spine can write its document abstraction as a .ssp file, a
  PEG-parsable serialisation from which other forms of it, such as
  the sqlite .ocda.db, can be derived
  https://git.sisudoc.org/sisudoc-spine
  git clone --depth=1 git://git.sisudoc.org/software/sisudoc-spine

- this repository states the specification of that abstraction, as
  the .ssp writes it, in enough detail and with enough precision for
  the abstraction to be read and written independently
  git clone --depth=1 git://git.sisudoc.org/specs/sisudoc-abstraction-format

- the claim is tested separately: with readers and writers built from
  the specification alone, with no other knowledge of the format, that
  read and write the abstraction exactly

The specification is derived from the spine emitter,
sisudoc/ocda/abstraction/ssp.d, whose sspObjectRecord is the single
definition of what an object looks like, and checked against the
document markup sample set. Where the two differ the emitter is
normative and the specification is wrong; the specification says so.

Three documents, so the model is described once rather than in each
format specification:

  ocda-model.md                    the model: what an object is, the
                                   citation number, structure,
                                   sections, segments, digests.  The
                                   part both serialisations share
  ssp-format-specification.md      the model written as text
  ocda-db-format-specification.md  the model written as sqlite, to
                                   come

The naming follows the three levels: ocda names the model,
abstraction names the pipeline stage, and .ssp and .ocda.db name the
two serialisations. A thing is named for the level it belongs to,
which is why this file is ssp-format-specification.md and not
ocda-format-specification.md: it specifies one serialisation, not the
model.

The specification states the version and the policy that governs it,
and separates conformance into what a reader must do, should do, and
what a writer must do. The single "should" is that a reader should
report what it ignored: without it, silence cannot be told from
understanding.

Both worked examples regenerated from spine 0.25.0.  The excerpt
carries one complete object embedding an image, so the .image record
and the image marker in the object text can be read against each
other.

The name .ssp is recorded: it belongs to the .sst, .ssm, .ssi family
and stands loosely for sisu peg or sisu parsable, .ssa for sisu
abstraction having been thought taken by other projects.

README.md identifies the repository as a specification, not a
program, summarises what a .ssp is, gives its line types at a glance,
and points to ssp-format-specification.md and the two examples.
org/ocda_specification.org is the literate source the documents are
tangled from.

2026-09-22

(assisted by Claude-Code)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In an age of malleable, replaceable, improvable text, we continue to
seek to represent set text in a fixed, determinate way.

This is an effort, using an LLM (Anthropic's Claude Code), to extract
and state the specification of the document abstraction of the
program spine:

- spine can write its document abstraction as a .ssp file, a
  PEG-parsable serialisation from which other forms of it, such as
  the sqlite .ocda.db, can be derived
  https://git.sisudoc.org/sisudoc-spine
  git clone --depth=1 git://git.sisudoc.org/software/sisudoc-spine

- this repository states the specification of that abstraction, as
  the .ssp writes it, in enough detail and with enough precision for
  the abstraction to be read and written independently
  git clone --depth=1 git://git.sisudoc.org/specs/sisudoc-abstraction-format

- the claim is tested separately: with readers and writers built from
  the specification alone, with no other knowledge of the format, that
  read and write the abstraction exactly

The specification is derived from the spine emitter,
sisudoc/ocda/abstraction/ssp.d, whose sspObjectRecord is the single
definition of what an object looks like, and checked against the
document markup sample set. Where the two differ the emitter is
normative and the specification is wrong; the specification says so.

Three documents, so the model is described once rather than in each
format specification:

  ocda-model.md                    the model: what an object is, the
                                   citation number, structure,
                                   sections, segments, digests.  The
                                   part both serialisations share
  ssp-format-specification.md      the model written as text
  ocda-db-format-specification.md  the model written as sqlite, to
                                   come

The naming follows the three levels: ocda names the model,
abstraction names the pipeline stage, and .ssp and .ocda.db name the
two serialisations. A thing is named for the level it belongs to,
which is why this file is ssp-format-specification.md and not
ocda-format-specification.md: it specifies one serialisation, not the
model.

The specification states the version and the policy that governs it,
and separates conformance into what a reader must do, should do, and
what a writer must do. The single "should" is that a reader should
report what it ignored: without it, silence cannot be told from
understanding.

Both worked examples regenerated from spine 0.25.0.  The excerpt
carries one complete object embedding an image, so the .image record
and the image marker in the object text can be read against each
other.

The name .ssp is recorded: it belongs to the .sst, .ssm, .ssi family
and stands loosely for sisu peg or sisu parsable, .ssa for sisu
abstraction having been thought taken by other projects.

README.md identifies the repository as a specification, not a
program, summarises what a .ssp is, gives its line types at a glance,
and points to ssp-format-specification.md and the two examples.
org/ocda_specification.org is the literate source the documents are
tangled from.

2026-09-22

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