This file is indexed.

/usr/share/doc/lire/dev-manual/ch01s04.html is in lire-devel-doc 2:2.1.1-2.1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Report Generation</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Lire Developer's Manual"><link rel="up" href="ch01.html" title="Chapter 1. Architecture Overview"><link rel="prev" href="ch01s03.html" title="Log Analysis"><link rel="next" href="ch01s05.html" title="Report Formatting and Other Post-Processing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Report Generation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><th width="60%" align="center">Chapter 1. Architecture Overview</th><td width="20%" align="right"> <a accesskey="n" href="ch01s05.html">Next</a></td></tr></table><hr></div><div class="section" title="Report Generation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sect:generation"></a>Report Generation</h2></div></div></div><p>Once you have all this data, it's time to generate some
	  useful reports out of it. Lire's framework includes a
	  generic report builder. What <span class="application">Lire</span> calls a
	  <em class="firstterm">report</em> is actually a
	  <span class="emphasis"><em>collection</em></span> of what one may understand
	  as reports; <span class="application">Lire</span> however speaks about a
	  <em class="firstterm">subreports</em>. For example, the proxy's
	  superservice report will contain subreports about the top
	  visited sites, another subreport on the cache hit ratio, as
	  well as several others. The subreports are defined using the
	  <em class="firstterm">Report Specification Markup Language</em>.
	  This markup language contains elements for several things:
	  information regarding the schema on which it operates;
	  descriptions that should be included in the generated report
	  to help in the interpretation of the data; parameters that
	  can be used to modify the generated report (for example, to
	  generate a top 20 subreport instead of a top 10); a filter
	  that selects the records that will be used for the
	  subreport; and finally the operations that make up the
	  subreport: grouping, summing, counting, etc. The report
	  markup language covers most simple needs and there is an
	  extension element as well as an API that can be used to hook
	  in more fancy computations.  There are no subreport
	  specifications in the current distribution that make use of
	  this feature yet, however. You can see an overview of this
	  process in the <a class="xref" href="ch01s04.html#fig:flow-generation" title="Figure 1.4. Report Generation Process">Figure 1.4, &#8220;Report Generation Process&#8221;</a> figure.
	</p><div class="figure"><a name="fig:flow-generation"></a><p class="title"><b>Figure 1.4. Report Generation Process</b></p><div class="figure-contents"><div align="center"><img src="flow-generation.png" align="middle" alt="Report Generation Process"></div></div></div><br class="figure-break"><p>The generated report is another XML file that uses
	  another markup language, this time called the Lire's Report
	  Markup Language. An actual report contains the help
	  descriptions from the report specifications, information on
	  the subreport specifications used, as well as the actual
	  subreport's data.Using another intermediary XML file as
	  output format makes all sort of things possible in the
	  formatting and post-processing stage.
	</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Log Analysis </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Report Formatting and Other Post-Processing</td></tr></table></div></body></html>