The DocBook Schema V5.1
Technical Committee Editorial Draft Candidate Release 3 (CR3)
16 Jul 2014
- Specification URIs:
- This Version:
- Previous Version:
- Latest Version:
- Technical Committee:
- OASIS DocBook Technical Committee
- Norman Walsh
- Norman Walsh
- Declared XML Namespaces:
DocBook is a general purpose [XML] schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).
The Version 5.1 release introduces assemblies for topic-oriented authoring. It also addresses a selection of bugs and feature requests.
The Technical Committee provides the DocBook 5.1 schema in other schema languages, including W3C XML Schema and an XML DTD, but the RELAX NG Schema is the normative schema.
This specification is known to have formatting problems. These will be resolved before the final release.
This document was last revised or approved by the DocBook Technical Committee on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.
Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's web page at http://www.oasis-open.org/committees/docbook.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/docbook/ipr.php).
The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/docbook.
DocBook is general purpose XML schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).
The DocBook Technical Committee maintains the DocBook schema. Starting with V5.0, DocBook is normatively available as a [RELAX NG] Schema (with some additional [Schematron] assertions). W3C XML Schema and Document Type Definition (DTD) versions are also available.
The Version 5.1 introduces assemblies for topic-oriented authoring and addresses a selection of bugs and feature requests.
The DocBook Technical Committee welcomes bug reports and requests for enhancement (RFEs) from the user community. The current list of outstanding requests is available through the SourceForge tracker interface. This is also the preferred mechanism for submitting new requests.
The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this OASIS TC Working Draft are to be interpreted as described in [RFC 2119].
1.2. Normative References
[XML] Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, et. al., editors. Extensible Markup Language (XML) 1.0 (Fourth Edition). World Wide Web Consortium, 16 August 2006.
[W3C XML Datatypes] Paul V. Biron and Ashok Malhotra, editors. XML Schema Part 2: Datatypes. World Wide Web Consortium, 2000.
[RFC 2119] IETF (Internet Engineering Task Force). RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. 1997.
[RFC 3023] IETF (Internet Engineering Task Force). RFC 3023: XML Media Types. M. Murata, S. St. Laurent, D. Kohn. 2001.
[DocBook 5: TDG] Norman Walsh. DocBook 5.0: The Definitive Guide. O'Reilly Media. April 2010.
[DocBook 5.1: TDG] Norman Walsh. DocBook 5.1: The Definitive Guide.
1.3. Non-Normative References
[SGML] JTC 1, SC 34. ISO 8879:1986 Information processing -- Text and office systems -- Standard Generalized Markup Language (SGML). 1986.
[W3C XML Schema] Henry S. Thompson, David Beech, Murray Maloney, et. al., editors. XML Schema Part 1: Structures. World Wide Web Consortium, 2000.
2. The DocBook RELAX NG Schema
The DocBook RELAX NG Schema is distributed from the DocBook site at OASIS. DocBook is also available from the mirror on http://docbook.org/.
One modern school of thought on technical documentation stresses the development of independent units of documentation, often called topics, rather than a single narrative. Instead of writing something that DocBook users would easily recognize as a book consisting of a preface, several consecutive chapters, and a few appendixes, the author (or authors) write a set of discrete topics covering different aspects of the system as if they were wholly independent.
In a typical online presentation system, for example the world wide web or online help, each topic is a page that stands alone. Except, of course, that just as no man is an island, no topic is completely unrelated to the other topics that are available.
From any given topic, there may be topics of obviously related interest. The nature of the relationships may vary. Some topics are related by physical proximity (if you're interested in the ink cartridges in a printer, you may also be interested in the print head), others by their procedural nature (adding or replacing memory, adding or replacing a hard drive, or even changing the CPU are all topics that might logically follow a topic that describes how to open the computer case).
In a single narrative, it is the responsibility of the author to manage these relationships. He or she can reasonably assume that anyone reading chapter 4 has read chapters 1, 2, and 3. If the reader needs to be directed elsewhere, a cross reference can be used (for example, “for more information on paper jams, see Section 3.5, The Paper Path”).
In a topic-oriented system, authors are explicitly instructed to write independent units. No linear order can be assumed and many forms of explicit cross-reference are discouraged.
Documentation managers treat the library of available topics very much as programmers treat libraries of available functions. Just as any given program can pick and choose from the available libraries, the documentation for any given system can pick and choose from the available topics.
If you imagine a large documentation group managing the documentation for several related systems (different models of printer, different configurations of a software system, computers assembled from different components, etc.) it's easy to see the appeal of topic-oriented authoring.
In a successful deployment, you might find a library of say 1,000 topics which, taken together, document five or six related systems, each of which uses 700-800 topics. Some topics are used in every system, many are used in several systems, and a small number of topics are unique to a specific system.
In order to make such a documentation platform functional, you need not only the individual topics, but also some sort of “map” or “assembly” file that describes which topics from the library are used, what relationships exist between them and, at least for print presentation, what linear order is to be imposed upon them.
DocBook uses an assemblies for this purpose.
3. Identifying DocBook Documents and Schemas
Historically, when DocBook was defined by a DTD, DocBook documents could be identified by the presence of standard public and/or system identifiers in the document type declaration. RELAX NG, the normative schema language for DocBook V5.0, does not provide any equivalent mechanism.
For systems that can make use of public identifiers, e.g., systems
where the informative DTD is being used, the following
public identifier should be used for DocBook V5.1:
-//OASIS//DTD DocBook V5.1//EN//XML”.
This specification normatively defines DocBook V5.1 with a RELAX NG grammar and a set of Schematron assertions. A conformant DocBook V5.1 document must be valid according to both the grammar and the assertions.
The reference documentation describes additional constraints and processing expectations. A conformant DocBook V5.1 document should respect those constraints and anticipate those processing expectations.
5. Release Notes
See http://www.relaxng.org/ for a list of tools that can validate an XML document using RELAX NG. Note that not all products are capable of evaluating the Schematron assertions in the schema.
This appendix registers a new MIME media type,
1. Registration of MIME media type application/docbook+xml
- MIME media type name:
- MIME subtype name:
- Required parameters:
- Optional parameters:
This parameter has identical semantics to the
charsetparameter of the
application/xmlmedia type as specified in [RFC 3023] or its successors.
- Encoding considerations:
By virtue of DocBook XML content being XML, it has the same considerations when sent as “
application/docbook+xml” as does XML. See [RFC 3023], Section 3.2.
- Security considerations:
Several DocBook elements may refer to arbitrary URIs. In this case, consider the security issues of RFC 2396, section 7.
- Interoperability considerations:
- Published specification:
This media type registration is for DocBook documents as described by [DocBook 5: TDG].
- Applications which use this media type:
There is no experimental, vendor specific, or personal tree predecessor to “
application/docbook+xml”, reflecting the fact that no applications currently recognize it. This new type is being registered in order to allow for the deployment of DocBook on the World Wide Web as a first class XML application.
- Additional information:
- Magic number(s):
There is no single initial octet sequence that is always present in DocBook documents.
- File extension(s):
DocBook documents are most often identified with the extension “
- Macintosh File Type Code(s):
- Person & email address to contact for further information:
- Intended usage:
- Author/Change controller:
The DocBook specification is a work product of the DocBook Technical Committee at OASIS.
2. Fragment Identifiers
For documents labeled as
identifier notation is exactly that for
as specified in [RFC 3023] or its successors.
The following individuals have participated in the creation of this specification and are gratefully acknowledged: Steve Cogorno, Gary Cornelius, Adam Di Carlo, Paul Grosso, Dick Hamilton, Nancy Harrison, Scott Hudson, Mark Johnson, Gershon Joseph, Jirka Kosek, Larry Rowland, Michael Smith, Robert Stayton (Secretary), Norman Walsh, (Chair, Editor).
Table of Contents
1. Changes in DocBook V5.1CR3
This release contains a bug fix.
2. Changes in DocBook V5.1CR2
This release contains bug fixes and improvements over V5.1CR1.
3. Changes in DocBook V5.1CR1
This release contains bug fixes and improvements over V5.0.
Added an RDFa Lite extension schema.
Merged ITS changes.
Added @its:version, improved better handling of extensibility.
Updated ITS to support ITS 2.0
Attempt to implement the whole proposal for accessability attributes in CALS tables.
Added scope attribute to CALS tables.
Removed format attribute from output element; the standard effectivity attribute outputformat can be used instead.
Added outputformat as an effectivity attribute.
Added: AltGr and Return to keycap class values.
Renamed fileref attribute to href in on resources in assemblies.
Fixed bug in Schematron assertions about XLink, thanks to Hussein Shafie
Made info on structure and module optional in assemblies.
Adopted the recent proposals to add attributes/parameters to audio and video objects.
Fixed reference to broken pattern; make sure linking attributes are on areas.
Allow link in extendedlink, in preparation for arc and locator being removed in V6.0.
Added extendedlink changes to the V6.0 future use comments.
Reworked XLink attributes to support simple/extended links.
Added pattern for imagedata, SVG, and MathML content (so that it can be extended by the XInclude schema).
Added XInclude to images and equations; allow foreign, namespace-qualified attributes on the xi:include element.
Attempt to implement Larry's latest suggestions about assemblies.
Changed Schematron namespace to official ISO Schematron URI.
Allow topic in chapter and appendix (as an alternative to narrative content) per May 2010 TC meeting.
Fixed content model of book and part to make topic an alternative, not part of the component mixture.
Allow the other major components of an assembly to be top level elements (so they can be stored in separate files, for example).
Allow an assembly without any structure elements.
Tweak assembly schemas.
Allow override element in assemblies.
Generalized toc/index to db.navigation.components in assembly structure and module for consistency
Updated: in assembly, if at least one resource is required, then at least one structure should be required as well.
Removed description attribute from assemblies (no content in attributes!); added some refpurpose documentation for attributes and attribute values.
Added refpurpose for type attribute.