## 3 Reference Manual DTDs

There are five DTDs for writing manual pages about applications, shell commands, C libraries, Erlang modules and files, all with a similar structure:

- A header.
- Name of the application/command/library/module/file.
- Short summary (one line).
- A longer description.
- "Formal" definitions of functions or commands.
- Optional sections of free text.
- Optional section with the name(s) and email(s) of the author(s).

The differences between the DTDs are the tags for the name, the short summary and some tags inside the "formal" definitions.

### 3.1 The application DTD

The application DTD is intended for a Reference Manual and groups a set of manual pages into one unit. The structure is similar to the part DTD: first an introduction and then the manual pages, written in separate files with the appref, comref, cref, erlref, or fileref DTD.

Example:

    <?xml version="1.0" encoding="latin1" ?>
    <!DOCTYPE application SYSTEM "application.dtd">
    <application>
      <header>
        <title>Application name</title>
        <prepared/>
        <docno/>
        <date/>
        <rev/>
      </header>

      <description>
        <p>Application description...</p>
      </description>

      <include file="module1">
      <include file="module2">
    </application>

### 3.2 <application>

The top level tag of an application DTD.

Contains a <header>, an optional <description>, followed by one or more <include>.

### 3.3 The appref DTD

This is the DTD for writing an application manual page.

Example:

    <?xml version="1.0" encoding="latin1" ?>
    <!DOCTYPE appref SYSTEM "appref.dtd">
    <appref>
      <header>
        <title>Application name</title>
        <prepared/>
        <docno/>
        <date/>
        <rev/>
      </header>

      <app>Application name</app>

      <appsummary>A short application summary.</appsummary>

      <description>
        <p>A longer description of the application.</p>
      </description>

      <section>
        <title>Configuration</title>

          <p>...</p>
      </section>

      ...

      <authors>
        <aname>Name of author</aname>
        <email>Email of author</email>
      </authors>
    </appref>

#### 3.3.1 <appref>

The top level tag of an appref DTD.

Contains <header>, <app>, <appsummary>, <description>, zero or more <section> and <funcs>, followed by zero or more <authors>.

#### 3.3.2 <app>

The application name. Contains plain text.

#### 3.3.3 <appsummary>

Short summary. Contains plain text.

### 3.4 The comref DTD

This is the DTD for writing a command manual page.

Example:

    <?xml version="1.0" encoding="latin1" ?>
    <!DOCTYPE comref SYSTEM "comref.dtd">
    <comref>
      <header>
        <title>Command name</title>
        <prepared/>
        <docno/>
        <date/>
        <rev/>
      </header>

      <com>Command name</com>

      <comsummary>A short command summary.</comsummary>

      <description>
        <p>A long description of the command.</p>
      </description>

      <funcs>
        <func>
          <name>command</name>
          <name>command -flag <arg></name>
          <fsummary>A short command summary (max 40 characters).</fsummary>
          <desc>
            <p>An extended command description.
          </desc>
        </func>
      </funcs>

      <section>
        <title>Options</title>

        <p>...</p>
      </section>

      <authors>
        <aname>Name of author</aname>
        <email>Email of author</email>
      </authors>
    </comref>

#### 3.4.1 <comref>

The top level tag for a comref DTD.

Contains <header>, <com>, <comsummary>, <description>, zero or more <section> and <funcs>, followed by zero or more <authors>.

#### 3.4.2 <com>

The command name. Contains plain text.

#### 3.4.3 <comsummary>

Short summary. Contains plain text.

### 3.5 The cref DTD

This is the DTD for writing a C library manual page.

Example:

    <?xml version="1.0" encoding="latin1" ?>
    <!DOCTYPE cref SYSTEM "cref.dtd">
    <cref>
      <header>
        <title>C library name</title>
        <prepared/>
        <docno/>
        <date/>
        <rev/>
      </header>

      <lib>C library name</lib>

      <libsummary>A short C library summary.</libsummary>

      <description>
        <p>A longer description of the C library.</p>
      </description>

      <funcs>
        <func>
          <name><ret>void</ret><nametext>start(bar)</nametext></name>
          <name><ret>void</ret><nametext>start(foo)</nametext></name>
          <fsummary>A short function summary (max 40 characters).</fsummary>
          <type>
            <v>char bar</v>
            <v>int foo</v>
          </type>
          <desc>
            <p>An extended function description.</p>
          </desc>
        </func>

        ...
      </funcs>

      <section>
        <title>A title</title>

        <p>Some text...</p>
      </section>

    </cref>

#### 3.5.1 <cref>

The top level tag for a cref DTD.

Contains <header>, <lib>, <libsummary>, <description>, zero or more <section> and <funcs>, followed by zero or more <authors>.

#### 3.5.2 <lib>

The C library name or acronym. Contains plain text.

#### 3.5.3 <libsummary>

Short summary. Contains plain text.

### 3.6 The erlref DTD

This is the DTD for writing Erlang module manual pages.

Example:

    <?xml version="1.0" encoding="latin1" ?>
    <!DOCTYPE erlref SYSTEM "erlref.dtd">
    <erlref>
      <header>
        <title>Module name</title>
        <prepared/>
        <docno/>
        <date/>
        <rev/>
      </header>

      <module>Module name</module>

      <modulesummary>A short module summary.</modulesummary>

      <description>
        <p>A longer description of the module.</p>
      </description>

      <funcs>
        <func>
          <name>start() -> Result</name>
          <name>start(N) -> Result</name>
          <fsummary>A short function summary (max 40 characters).</fsummary>
          <type>
            <v>Pid = pid()</v>
            <v>N = int()</v>
            <v>Result = {ok, Pid} | {error, Reason}</v>
            <v>Reason = term()</v>
            <d>A parameter description.</d>
          </type>
          <desc>
            <p>An extended function description.</p>
          </desc>
        </func>

        ...
      </funcs>

      <section>
        <title>Some Title</title>
        <p>Some text...</p>
      </section>

      <authors>
        <aname>Name of author</aname>
        <email>Email of author</email>
      </authors>
    </erlref>

#### 3.6.1 <erlref>

The top level tag for an erlref DTD.

Contains <header>, <module>, <modulesummary>, <description>, zero or more <section> and <funcs>, followed by zero or more <authors>.

#### 3.6.2 <module>

The module name. Contains plain text.

#### 3.6.3 <modulesummary>

Short summary. Contains plain text.

### 3.7 The fileref DTD

This is the DTD for writing file manual pages. In OTP, this DTD is used for defining the format of for example .rel and .app files.

Example:

    <?xml version="1.0" encoding="latin1" ?>
    <!DOCTYPE fileref SYSTEM "fileref.dtd">
    <fileref>
      <header>
        <title>File name</title>
        <prepared/>
        <docno/>
        <date/>
        <rev/>
      </header>

      <file>fileref</file>

      <filesummary>A short file summary.</filesummary>

      <description>
        <p>A longer description of the file.</p>
      </description>

      <section>
        <title>File format</title>

        <p>...</p>
      </section>

      <authors>
        <aname>Name of author</aname>
        <email>Email of author</email>
      </authors>
    </fileref>

The file reference manual can also contain function definitions, similar to the erlref DTD.

#### 3.7.1 <fileref>

The top level tag for a fileref DTD.

Contains <header>, <file>, <filesummary>, <description>, zero or more <section> and <funcs>, followed by zero or more <authors>.

#### 3.7.2 <file>

The name of the file or file type. Contains plain text.

#### 3.7.3 <filesummary>

Short summary. Contains plain text.

### 3.8 <description>

The introduction after the title and before sections and "formal" definitions.

Contains any combination and any number of block tags except <image> and <table>.

### 3.9 <section>

Subdivisions of the document. Contains an optional <marker>, a <title>, followed by any combination and any number of block tags except <image> and <table>.

### 3.10 <funcs>

A group of "formal" function definitions.

Contains one or more <func>.

### 3.11 <func>

A "formal" function definition.

Contains one or more <name>, followed by <fsummary>, <type> (optional) and <desc> (optional).

### 3.12 <name>

Function/command signature with name, arguments and return value. Contains plain text, except for the cref DTD where it contains a <ret> (return type, plain text) and a <nametext> (function name and arguments, plain text).

In the case of an erlref DTD, DocBuilder will automatically try to add a marker, <marker id="Name/Arity"> or <marker id="Name">, based on the contents of this tag before the function definition.

Example: Consider the following name definition

    <name>foo(Arg1, Arg2) -> ok | {error, Reason}</name>

DocBuilder will create a marker <marker id="foo/2"> before the function definition in the generated HTML. That is, referring to the function using <seealso marker="#foo/2">foo/2</seealso> will automatically work.

### 3.13 <fsummary>

Function/command summary. Contains plain text, <c> and <em>.

### 3.14 <type>

Type declarations for the function/command.

Contains one or more pairs of <v> and <d> (optional).

### 3.15 <v>

Type declaration for an argument or return value. Contains plain text.

### 3.16 <d>

Description for an argument or return value. Contains plain text, <c> and <em>.

### 3.17 <desc>

Function/command description. Contains block tags except <image> and <table>.

### 3.18 <authors>

Authors of the manual page. The authors element is optional.

Contains one or more pairs of <aname> and <email>.

### 3.19 <aname>

Author name. Contains plain text.

### 3.20 <email>

Author email address. Contains plain text.

docbuilder 0.9.8.4
Copyright © 1991-2008 Ericsson AB