<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sisudoc-abstraction-format/claude-org/ocda_specification.org, branch claude-spec-matchup</title>
<subtitle>SiSU Spine: specs</subtitle>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/'/>
<entry>
<title>2.1.1: the patch part of a release number; the readers named</title>
<updated>2026-10-13T20:54:02+00:00</updated>
<author>
<name>Ralph Amissah</name>
<email>ralph.amissah@gmail.com</email>
</author>
<published>2026-10-13T20:54:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sisudoc.org/sisudoc-abstraction-format/commit/?id=bb28568715e9feabfd7ee357d4802dd0d251bbac'/>
<id>bb28568715e9feabfd7ee357d4802dd0d251bbac</id>
<content type='text'>
A release is numbered major.minor.patch. major.minor is the format,
and is shared by the specification and the programs that implement
it; the patch is each one's own. A patch changes nothing a file can
contain - a correction or clarification of this text, or a fix in a
program - so a file declares major.minor only, as it always has, and
spine and every reader are unaffected.

Section 2.1 of the .ssp specification says so, beside the rule for
the minor and major parts, and a new 2.3 lists the releases of this
text: 2.0.0 the model and the .ssp, 2.0.1 the kinds, types, levels,
make block and markers, 2.0.2 the .ocda.db and two rules a validator
found, 2.0.3 the derived values, 2.1.0 .ocn_range and the editor's
notes, 2.1.1 this. The README's version section says it in brief.

The README's related projects name the first readers,
sisudoc-ssp-reader and sisudoc-ocda-db-reader, published frozen as
the record of readers written from this specification alone, their
work now done by ocda-read in sisudoc-ocda-lib.

claude-org/: ocda_specification.org with the same changes, so that it
tangles every document exactly as committed, and the version and
header file with its two local git+file blocks taken out; proposed
replacements for their org/ counterparts.

(assisted by Claude-Code)

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A release is numbered major.minor.patch. major.minor is the format,
and is shared by the specification and the programs that implement
it; the patch is each one's own. A patch changes nothing a file can
contain - a correction or clarification of this text, or a fix in a
program - so a file declares major.minor only, as it always has, and
spine and every reader are unaffected.

Section 2.1 of the .ssp specification says so, beside the rule for
the minor and major parts, and a new 2.3 lists the releases of this
text: 2.0.0 the model and the .ssp, 2.0.1 the kinds, types, levels,
make block and markers, 2.0.2 the .ocda.db and two rules a validator
found, 2.0.3 the derived values, 2.1.0 .ocn_range and the editor's
notes, 2.1.1 this. The README's version section says it in brief.

The README's related projects name the first readers,
sisudoc-ssp-reader and sisudoc-ocda-db-reader, published frozen as
the record of readers written from this specification alone, their
work now done by ocda-read in sisudoc-ocda-lib.

claude-org/: ocda_specification.org with the same changes, so that it
tangles every document exactly as committed, and the version and
header file with its two local git+file blocks taken out; proposed
replacements for their org/ counterparts.

(assisted by Claude-Code)

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
