Document Revision History¶
Revision register — instantiates Identity-Bounded Change
Preserves a document's identity across drafts and editions by recording every revision, redline, and approval in order, so any past state is recoverable and every change is attributable.
A document that anyone keeps working on raises a quiet question: after all the drafts, redlines, and re-releases, is the thing in front of me still the same document, and how did it get from what it was to what it is? Document Revision History answers by keeping the ordered trail of a single document's successive textual states — each draft and edition recorded with the diff to the state before it, and each change stamped with who made or approved it. Its defining move is to treat the document as one continuing versioned subject whose editions are states of the same work, and to make the transitions between those states legible and reversible: any earlier version can be reconstructed, and any word can be traced to the revision where it entered and the person who signed off on it. It is a history of what the text was, not of where the document lives or who is bound by it.
Example¶
A textbook manuscript moves through the usual mill. The author submits a first draft; the developmental editor returns it thick with tracked changes; the author accepts some, rejects others, and adds two sections; a copyedit pass follows, then proofs, then the first edition ships. Two years later a second edition substantially rewrites three chapters and adds a fourth.
The revision history holds all of it: each draft numbered, the redline between every pair of states, and the name against each accepted change. When a reviewer wants to know what actually changed between the first and second editions, they diff the two and see exactly the rewritten passages. When a disputed claim surfaces, it is traced back to the draft where it first appeared and the editor who approved it. And the whole ordered chain is what lets everyone treat the second edition as the same book, continued — right up to the edge case where a rewrite is so total that it has quietly become a different work wearing the old title.
How it works¶
- Record each state and its diff. Every draft or edition is snapshotted, and the change from the prior state is captured as a redline, so revisions are shown, not just asserted.
- Attribute and order every change. Each revision carries an author or approver and a timestamp, and states are numbered so any of them is addressable and the sequence is unambiguous.
- Keep history append-only and recoverable. Past states are never overwritten; any earlier version can be reconstituted exactly.
Tuning parameters¶
- Revision granularity — whether history is kept per keystroke, per saved draft, or per released edition. Fine granularity reconstructs everything but buries the meaningful changes in noise; coarse granularity is readable but loses detail.
- Diff unit — character- and word-level redlines versus paragraph or section summaries. Fine diffs show precisely what changed; summaries stay legible on large documents.
- Attribution depth — author only, or author plus approver plus rationale. Deeper attribution supports later disputes but adds ceremony to every edit.
- Retention and pruning — keep every draft forever, or prune to approved editions. Full history aids audit; pruning saves space and reduces the surface of stale, quotable drafts.
- Edition threshold — how much change promotes a revision to a new edition, and how much promotes it to a new work entirely.
When it helps, and when it misleads¶
Its strength is that it makes a document's evolution transparent and reversible: every state recoverable, every change attributable, every edition diffable against the last. That is what lets contributors, reviewers, and auditors trust that the current text is a continuation of a known history rather than an unaccountable rewrite.
Its central trap is mistaking a version label for an identity guarantee — reading "it's the third edition" as proof that it is still the same work, when a wholesale rewrite may have produced a different work under the inherited title. Publishing itself already grades change by label (an impression reprints the same setting; a new edition signals substantive revision), but even a "new edition" can cross the line into a new work[1], and the version number alone cannot tell you which side of that line you are on. The related misuse is editing the history itself — rewriting the log to make the past look like the present, which destroys the very reconstructability that gives the record its value. The discipline is an append-only history plus an explicit judgment, kept separate from the numbering, about when an edition has become a new work.
How it implements the components¶
versioned_subject— treats the document as one continuing subject whose numbered drafts and editions are its successive states rather than separate objects.change_log— records the redline for each revision: exactly what text changed from the prior state, and by whom.version_identifier— numbers every draft and edition so any past state is addressable and the sequence is ordered.
It does NOT bind or resolve the document's permanent identifier (persistent_identity_binding, source_of_truth_reference) — that is Persistent Identifier Resolver; and it does NOT manage concurrent branches and their merges (branch_or_variant_marker) — that belongs to Version Control System.
Related¶
- Instantiates: Identity-Bounded Change — keeps a document one continuing work across its drafts and editions by recording the ordered chain of textual states.
- Sibling mechanisms: Version Control System · Persistent Identifier Resolver · Legal Amendment Record · Policy Amendment Register · Split/Merge Change Log · Event-Sourced Entity History · Chain-of-Custody Record · Conservation Treatment Record · Identity Continuity Review · Replacement or Fork Decision Record
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Document Revision History operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it preserves a document's identity across drafts and editions by recording every revision, redline, and approval in order, so any past state is recoverable and every change is attributable.
Independent corroboration: The frozen evidence defines Document Revision History as 'Preserves a document's identity across drafts and editions by recording every revision, redline, and approval in order, so any past state is recoverable and every change is attributable', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Bibliographic and records practice cohered editions, versions, provenance, and recoverable document states across change.
Related originating lineages:
- Computer Science & Software Engineering — Version-control systems supplied fine-grained ordered revision, attribution, and restoration.
- Literature & Literary Theory — Textual scholarship developed collation and genealogies of drafts, witnesses, and editions.
Review resolution: Both current reviews place document_revision_history primarily in library_information_science; the reconciled classification retains only lineages that materially shaped the mechanism and keeps breadth of origin separate from reach.
Attribution caveat: Bibliographic edition control and digital version control are convergent lineages for revision history.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The history records how the text changed; it does not decide whether the result is still the same work. That identity call — when accumulated rewrites have turned a new edition into a new work — belongs to Identity Continuity Review, which reads this history as evidence rather than as the verdict. Letting the edition number make the call by itself is exactly the failure the archetype warns against: version succession is not the same as identity continuity.
References¶
[1] IFLA Study Group on the Functional Requirements for Bibliographic Records. Functional Requirements for Bibliographic Records: Final Report. K. G. Saur, UBCIM Publications, New Series, vol. 19 (1998). FRBR treats a sufficiently substantial modification as a new work and makes the boundary depend on intellectual or artistic effort rather than merely an edition label. registry ↩