Skip to main content
Version: DocBook V4.5


revhistory — A history of the revisions to a document


Content Model

revhistory ::=


Common attributes


RevHistory is a structure for documenting a history of changes, specifically, a history of changes to the document or section in which it occurs.

DocBook does not mandate an order for revisions: ascending order by date, descending order by date, and orders based on some other criteria are all equally acceptable.

Processing expectations

Formatted as a displayed block. A tabular or list presentation is most common.

The order of revisions within a revhistory (ascending or descending date order, for example) is not mandated by DocBook

Future Changes

Due to a parameterization oversight in the DTD, RevHistory is allowed in some outlandish places. Still, it is not an inline, so it should not be used inside LineAnnotations, Links, or Quotes. (Not to mention the truly outlandish places like Title and SeeAlso!)

In a future version of DocBook, RevHistory will be removed from these inline contexts.

The original intent for RevHistory was simply to document the history of changes to the document that contains it. In keeping with this meaning, you are advised to limit its use to places where bibliographic meta-information is allowed (the “info” elements).

One can argue that RevHistory has broader applicability for documenting changes to other systems as well, and in light of this, it may become available in more contexts, but that has not yet been decided.


The following elements occur in revhistory: revision.


<!DOCTYPE revhistory PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"

<date>11 Dec 1996</date>
<revremark>Bug fixes</revremark>

<date>30 Nov 1996</date>
<revremark>First beta release</revremark>


For additional examples, see also article.