<?xml version="1.0"?>
<!DOCTYPE lrcsml:config-spec PUBLIC
  "-//LogReport.ORG//DTD Lire Report Configuration Specification Markup Language V1.1//EN"
  "http://www.logreport.org/LRCSML/1.1/lrcsml.dtd">
<lrcsml:config-spec xmlns:lrcsml="http://www.logreport.org/LRCSML/"
 xmlns:lrcml="http://www.logreport.org/LRCML/">

  <!-- $Id: lire.xml.in,v 1.20 2008/07/10 15:15:17 wraay Exp $ -->

  <lrcsml:boolean name="lr_test_uid" section="operation">
    <lrcsml:summary>Prevent Lire from being run as root</lrcsml:summary>
    <lrcsml:description>
      <para>It's generally a good idea to give programs
        only the minimum amount of privileges required to run and restrict all
        else. Lire does not need to run as root for normal operation and it's
        therefore recommended practice to run it in a dedicated UNIX account.
        Lire checks its user ID when it starts and aborts when it finds that it
        runs as root. You can disable this check here so that Lire can be run
        from the superuser account. Caveat emptor.</para>
    </lrcsml:description>
    <lrcml:param name="lr_test_uid">true</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:boolean name="lr_keep" section="responder">
    <lrcsml:summary>Keep intermediate files</lrcsml:summary>
    <lrcsml:description>
      <para>During its operation Lire generates intermediate files that are
        normally removed when done with. If you wish to study or debug the way
        Lire works you can prevent Lire from deleting them with this option.
        The files will be stored in the directory set in the
        `<varname>TMPDIR</varname>' environment variable.</para>
    </lrcsml:description>
    <lrcml:param name="lr_keep">no</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:boolean name="lr_debug" section="operation">
    <lrcsml:summary>Enable debugging output</lrcsml:summary>
    <lrcsml:description>
      <para>When this option is set, all messages of levels
        `debug' and `info' will be sent to <filename>stderr</filename> or to
        the system log - depending on how Lire is configured and if you use
        the <command>lr_run</command> wrapper to run Lire.</para>
    </lrcsml:description>
    <lrcml:param name="lr_debug">no</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:select name="lr_logging_method" section="operation">
    <lrcsml:summary>Where to send progress/debug/warning/error
      messages</lrcsml:summary>
    <lrcsml:description>
      <para>Lire can output a lot of information while it runs.
        If Lire runs from a batch environment such as an autoresponder or a
        cron job, it may be more convenient to send this data to the system
        log so that it may be inspected later.</para>
    </lrcsml:description>
    <lrcsml:option name="stderr">
      <lrcsml:summary>Standard error (terminal or redirected to a
        file)</lrcsml:summary>
    </lrcsml:option>
    <lrcsml:option name="syslog">
      <lrcsml:summary>UNIX syslog daemon</lrcsml:summary>
    </lrcsml:option>
    <lrcml:param name="lr_logging_method">stderr</lrcml:param>
  </lrcsml:select>

  <lrcsml:select name="lr_logging_facility" section="operation">
    <lrcsml:summary>Which syslog `facility' to use</lrcsml:summary>
    <lrcsml:description>
      <para>The standard UNIX syslog daemon has a couple of ways to categorize
        log messages. You can configure the syslog daemon to sort messages
        into different log files based on the facility tag. See the
        syslog.conf(5) man page for more information. You can select a syslog
        `facility' tag for Lire to use here.</para>
    </lrcsml:description>

    <lrcsml:option name="auth"/>
    <lrcsml:option name="authpriv"/>
    <lrcsml:option name="cron"/>
    <lrcsml:option name="daemon"/>
    <lrcsml:option name="ftp"/>
    <lrcsml:option name="kern"/>
    <lrcsml:option name="local0"/>
    <lrcsml:option name="local1"/>
    <lrcsml:option name="local2"/>
    <lrcsml:option name="local3"/>
    <lrcsml:option name="local4"/>
    <lrcsml:option name="local5"/>
    <lrcsml:option name="local6"/>
    <lrcsml:option name="local7"/>
    <lrcsml:option name="lpr"/>
    <lrcsml:option name="mail"/>
    <lrcsml:option name="news"/>
    <lrcsml:option name="syslog"/>
    <lrcsml:option name="user"/>
    <lrcsml:option name="uucp"/>
    <lrcml:param name="lr_logging_facility">local2</lrcml:param>
  </lrcsml:select>

  <lrcsml:string name="lr_logging_tag" section="operation">
    <lrcsml:summary>Which syslog program identifier to use</lrcsml:summary>
    <lrcsml:description>
      <para>The standard UNIX syslog daemon allows you to supply an identifier
        with which each Lire-generated log line will be marked. It's
        recommended that you use a short string without any spaces, for
        example `lire'.</para>
    </lrcsml:description>
    <lrcml:param name="lr_logging_tag">lire</lrcml:param>
  </lrcsml:string>

  <lrcsml:executable name="lambda_path" section="programs">
    <lrcsml:summary>Path to Lambda</lrcsml:summary>
    <lrcsml:description>
      <para>To generate DVI, PostScript or PDF reports you need Lambda
        which is the Omega version of LaTeX. It is bundled with the
        TeTeX distribution since version 0.9. See the User Manual for
        download locations.
      </para>
    </lrcsml:description>
    <lrcml:param name="lambda_path">/usr/local/bin/lambda</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="odvips_path" section="programs">
    <lrcsml:summary>Path to odvips</lrcsml:summary>
    <lrcsml:description>
      <para>To generate PostScript or PDF reports you need odvips
        which is the Omega version of dvips. It is bundled with the
        TeTeX distribution since version 0.9. See the User Manual for
        download locations.
      </para>
    </lrcsml:description>
    <lrcml:param name="odvips_path">no</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="ps2pdf_path" section="programs">
    <lrcsml:summary>Path to ps2pdf</lrcsml:summary>
    <lrcsml:description>
      <para>To generate PDF reports you need ps2pdf. This is part of
        the Ghostscript distribution. See the User Manual for download
        locations.
      </para>
    </lrcsml:description>
    <lrcml:param name="ps2pdf_path">no</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="gzip_path" section="programs">
    <lrcsml:summary>Path to the gzip(1) program.</lrcsml:summary>
    <lrcml:param name="gzip_path">/usr/bin/gzip</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="tar_path" section="programs">
    <lrcsml:summary>Path to the tar(1) program.</lrcsml:summary>
    <lrcml:param name="tar_path">/usr/bin/tar</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="sendmail_path" section="programs">
    <lrcsml:summary>Path to the sendmail(1) program.</lrcsml:summary>
    <lrcml:param name="sendmail_path">/usr/sbin/sendmail</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="ploticus_path" section="programs">
    <lrcsml:summary>Path to the ploticus(1) program.</lrcsml:summary>
    <lrcml:param name="ploticus_path">no</lrcml:param>
  </lrcsml:executable>

  <lrcsml:executable name="ghostscript_path" section="programs">
    <lrcsml:summary>Path to the gs(1) program.</lrcsml:summary>
    <lrcml:param name="ghostscript_path">no</lrcml:param>
  </lrcsml:executable>

  <lrcsml:command name="tai64nlocal_name" section="programs">
    <lrcsml:summary>Name of the tai64nlocal(1) program.</lrcsml:summary>
    <lrcsml:description>
      <para>Some log files, particularly those left
        by programs written by professor D.J. Bernstein, use a timestamping
        format called tai64n which represents points in time in nanosecond
        precision using the TAI timebase. This program is required to do the
        conversion of TAI seconds to UTC seconds. For more information, visit
        <ulink url="http://cr.yp.to/libtai/tai64.html">DJB's website</ulink>.
        Specifying a full path is optional but recommended. If you're not
        processing any log files using this format (like qmail or djbdns), you
        don't have to touch this value: it is ignored by Lire in this
        case.</para>
    </lrcsml:description>
    <lrcml:param name="tai64nlocal_name"></lrcml:param>
  </lrcsml:command>

  <lrcsml:directory name="lr_spool_dir" section="responder">
    <lrcsml:summary>Autoresponder input spool</lrcsml:summary>
    <lrcsml:description>
      <para>The Lire autoresponder modules extracts
        log file attachments from email messages, processes the
        log files and e-mails the resulting report back to the
        sender. When the responder is enabled, it will look in
        this directory for incoming email messages. See the Lire
        User Manual for information on configuring email delivery
        to this directory.</para>
    </lrcsml:description>
    <lrcml:param name="lr_spool_dir">/usr/local/var/spool/lire</lrcml:param>
  </lrcsml:directory>

  <lrcsml:integer name="lr_spool_interval" section="responder">
    <lrcsml:summary>Autoresponder spool check interval</lrcsml:summary>
    <lrcsml:description>
      <para>When the responder is enabled, it will often check the spool
        directory for incoming email messages. You can enter the frequency in
        minutes here.</para>
    </lrcsml:description>
    <lrcml:param name="lr_spool_interval">300</lrcml:param>
  </lrcsml:integer>

  <lrcsml:boolean name="lr_archive" section="responder">
    <lrcsml:summary>Should submissions be archived?</lrcsml:summary>
    <lrcsml:description>
      <para>When this parameter is set, the
        Responder will save each submitted message to the directory
        specified in the '<varname>lr_archive_dir</varname>' parameter.
      </para>
    </lrcsml:description>
    <lrcml:param name="lr_archive">no</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:directory name="lr_archive_dir" section="responder">
    <lrcsml:summary>Location of the archive</lrcsml:summary>
    <lrcsml:description><para>If the `<varname>lr_archive</varname>'
        option is enabled, this is where the requests will be
        archived.</para>
    </lrcsml:description>
    <lrcml:param name="lr_archive_dir">/usr/local/var/lib/lire/data</lrcml:param>
  </lrcsml:directory>


  <lrcsml:file name="lr_mail_explanation" section="responder">
    <lrcsml:summary>Autoresponder explanation text</lrcsml:summary>
    <lrcsml:description>
      <para>This file is prepended to email messages
        that are sent back by the autoresponder.</para>
    </lrcsml:description>
    <lrcml:param name="lr_mail_explanation">/usr/local/etc/lire/explanation</lrcml:param>
  </lrcsml:file>

  <lrcsml:file name="lr_mail_disclaimer" section="responder">
    <lrcsml:summary>Autoresponder disclaimer text</lrcsml:summary>
    <lrcsml:description>
      <para>This file is appended to email messages
        that are sent back by the autoresponder.</para>
    </lrcsml:description>
    <lrcml:param name="lr_mail_disclaimer">/usr/local/etc/lire/disclaimer</lrcml:param>
  </lrcsml:file>

  <lrcsml:file name="lr_mail_signature" section="responder">
    <lrcsml:summary>Autoresponder disclaimer text</lrcsml:summary>
    <lrcsml:description>
      <para>This plain text file is appended to
        email messages that are sent back by the
        autoresponder.</para>
    </lrcsml:description>
    <lrcml:param name="lr_mail_signature">/usr/local/etc/lire/signature</lrcml:param>
  </lrcsml:file>

  <lrcsml:string name="lr_mail_from" section="responder">
    <lrcsml:summary>Email address to send report from.</lrcsml:summary>
    <lrcsml:description>
      <para>Email address in the "From" field of report emailed by the
        responder.</para>
    </lrcsml:description>
    <lrcml:param name="lr_mail_from" />
  </lrcsml:string> 

  <lrcsml:string name="lr_mail_reply_to" section="responder">
    <lrcsml:summary>Sets the Reply-To email header</lrcsml:summary>
    <lrcsml:description>
      <para>Email address where users of the responder should reply if
        different from the value set for "lr_mail_from".</para>
    </lrcsml:description>
    <lrcml:param name="lr_mail_reply_to"/>
  </lrcsml:string>

  <lrcsml:file name="unicode.tex" section="path">
    <lrcsml:summary>Path to the unicode.tex file</lrcsml:summary>
    <lrcml:param name="unicode.tex">/usr/local/share/lire/tex/unicode.tex</lrcml:param>
  </lrcsml:file>

  <lrcsml:list name="lr_schemas_path" section="path">
    <lrcsml:summary>Directories containing DLF schemas.</lrcsml:summary>
    <lrcsml:directory name="schemas"/>
    <lrcml:param name="lr_schemas_path">
      <lrcml:param name="schemas">~/.lire/schemas</lrcml:param>
      <lrcml:param name="schemas">/usr/local/share/lire/schemas</lrcml:param>
    </lrcml:param>
  </lrcsml:list>

  <lrcsml:list name="lr_filters_path" section="path">
    <lrcsml:summary>Directories containing filter
      specifications.</lrcsml:summary>
    <lrcsml:directory name="filters"/>
    <lrcml:param name="lr_filters_path">
      <lrcml:param name="filters">~/.lire/filters</lrcml:param>
      <lrcml:param name="filters">/usr/local/share/lire/filters</lrcml:param>
    </lrcml:param>
  </lrcsml:list>

  <lrcsml:list name="lr_reports_path" section="path">
    <lrcsml:summary>Directories containing report
      specifications.</lrcsml:summary>
    <lrcsml:directory name="reports"/>
    <lrcml:param name="lr_reports_path">
      <lrcml:param name="reports">~/.lire/reports</lrcml:param>
      <lrcml:param name="reports">/usr/local/share/lire/reports</lrcml:param>
    </lrcml:param>
  </lrcsml:list>

  <lrcsml:list name="lr_templates_path" section="path">
    <lrcsml:summary>Directories containing report
      configuration templates.</lrcsml:summary>
    <lrcsml:directory name="templates"/>
    <lrcml:param name="lr_templates_path">
      <lrcml:param name="templates">~/.lire/templates</lrcml:param>
      <lrcml:param name="templates">/usr/local/share/lire/templates</lrcml:param>
    </lrcml:param>
  </lrcsml:list>

  <lrcsml:list name="plugins_init_path" section="path">
    <lrcsml:summary>Directories containing plugin
      initializers.</lrcsml:summary>
    <lrcsml:description>
     <para>A list of directories which contain initialization scripts.
       These are short perl script that should register plugins with the
       Lire::PluginManager.</para>
    </lrcsml:description>
    <lrcsml:directory name="plugins"/>
    <lrcml:param name="plugins_init_path">
      <lrcml:param name="plugins">~/.lire/plugins</lrcml:param>
      <lrcml:param name="plugins">/usr/local/etc/lire/plugins</lrcml:param>
    </lrcml:param>
  </lrcsml:list>

  <lrcsml:file name="lr_old_address_file" section="path">
    <lrcsml:summary>Path to the old address.cf file.</lrcsml:summary>
    <lrcml:param name="lr_old_address_file">/usr/local/etc/lire/address.cf</lrcml:param>
  </lrcsml:file>

  <lrcsml:directory name="lr_old_convertors_dir" section="path">
    <lrcsml:summary>Path to the directory containing old style DLF
      converters.</lrcsml:summary>
    <lrcml:param name="lr_old_convertors_dir">/usr/local/libexec/lire/convertors</lrcml:param>
  </lrcsml:directory>

  <lrcsml:boolean name="lr_scale_numbers" section="report">
    <lrcsml:summary>Abbreviate numbers (Kb, Mb, ...)</lrcsml:summary>
    <lrcsml:description>
      <para>Makes Lire display numbers in
        a legible format. Decimal scales are used, so `1K' requests means
        `1000' requests.</para>
    </lrcsml:description>
    <lrcml:param name="lr_scale_numbers">no</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:boolean name="lr_scale_bytes" section="report">
    <lrcsml:summary>Abbreviate byte counts (Kb, Mb, ...)</lrcsml:summary>
    <lrcsml:description>
      <para>Makes Lire display byte counts in
        a legible format. Binary scales are used, so `1 Kb' means
        `1024 bytes'.</para>
    </lrcsml:description>
    <lrcml:param name="lr_scale_bytes">yes</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:boolean name="lr_scale_seconds" section="report">
    <lrcsml:summary>Abbreviate time units (minutes, hours,
      ...)</lrcsml:summary>
    <lrcsml:description>
      <para>Makes Lire display times in a legible format, using `m', `h' and
        `d' suffixes.</para>
    </lrcsml:description>
    <lrcml:param name="lr_scale_seconds">yes</lrcml:param>
  </lrcsml:boolean>

  <lrcsml:select name="lr_week_numbering" section="report">
    <lrcsml:summary>How are week numbers computed?</lrcsml:summary>
    <lrcsml:description>
      <para>With "W", week numbers range from 00 to 53, starting with the
        first Monday as the first day of week 01; with "U", week numbers range
        from 00 to 53, starting with the first Sunday as the first day of week
        01 and with "ISO", week numbers are computed according to ISO
        8601:1988, range 01 to 53, where week 1 is the first week that has at
        least 4 days in the current year, and with Monday as the first day of
        the week.</para> 
    </lrcsml:description>
    <lrcsml:option name="W"/>
    <lrcsml:option name="U"/>
    <lrcsml:option name="ISO"/>
    <lrcml:param name="lr_week_numbering">U</lrcml:param>
  </lrcsml:select>

  <lrcsml:string name="lr_logo" section="report">
    <lrcsml:summary>Which logo to display in the report
      headers?</lrcsml:summary>
    <lrcsml:description>
      <para>Some report output formats support the bundling of images (HTML,
        PDF, ...). It is then possible to associate a logo with those reports,
        such as the Lire logo (the default) or your company's, for
        example. This parameter can either be an image file on your local
        filesystem or an URL.</para>
    </lrcsml:description>
    <lrcml:param name="lr_logo">/usr/local/share/lire/html/lire.png</lrcml:param>
  </lrcsml:string>

  <lrcsml:string name="lr_logo_url" section="report">
    <lrcsml:summary>Which URI should be pointed to by the logo displayed
      in your report headers?</lrcsml:summary>
    <lrcsml:description>
      <para>Some report output formats support the handling of hyperlinks
        (HTML, PDF, ...). It is then possible to associate one with the logo
        to be displayed in your report headers. By default, this link points
        to the LogReport Foundation's website. If you don't want any link,
        set this field to an empty value.</para>
    </lrcsml:description>
    <lrcml:param name="lr_logo_url">http://www.logreport.org/</lrcml:param>
  </lrcsml:string>

  <lrcsml:string name="lr_html_css" section="report">
    <lrcsml:summary>Which CSS stylesheet should be used for your HTML reports
      ?</lrcsml:summary>
    <lrcsml:description>
      <para>It is now possible to customize the presentation of some elements
      of the HTML reports. The default's Lire CSS for HTML provides a good
      presentation but this option gives you the ability to use your own
      version.</para>
    </lrcsml:description>
    <lrcml:param name="lr_html_css">/usr/local/share/lire/html/lire-html.css</lrcml:param>
  </lrcsml:string>

  <lrcsml:string name="lr_chart_font" section="report">
    <lrcsml:summary>Font to use in charts</lrcsml:summary>
    <lrcsml:description>
      <para>Use this option to control the font that
        Ploticus will use to render characters. The available fonts
        depend on the image format chosen. Consult the Ploticus
        documentation for all the details.</para>
    </lrcsml:description>
    <lrcml:param name="lr_chart_font"/>
  </lrcsml:string>

  <lrcsml:string name="lr_latex_include" section="report">
    <lrcsml:summary>LaTeX Customization</lrcsml:summary>
    <lrcsml:description>
      <para>This option can be used to include LaTeX code that will
        be inserted in LaTeX formatted reports (this also include the 
        DVI, PS and PDF output formats). This can be use to custommize
        headers or fonts.
      </para>
    </lrcsml:description>
    <lrcml:param name="lr_latex_include"/>
  </lrcsml:string>

  <lrcsml:list name="import_jobs">
    <lrcsml:summary>ImportJobs configured in the current
      store.</lrcsml:summary>
    <lrcsml:object name="import_job" class="Lire::ImportJob" label="name">
      <lrcsml:string name="name">
        <lrcsml:summary>Name for the ImportJob.</lrcsml:summary>
        <lrcsml:description>
          <para>It is needed to identify the import jobs for Lire to process
            them properly. Set this variable to do so.</para>
        </lrcsml:description>
      </lrcsml:string>

      <lrcsml:select name="period">
        <lrcsml:summary>How often to import the log into the
          store</lrcsml:summary>
        <lrcsml:description>
          <para>Each ImportJob can have its own import period. Monthly and
            yearly cron jobs are run on the first day of the month or year.
            Weekly cron jobs are run on monday morning 00:00.
          </para>
        </lrcsml:description>
        <lrcsml:option name="hourly"/>
        <lrcsml:option name="daily"/>
        <lrcsml:option name="weekly"/>
        <lrcsml:option name="monthly"/>
        <lrcsml:option name="yearly"/>
      </lrcsml:select>

      <lrcsml:dlf-converter name="service">
        <lrcsml:summary>Type of the logfile.</lrcsml:summary>
        <lrcsml:description>
          <para>This parameter describes the service by which the specified
            logfile was produced. This parameter is mandatory since Lire has
            no way of deducing it otherwise.</para>
        </lrcsml:description>
      </lrcsml:dlf-converter>

      <lrcsml:string name="log_file">
        <lrcsml:summary>Path to the log file that will be
          processed.</lrcsml:summary>
        <lrcsml:description>
          <para>This is the path to the log file which should be imported.
            That path is actually a pattern which accepts strftime(3) format
            specifications which will be interpolated before importing the log.
            For example,
            <literal>/var/log/apache/corp.com%Y%m%d.log.gz</literal> will be
            replaced with something like
            <literal>/var/log/apache/corp.com20040124.log.gz</literal>.
          </para>
        </lrcsml:description>
      </lrcsml:string>

      <lrcsml:string name="log_encoding">
        <lrcsml:summary>Encoding used in the log file.</lrcsml:summary>
        <lrcsml:description>
          <para>Use this parameter in the case where your
            log file is in a different encoding than the system's
            default.</para>
        </lrcsml:description>
      </lrcsml:string>

      <lrcsml:string name="filter">
        <lrcsml:summary>Filter to apply to the log file.</lrcsml:summary>
        <lrcsml:description>
          <para>Some log files need preprocessing before they
            can be fed to the main Lire engine. 
            A common filter is <command>zcat</command> to decompress files
            that were compressed using <command>gzip</command> or
            <command>compress</command>.
          </para>
        </lrcsml:description>
      </lrcsml:string>

    </lrcsml:object>
  </lrcsml:list>
  
  <lrcsml:list name="report_jobs">
    <lrcsml:summary>ReportJobs configured in the current
      store.</lrcsml:summary>
    <lrcsml:object name="report_job" class="Lire::ReportJob" label="name">
      <lrcsml:string name="name" valid-re="^[\w-]+$">
        <lrcsml:summary>Name of the ReportJob.</lrcsml:summary>
        <lrcsml:description>
          <para>It is needed to identify the report jobs for Lire to
            process them properly. Set this variable to do so. NOTE:
            This name should contains only alphanumeric characters,
            hyphens or underscores.</para>
        </lrcsml:description>
      </lrcsml:string>

      <lrcsml:dlf-schema name="superservice" obsolete="1">
        <lrcsml:summary>Select the superservice for this
          report.</lrcsml:summary>
        <lrcsml:description>
          <para>Lire gathers data by "superservices", which in short are types
            of "services". This option let you select the type of data that
            this report job should process, whether it is database, web,
            email data or any other type available in this list.</para>
        </lrcsml:description>
      </lrcsml:dlf-schema>

      <lrcsml:list name="schedules">
        <lrcsml:summary>Report Generation Schedules</lrcsml:summary>
        <lrcsml:description>
          <para>ReportJob's must be generated on one or more periods, each of
            which have to be described as a "report schedule". A report
            schedule let you specify which report should be formatted,
            following which configuration at which frequency.</para>
        </lrcsml:description>

        <lrcsml:object name="schedule" label="period"
          class="Lire::ReportSchedule">
          <lrcsml:select name="period">
            <lrcsml:summary>How often you want to generate the
              report</lrcsml:summary>
            <lrcsml:description>
              <para>This is the frequency by which this report schedule will
                be executed. The value for this parameter can be either
                "hourly", "daily", "weekly", "monthly" or "yearly". NOTE: to
                generate weekly, monthly or yearly reports, you need to have at
                least one daily report schedule if you often clean your DLF
                store. This is because Lire uses the merging algorithm when it
                can't find the data in the DLF database and only daily reports
                are considered in this case.</para>
            </lrcsml:description>

            <lrcsml:option name="hourly"/>
            <lrcsml:option name="daily"/>
            <lrcsml:option name="weekly"/>
            <lrcsml:option name="monthly"/>
            <lrcsml:option name="yearly"/>
          </lrcsml:select>

          <lrcsml:file name="report_cfg" obsolete="1">
            <lrcsml:summary>Report configuration file to use.</lrcsml:summary>
            <lrcsml:description>
              <para>Report configuration files are text files with a specific
                syntax designed to describe the type of information displayed
                in the report and the presentation thereof. Lire provides a
                typical configuration file for each superservice but you can
                also create your own, tailored to your needs.</para>
            </lrcsml:description>
          </lrcsml:file>

          <lrcsml:reference name="report_config" index="store_report_configurations">
            <lrcsml:summary>Report configuration.</lrcsml:summary>
            <lrcsml:description>
              <para>Select the report configuration that should be
                used for this schedule.</para>
            </lrcsml:description>
          </lrcsml:reference>

          <lrcsml:list name="output_jobs">
            <lrcsml:summary>List of OutputJobs</lrcsml:summary>
            <lrcsml:description>
              <para>When reports are scheduled, they can be output in
                different forms and different formats. This is what OutputJobs
                are about and you can configure several of them for the same
                schedule.</para>
            </lrcsml:description>

            <lrcsml:object name="output_job" label="name"
              class="Lire::OutputJob">
              <lrcsml:string name="name">
                <lrcsml:summary>Identifier</lrcsml:summary>
                <lrcsml:description>
                  <para>An identifier for this output job.</para>
                </lrcsml:description>
              </lrcsml:string>
              <lrcsml:output-format name="format">
                <lrcsml:summary>File type of the generated
                  report</lrcsml:summary>
                <lrcsml:description>
                  <para>Lire can format its reports in a variety of
                    ways, from a simple plain text file to a pretty PDF file
                    suitable for printing.
                  </para>
                </lrcsml:description>
              </lrcsml:output-format>

              <lrcsml:plugin name="destination">
                <lrcsml:summary>The target type of the output
                  report.</lrcsml:summary>
                <lrcsml:description>
                  <para>Lire can either save its formatted report as a file on
                    a filesystem or send it by email to a chosen address. This
                    option lets you configure this.</para>
                </lrcsml:description>
                <lrcsml:option name="file">
                  <lrcsml:summary>Store the formatted output into a
                    file.</lrcsml:summary>
                </lrcsml:option>
                <lrcsml:option name="email">
                  <lrcsml:summary>Send the formatted output via
                    email.</lrcsml:summary>
                </lrcsml:option>
              </lrcsml:plugin>
            </lrcsml:object>
          </lrcsml:list>
        </lrcsml:object>
      </lrcsml:list>
    </lrcsml:object>
  </lrcsml:list>

  <lrcsml:list name="reports">
    <lrcsml:summary>Report Configurations</lrcsml:summary>
    <lrcsml:description>
      <para>List of ReportConfig objects used by this store.</para>
    </lrcsml:description>
    <lrcsml:report-config name="report_cfg">
      <lrcsml:summary>Report Configuration</lrcsml:summary>
      <lrcsml:description>
        <para>Defines a report that can be used in the report job. A
          report contains one or more section.
        </para>
      </lrcsml:description>
    </lrcsml:report-config>
  </lrcsml:list>

  <lrcsml:dlf-streams name="streams_config">
    <lrcsml:summary>DlfStreams configuration</lrcsml:summary>
      <lrcsml:description>
        <para>This configuration list contains configuration for each
         DlfStreams in the store.</para>
      </lrcsml:description>
  </lrcsml:dlf-streams>

  <lrcsml:record name="file_properties">
    <lrcsml:summary>Options specific to the chosen destination
      file.</lrcsml:summary>
    <lrcsml:description>
      <para>This let you configure the different attributes (currently only
        one) for the generated file.</para>
    </lrcsml:description>

    <lrcsml:string name="file">
      <lrcsml:summary>File template for the report job.</lrcsml:summary>
      <lrcsml:description>
        <para>This is a file name template that may contain strftime(3)
          interpolation.</para>
      </lrcsml:description>
    </lrcsml:string>
  </lrcsml:record>

  <lrcsml:record name="email_properties">
    <lrcsml:string name="subject">
      <lrcsml:summary>Subject of email containing the report.</lrcsml:summary>
      <lrcsml:description>
        <para>This let you specify the subject that will appear in the
          generated emails, as a way of identifying the received
          reports.</para>
      </lrcsml:description>
    </lrcsml:string>

    <lrcsml:list name="emails">
      <lrcsml:summary>Email addresses to mail report to.</lrcsml:summary>
      <lrcsml:description>
        <para>A report output can be emailed to many addresses at the same
          time. Fill in this list with those. At least one address is
          required.</para>
      </lrcsml:description>

      <lrcsml:string name="email"/>
    </lrcsml:list>
  </lrcsml:record>

  <!-- Obsolete parameters kept to prevent errors triggered by
       old configuration file. -->
  <lrcsml:string name="lr_old_service_aliases_file" summary="Obsolete"
    obsolete="1"/>

  <lrcsml:list name="lr_sql_archive" summary="Obsolete" obsolete="1">
    <lrcsml:string name="service" summary="Obsolete"/>
  </lrcsml:list>

  <lrcsml:integer name="lr_sql_max_size" summary="Obsolete" obsolete="1"/>

  <lrcsml:string name="lr_dbi_uri" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbi_user" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbi_passwd_file" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="zip_path" summary="Obsolete" obsolete="1"/>

  <lrcsml:string name="lr_period" summary="Replaced by logsource."
    obsolete="1"/>
  <lrcsml:string name="lr_service" summary="Replaced by logsource." 
    obsolete="1"/>
  <lrcsml:string name="log_file" summary="Replaced by logsource."
    obsolete="1"/>
  <lrcsml:string name="lr_filter" summary="Replaced by logsource."
    obsolete="1"/>
  <lrcsml:string name="lr_output_format" summary="Replaced by report_output."
    obsolete="1">
    <lrcml:param name="lr_output_format">txt</lrcml:param>
  </lrcsml:string>

  <lrcsml:string name="lr_mail_to" summary="Replaced by report_output." 
    obsolete="1"/>
  <lrcsml:string name="lr_mail_subject" summary="Replaced by report_output." 
    obsolete="1"/>
  <lrcsml:string name="lr_images" summary="Replaced by report_output." 
    obsolete="1"/>
  <lrcsml:string name="lr_user_level" summary="Obsolete" obsolete="1">
    <lrcml:param name="lr_user_level">advanced</lrcml:param>
  </lrcsml:string>

  <lrcsml:string name="lr_dbk_html_xsl" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbk_html_onepage_xsl" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbk_xhtml_xsl" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbk_xhtml_onepage_xsl" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbk_fo_xsl" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="pdfxmltex_path" summary="Obsolete" obsolete="1" />
  <lrcsml:string name="lr_xslt_processor" summary="Obsolete" obsolete="1" />
  <lrcsml:string name="lr_pdf_style" summary="Obsolete" obsolete="1" />
  <lrcsml:string name="lr_image_format" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_image_style" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_image_resolution" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="xsltproc_path" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="jade_path" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="pdfjadetex_path" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="xmlcatalog_path" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbk_xml_dtd" summary="Obsolete" obsolete="1"/>
  <lrcsml:string name="lr_dbk_print_stylesheet" summary="Obsolete" obsolete="1"/>

  <lrcsml:record name="pdf_properties" summary="Obsolete"  obsolete="1">
    <lrcsml:string name="charts" summary="Obsolete" obsolete="1"/>
  </lrcsml:record>

  <lrcsml:list name="lr_converters_init_path" obsolete="1">
    <lrcsml:summary>Directories containing DLF converter initializers (obsolete).</lrcsml:summary>
    <lrcsml:description>
      <para>This variable is superseded by <varname>plugins_init_path</varname>.</para>
    </lrcsml:description>
    <lrcsml:directory name="converters"/>
    <lrcml:param name="lr_converters_init_path">
      <lrcml:param name="converters">~/.lire/converters</lrcml:param>
      <lrcml:param name="converters">/usr/local/etc/lire/converters</lrcml:param>
    </lrcml:param>
  </lrcsml:list>

</lrcsml:config-spec>
<!--
Local Variables:
mode: xml
sgml-indent-step: 2
End:
-->
