DocBook 5 markup

Why use DocBook 5?

DocBook is an XML schema (language) that has been under development since 1991. It is used by publishers around the world as a preferred schema for single-source publishing of books and technical documents. One such publisher is ANU E Press, which uses DocBook to produce publications. The XML elements of DocBook are terms familiar to editors and publishers—such as book, chapter, glossary, index, bibliography, title, caption, section and paragraph. This naming convention makes it easy for editors to understand how content should be marked up.

The most recent version, DocBook 5, was released in November 2010, and the stylesheets and schema are still being developed by a small group of dedicated programmers to accommodate publishing of new ebook products—PDF, epub 2 and XHTML 1.1 compliant documents can be produced. A new version, DocBook Publishers Schema, is being developed and will better accommodate Dublin Core metadata elements for epub ebooks. Because DocBook is actively maintained and supported with customisable stylesheets, we're confident that it's appropriate for book-based publishing.

An alternative schema is DITA (Darwin Information Typing Architecture). This is newer than DocBook and has a lot of support from technical communication specialists. It is also integrated into various XML authoring products. DITA has a different element structure, and is most suitable for writing online help documentation for software because its content structure is based on standalone, modular topics.

Clean and valid XML code

DocBook markupOur desktop workflow ensures that when word processing documents are converted to DocBook, the XML files contain no extraneous coding—so there's no additional (proprietary) markup that could affect output or make XML content less portable between computing platforms.

For example, our conversion process strips out all Microsoft-specific XML coding and namespaces from Word "docx" documents. The resulting XML files contain only the essential DocBook coding that's needed to produce ebooks. There's also no style coding left behind after conversion—because we add the XML markup and XSLT styles during editing.

All XML coding is validated "on the fly" as we edit—elements are properly marked up and are correctly located within other elements (nested) according to predefined business rules for DocBook. Without valid coding, we could not produce output documents.

 

Data conversion | Editing | Epub ebooks | Publishing | Graphics | Stylesheets | White papers | Contact | Terms
© 2011–2013 Xmplar