Under the auspices of the Davenport Group, the DocBook DTD began to
take on a larger scope: It was now being used by a much wider audience, and
for new purposes, such as direct authoring with SGML-aware tools and publishing
directly to paper. As the largest users of DocBook, Novell and Sun tended
to have heavy influence on the design.
In order to help users manage change, the new Davenport charter established
the following rules for DocBook releases:
Minor versions (“point releases,” such as V2.2)
could add to the markup model, but could not change it in a backwards-incompatible
way. For example, a new kind of list element could be added, but it would
not be acceptable for the existing itemized-list model to start requiring
two list items inside it instead of only one. Thus, any document conforming
to version n
.0 would also conform to n
.m
.
Major versions (such as V3.0) could both add to the markup
model and make backwards-incompatible changes. However, the changes had to
have been announced in the previous major release.
Major-version introductions must be separated by at least
a year.
V3.0 was released in January 1997. After that time, although DocBook's
audience continued to grow, many of the stalwarts of the Davenport Group became
involved in the XML effort, and development slowed dramatically. The idea
of creating an official XML-compliant version of DocBook was discussed, but
not implemented.
The sponsors wanted to close out Davenport in an orderly way, but ensure
that DocBook users would be supported somehow. It was suggested that OASIS
become DocBook's new home. An OASIS DocBook Technical Committee was formed
in July, 1998, with Eduardo Gutentag of Sun as chair.