Silberengel @Silberengel - 29d
Making the order explicit will make editing and replacement interesting. Means they can't use functions they've developed for editing other replaceable events.
mleku @mleku - 29d
i think that because changing one section implies a change that propagates up the tree to the ToC is necessary for integrity checking, so the replacement of events for this also has propagating effects, can't be avoided
this is also why it's important to subdivide the trees so you can trace the side effects properly
Yeah, I'm planning on 30040 Bible |__ 30040 Introduction |__ 30040 New Testament |__ 30040 Gospels |__ 30040 Mark |__ 30040 Chapter 4 |__ 30041 Verse 4:11 |__ 30040 Old Testament |__ 30040 Apocrypha |__ 30040 Appendices Something like that. In the final version, the bottom 30041 content-level will be individual versions. In this training material, it's all lumped together in the 30041 chapters, but we need verse-events for #biblestr The idea is that we atomize large publications and then any npub can piece them back together, in various formats and orders. Of course, it's Nostr, so someone else is free to create a different tree out of the same content. They could even add commentary, at the various levels, or something. Just have to include an additional event, in between, and reorder (and, with this change) and *renumber* the 30040.
