Skip to content


Norman Walsh edited this page Oct 3, 2015 · 2 revisions

OASIS DocBook SubCommittee for Publishers

SubCommittee home page at OASIS:


For more than a decade, DocBook has provided a structured markup vocabulary for hardware and software documentation. DocBook is now widely used in both commercial and Open Source environments. DocBook has a very broad element set, and applies to much more than just technical documentation. The DocBook TC is engaged in evolving the suite of DocBook specifications. The community benefits from having a standard, open, interchangeable vocabulary in which to write structured content. DocBook has been, and will continue to be, designed to satisfy this requirement.

The OASIS DocBook SubCommittee for Publishers is chartered to develop and maintain official variants of DocBook in support of the publishing industry. Specifically, the subcommittee will focus on schema and stylesheet customizations to support: periodicals as regularly published technical notes or journals, book publishing (such as business, legal, medical, and other non-technical domains), educational textbooks and other document types as appropriate for this industry.

Scope of Work

This subcommittee will submit additional enhancements back to the full DocBook standard as appropriate. The scope of this DocBook subcommittee is publishing industry content. Broadly, this includes books, journals and other related publications.

This effort will deliver on the following goals:

  • Build official DocBook variants, based against the DocBook v5.0 schemas.
  • Address issues and enhancement requests that have arisen from experience with real-world DocBook implementations.
  • Add support for features specific to the publishing industry.

Proposed Specialization Development Roadmap

  1. Identify elements that should be part of Core DocBook (e.g. dbpool.rnc)
  2. Identify potential "modules" for elements currently part of DocBook but belonging to a particular domain. (e.g. software.rnc, hardware.rnc, publishers.rnc)
  3. Recommend Core DocBook and proposed modules to DocBook TC
  4. Identify general publishing needs not currently met by DocBook
  5. Identify additional specific domains within publishing industry that may need specific modules.
  6. Develop RFEs from identified needs
  7. Develop DocBook v5.0 schema enhancements from RFEs (publishers.rnc)
  8. Submit schema enhancements for approval to DocBook TC


The Publishers SC has set up a mailing list to discuss related issues.

To post to this list, send your email to:

General information about the mailing list is at:



Clone this wiki locally