From 597d73db60679b8ed13524f9dd3832bb7476038f Mon Sep 17 00:00:00 2001 From: Ralph Amissah Date: Tue, 29 Sep 2026 14:07:32 -0400 Subject: model 2.1: ocn_range, the verses a poem holds The format now states, for a container, the first and last ocn of what it holds: .ocn_range in the .ssp, ocn_range_first and ocn_range_last in the .ocda.db. A poem is the one container, and since 2.1 it carries ocn 0 and comes before its verses. Both fields in the model, read by both loaders, in both languages, and written by the dump. A 2.0 database has neither column, so each loader asks sqlite whether it is there and reads a 2.0 file as having no ranges, which is what 2.0 meant; checked on a published 2.0 database, D and Gleam giving the same dump. Over the 36 document-languages written by spine at 2.1, the four dumps (D and Gleam, .ssp and .ocda.db) are byte identical, 36 of 36. (assisted by Claude-Code) --- dlang/src/ocda/model.d | 2 ++ 1 file changed, 2 insertions(+) (limited to 'dlang/src/ocda/model.d') diff --git a/dlang/src/ocda/model.d b/dlang/src/ocda/model.d index 403502a..6c8fc37 100644 --- a/dlang/src/ocda/model.d +++ b/dlang/src/ocda/model.d @@ -27,6 +27,8 @@ struct OcdaObject { string[] anchor_tags; // named targets the markup placed on this object int parent_ocn; int last_descendant_ocn; + int ocn_range_first;// a container (a poem): the first and last + int ocn_range_last; // ocn of what it holds; 0 otherwise (2.1) int[] children; // direct child heading OCNs int[] ancestors; // markedup_ancestors[8] bool dummy_heading; -- cgit v1.2.3