<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="lillet" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#">
<info>
    
    
    
    
    
    
    
<title>DocBook NG: The “PTO” Release</title><biblioid class="uri">http://norman.walsh.name/2005/07/24/pto</biblioid>
<volumenum>8</volumenum>
<issuenum>105</issuenum>
<pubdate>2005-07-24T11:16:50-04:00</pubdate>
<date>$Date: 2006-08-22 11:26:24 -0400 (Tue, 22 Aug 2006) $</date>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2005</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>On the road to DocBook V5.0α1. This is very likely to be the
last “NG” release before the DocBook Technical Committee releases an
official V5.0 alpha.</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#DocBook"/>
</info>

<epigraph>
<attribution>
      <personname>
	<firstname>E.</firstname>
<surname>Dijkstra</surname>
      </personname>
    </attribution>
<para xml:id="p15">Testing can show the presence of errors, but
not their absence.
</para>
</epigraph>

<para xml:id="p16"><link xlink:href="http://www.paulastexasorange.com/">Paula's
Texas Orange</link>, “PTO” is
<link xlink:href="/threads/refactorDocBook">the fourteenth</link><footnote>
<para xml:id="p17">What about “N” and “O”? Well, two things really: I couldn't
think of any good names starting with those letters that fit the
theme and I really wanted to get to “P” before the NG series
came to an end. Delicious in its own
right, <citetitle>Paula's Texas Orange</citetitle>
makes the finest of margaritas. That goes double
if you can get Paula to mix one up for you. If you're going to pass through
Austin, pick up a case for me, will you?</para>
    </footnote>
release of
<link xlink:href="http://docbook.org/docbook-ng/">DocBook NG</link>.</para>

<para xml:id="p18">It is very likely that the
<link xlink:href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook">DocBook
Technical Committee</link> will approve publication of “PTO” as
DocBook V5.0 (alpha release 1) in August, 2005.</para>

<para xml:id="p19">There are two significant changes in the “PTO”
release. First, the content models associated with sections have been
reworked. Second, support for XInclude, first introduced in <link xlink:href="http://docbook.org/docbook-ng/mezcal/">Mezcal</link>,
has been moved into a separate
schema. It will be part of the DocBook schema distribution, but it
will not be part of the normative DocBook schema.</para>

<para xml:id="p20">To understand how and why the section content
models have been reorganized, it's important to recall the intended
distinction between <tag>simplesect</tag> and the other sectioning
elements: <tag>simplesect</tag> does not appear in the
<citetitle>Table of Contents</citetitle> (ToC).</para>

<para xml:id="p21">What, you may ask, is the point of that? Well,
consider a long document where every chapter or major section always
ends with subsections named “Summary”, “Exercises”, and “See Also”.
The author or production editor for such a document might conclude
that the ToC is shorter and more helpful to the reader if it does not
include these three section titles over and over again. By using
<tag>simplesect</tag> for these sections, they are suppressed them
from the ToC.</para>

<para xml:id="p22">Problem is, since the introduction of
<tag>simplesect</tag>, they have always appeared as an alternative to
the other sectioning elements. In other words, a <tag>chapter</tag>
could contain <emphasis>either</emphasis> <tag>section</tag>+
<emphasis>or</emphasis> <tag>simplesect</tag>+. That greatly reduces
their utility since it prevents a chapter from containing a few
“normal” sections followed by “simple sections”.</para>

<para xml:id="p23">In “PTO”, I've replaced this forced choice with
groups of the form</para>

<screen>(section+, simplesect*) | simplesect+</screen>

<para xml:id="p24">allowing <tag>simplesect</tag>s to occur at the
same level as, but after, other sections. I think this will make
<tag>simplesect</tag> much more useful.</para>

<para xml:id="p14">I've also released “PTO” versions of
<link xlink:href="http://docbook.org/docbook-ng/simplified/pto/">Simplified NG</link>,
<link xlink:href="http://docbook.org/docbook-ng/slides/pto/">Slides NG</link>, and
<link xlink:href="http://docbook.org/docbook-ng/website/pto/">Website NG</link>.
</para>

</essay>

