report configs

[Francis J. Lacoste]

[modified resend by wsl]

On dim, 2003-06-08 at 09:33, Wessel Dankers wrote:
> 
> Cons:
> • The filtering scope is not explicit (it's another layer on top of the XML
>   structure, in a sense).
> • There's still no differentiation between different schemata. (But that
>   can be added).
> 

Hmm,

Thinking about it a little more, there is an issue that may make it less
interesting to use the existing <param> element to store the report
configuration. 

The "subreport" elements will need to be dictionary which contains some
static components to use their metadata:

<param name="nonrec_top-requesting-hosts"> <!-- This is an ID now -->
   <param name="schema">dns</param> <!-- The schema to use -->
   <param name="report-spec">top-requesting-hosts</param> <!-- The name
-->
   <param name="params"> <!-- Container to hold set the specification's
parameters -->
      <param name="names_to_show">10</param>
      ...
   </param>
</param>

An dedicated XML syntax would be more synthetic:

<subreport id="nonrec_top-requesting-hosts" schema="dns" 
           report-spec="top-requesting-hosts">
  <param name="names_to_show>10</param>

  <!-- Or even 
   <param name="names_to_show" value="10"/>
   -->
</subreport>

But again, is it really worth it to define yet-another XML schema?


Francis J. Lacoste

-- 
Francis J. Lacoste              . .           http://www.logreport.org
/^LogReport$/               . .               flacoste at logreport.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.logreport.org/pipermail/development/attachments/20030609/b604f11f/attachment.bin