aboutsummaryrefslogtreecommitdiffhomepage
path: root/test/test-abstraction-ssp-roundtrip.sh
diff options
context:
space:
mode:
authorRalph Amissah <ralph.amissah@gmail.com>2026-09-21 12:57:59 -0400
committerRalph Amissah <ralph.amissah@gmail.com>2026-09-22 15:11:02 -0400
commit1333ea2c3ba0a5cb13974e925978e50b97837f78 (patch)
tree449910b0a354520e8536910d833cffc5fb75ee7a /test/test-abstraction-ssp-roundtrip.sh
parenttest: ocn alignment check (diff)
ocda db: now carry markup source, conf & manifest
The database already carried the images, because without them no output can be produced. It now carries the markup as well, and with it the document's configuration and the manifest as the author wrote it. That is the difference between a serialised abstraction and a document source. An abstraction can be rendered but not re-parsed, and a reader who wants to correct a sentence needs the sentence as written. With these a pod can be written back out of the sqlite-file. Three new values in the existing role column, no schema change: the format stays 2.0. Source rows are named by their path within the pod, media/text/<lang>/<file>, and not by bare filename as images are. Every language of a document has a file of the same name, so bare names would collide under UNIQUE(role, name) and nine of ten would be dropped without a word. The path is also what a pod materialised from this database has to be told. Bytes stored as read with the digest over them, so that each row is checkable against the line source.digest was built from. Also build.spine_version, a file level row saying which spine wrote the file: not a property of the document, and the one thing a file cannot be asked for afterwards. The reader skips the build. prefix as it skips schema. and translation., or it would come back inside the document header and the round trip would differ. (assisted by Claude-Code)
Diffstat (limited to 'test/test-abstraction-ssp-roundtrip.sh')
0 files changed, 0 insertions, 0 deletions