DocBook · Lablypedia

As a semantic language, DocBook enables its users to create document content in a presentation-neutral form that captures the logical structure of the content; that content can then be published in a variety of formats, including HTML, XHTML, EPUB, PDF, man pages, WebHelp and HTML Help, without requiring users to make any changes to the source. In other words, when a document is written in DocBook format it becomes easily portable into other formats, rather than needing to be rewritten.

Design

DocBook is an XML language. In its current version (5.x), DocBook's language is formally defined by a RELAX NG schema with integrated Schematron rules. (There are also W3C XML Schema+Schematron and Document Type Definition (DTD) versions of the schema available, but these are considered non-standard.)

As a semantic language, DocBook documents do not describe what their contents "look like", but rather the meaning of those contents. For example, rather than explaining how the abstract for an article might be visually formatted, DocBook simply says that a particular section is an abstract. It is up to an external processing tool or application to decide where on a page the abstract should go and what it should look like or whether or not it should be included in the final output at all.

DocBook provides a vast number of semantic element tags. They are divided into three broad categories, namely structural, block-level, and inline.

Structural tags specify broad characteristics of their contents. The book element, for example, specifies that its child elements represent the parts of a book. This includes a title, chapters, glossaries, appendices, and so on. DocBook's structural tags include, but are not limited to:

set: Titled collection of one or more books or articles, can be nested with other sets
book: Titled collection of chapters, articles, and/or parts, with optional glossaries, appendices, etc.
part: Titled collection of one or more chapters—can be nested with other parts, and may have special introductory text
article: Titled, unnumbered collection of block-level elements
chapter: Titled, numbered collection of block-level elements—chapters don't require explicit numbers, a chapter number is the number of previous chapter elements in the XML document plus 1
appendix: Contains text that represents an appendix
dedication: Text represents the dedication of the contained structural element

Structural elements can contain other structural elements. Structural elements are the only permitted top-level elements in a DocBook document.

Block-level tags are elements like paragraph, lists, etc. Not all these elements can directly contain text. Sequential block-level elements render one "after" another. After, in this case, can differ depending on the language. In most Western languages, "after" means below: text paragraphs are printed down the page. Other languages' writing systems can have different directionality; for example, in Japanese, paragraphs are often printed in downward columns, with the columns running from right to left, so "after" in that case would be to the left. DocBook semantics are entirely neutral to these kinds of language-based concepts.

Inline-level tags are elements like emphasis, hyperlinks, etc. They wrap text within a block-level element. These elements do not cause the text to break when rendered in a paragraph format, but typically they cause the document processor to apply some kind of distinct typographical treatment to the enclosed text, by changing the font, size, or similar attributes. (The DocBook specification does say that it expects different typographical treatment, but it does not offer specific requirements as to what this treatment may be.) That is, a DocBook processor doesn't have to transform an emphasis tag into italics. A reader-based DocBook processor could increase the size of the words, or, a text-based processor could use bold instead of italics.

Sample document

<span id="mwUw"></span><span class="w" id="mwVA"> </span><span class="cp" id="mwVQ"><?xml version="1.0" encoding="UTF-8"?></span> <span class="w" id="mwVg"> </span><span class="nt" id="mwVw"><book</span><span class="w" id="mwWA"> </span><span class="na" id="mwWQ">xml:id=</span><span class="s" id="mwWg">"simple_book"</span><span class="w" id="mwWw"> </span><span class="na" id="mwXA">xmlns=</span><span class="s" id="mwXQ">"http://docbook.org/ns/docbook"</span><span class="w" id="mwXg"> </span><span class="na" id="mwXw">version=</span><span class="s" id="mwYA">"5.0"</span><span class="nt" id="mwYQ">></span> <span class="w" id="mwYg"> </span><span class="nt" id="mwYw"><title></span>Very<span class="w" id="mwZA"> </span>simple<span class="w" id="mwZQ"> </span>book<span class="nt" id="mwZg"></title></span> <span class="w" id="mwZw"> </span><span class="nt" id="mwaA"><chapter</span><span class="w" id="mwaQ"> </span><span class="na" id="mwag">xml:id=</span><span class="s" id="mwaw">"chapter_1"</span><span class="nt" id="mwbA">></span> <span class="w" id="mwbQ"> </span><span class="nt" id="mwbg"><title></span>Chapter<span class="w" id="mwbw"> </span>1<span class="nt" id="mwcA"></title></span> <span class="w" id="mwcQ"> </span><span class="nt" id="mwcg"><para></span>Hello<span class="w" id="mwcw"> </span>world!<span class="nt" id="mwdA"></para></span> <span class="w" id="mwdQ"> </span><span class="nt" id="mwdg"><para></span>I<span class="w" id="mwdw"> </span>hope<span class="w" id="mweA"> </span>that<span class="w" id="mweQ"> </span>your<span class="w" id="mweg"> </span>day<span class="w" id="mwew"> </span>is<span class="w" id="mwfA"> </span>proceeding<span class="w" id="mwfQ"> </span><span class="nt" id="mwfg"><emphasis></span>splendidly<span class="nt" id="mwfw"></emphasis></span>!<span class="nt" id="mwgA"></para></span> <span class="w" id="mwgQ"> </span><span class="nt" id="mwgg"></chapter></span> <span class="w" id="mwgw"> </span><span class="nt" id="mwhA"><chapter</span><span class="w" id="mwhQ"> </span><span class="na" id="mwhg">xml:id=</span><span class="s" id="mwhw">"chapter_2"</span><span class="nt" id="mwiA">></span> <span class="w" id="mwiQ"> </span><span class="nt" id="mwig"><title></span>Chapter<span class="w" id="mwiw"> </span>2<span class="nt" id="mwjA"></title></span> <span class="w" id="mwjQ"> </span><span class="nt" id="mwjg"><para></span>Hello<span class="w" id="mwjw"> </span>again,<span class="w" id="mwkA"> </span>world!<span class="nt" id="mwkQ"></para></span> <span class="w" id="mwkg"> </span><span class="nt" id="mwkw"></chapter></span> <span class="w" id="mwlA"> </span><span class="nt" id="mwlQ"></book></span>

Semantically, this document is a "book", with a "title", that contains two "chapters" each with their own "titles". Those "chapters" contain "paragraphs" that have text in them. The markup is fairly readable in English.

In more detail, the root element of the document is book. All DocBook elements are in an XML Namespace, so the root element has an xmlns attribute to set the current namespace. Also, the root element of a DocBook document must have a version that specifies the version of the format that the document is built on.

(XML documents can include elements from multiple namespaces at once, like the id attributes in the example.)

A book element must contain a title, or an info element containing a title. This must be before any child structural elements. Following the title are the structural children, in this case, two chapter elements. Each of these must have a title. They contain para block elements, which can contain free text and other inline elements like the emphasis in the second paragraph of the first chapter.

Schemas and validation

Rules are formally defined in the DocBook XML schema. Appropriate programming tools can validate an XML document (DocBook or otherwise), against its corresponding schema, to determine if (and where) the document fails to conform to that schema. XML editing tools can also use schema information to avoid creating non-conforming documents in the first place.

5 more chapters are free with a Lably account.

Authoring and processing

Because DocBook is XML, documents can be created and edited with any text editor. A dedicated XML editor is likewise a functional DocBook editor. DocBook provides schema files for popular XML schema languages, so any XML editor that can provide content completion based on a schema can do so for DocBook. Many graphical or WYSIWYG XML editors come with the ability to edit DocBook like a word processor.

Tables, list items, and other stylized content can be copied and pasted into the DocBook editor and will be preserved in the DocBook XML output. Because DocBook conforms to a well-defined XML schema, documents can be validated and processed using any tool or programming language that includes XML support.

History

DocBook began in 1991 in discussion groups on Usenet and eventually became a joint project of HAL Computer Systems and O'Reilly & Associates and eventually spawned its own maintenance organization (the Davenport Group) before moving in 1998 to the SGML Open consortium, which subsequently became OASIS. DocBook is currently maintained by the DocBook Technical Committee at OASIS.

DocBook is available in both SGML and XML forms, as a DTD. RELAX NG and W3C XML Schema forms of the XML version are available. Starting with DocBook 5, the RELAX NG version is the "normative" form from which the other formats are generated.

DocBook originally started out as an SGML application, but an equivalent XML application was developed and has now replaced the SGML one for most uses. (Starting with version 4 of the SGML DTD, the XML DTD continued with this version numbering scheme.) Initially, a key group of software companies used DocBook since their representatives were involved in its initial design. Eventually, however, DocBook was adopted by the open source community where it has become a standard for creating documentation for many projects, including FreeBSD, KDE, GNOME desktop documentation, the GTK+ API references, the Linux kernel documentation (which, as of July 2016, is transitioning to Sphinx/reStructuredText), and the work of the Linux Documentation Project.

Pre DocBook v5.0

Until DocBook 5, DocBook was defined normatively by a Document Type Definition (DTD). Because DocBook was built originally as an application of SGML, the DTD was the only available schema language. DocBook 4.x formats can be SGML or XML, but the XML version does not have its own namespace.

DocBook 4.x formats had to live within the restrictions of being defined by a DTD. The most significant restriction was that an element name uniquely defines its possible contents. That is, an element named info must contain the same information no matter where it is in the DocBook file. As such, there are many kinds of info elements in DocBook 4.x: bookinfo, chapterinfo, etc. Each has a slightly different content model, but they do share some of their content model. Additionally, they repeat context information. The book's info element is that, because it is a direct child of the book; it does not need to be named specially for a human reader. However, because the format was defined by a DTD, it did have to be named as such. The root element does not have or need a version, as the version is built into the DTD declaration at the top of a pre-DocBook 5 document.

DocBook 4.x documents are not compatible with DocBook 5, but can be converted into DocBook 5 documents via an XSLT stylesheet. One (db4-upgrade.xsl) is provided as part of the distribution of the DocBook 5 schema and specification package.

Output formats

DocBook files are used to prepare output files in a wide variety of formats. Nearly always, this is accomplished using DocBook XSL stylesheets. These are XSLT stylesheets that transform DocBook documents into a number of formats (HTML, XSL-FO for later conversion into PDF, etc.). These stylesheets can be sophisticated enough to generate tables of contents, glossaries, and indexes. They can oversee the selection of particular designated portions of a master document to produce different versions of the same document (such as a "tutorial" or a "quick-reference guide", where each of these consist of a subset of the material). Users can write their own customized stylesheets or even a full-fledged program to process the DocBook into an appropriate output format as their needs dictate.

Norman Walsh and the DocBook Project development team maintain the key application for producing output from DocBook source documents: A set of XSLT stylesheets (as well as a legacy set of DSSSL stylesheets) that can generate high-quality HTML and print (FO/PDF) output, as well as output in other formats, including RTF, man pages and HTML Help.

Web help is a chunked HTML output format in the DocBook XSL stylesheets that was introduced in version 1.76.1. The documentation for web help also provides an example of web help and is part of the DocBook XSL distribution.

The major features are its fully CSS-based page layout, search of the help content, and a table of contents in collapsible-tree form. Search has stemming, match highlighting, explicit page-scoring, and the standard multilingual tokenizer. The search and TOC are in a pane that appears as a frameset, but is actually implemented with div tags and cookies (so that it is progressive).

Simplified DocBook

DocBook offers a large number of features that may be overwhelming to a new user. For those who want the convenience of DocBook without a steep learning curve, Simplified DocBook was designed. It is a small subset of DocBook designed for single documents such as articles or white papers (i.e., "books" are not supported). The Simplified DocBook DTD is currently at version 1.1.

Criticism

Ingo Schwarze, the author of OpenBSD's mandoc, considers DocBook inferior to the semantic mdoc macro for man pages. In an attempt to write a DocBook-to-mdoc converter (previous converters like docbook-to-man do not cover semantic elements), he finds the semantic parts "bloated, redundant, and incomplete at the same time" compared to elements covered in mdoc. Moreover, Schwarze finds the DocBook specification not specific enough about the use of tags, the language non-portable across versions, rough in details and overall inconsistent.