The closest thing to a standard XML description is in RFC 3195, in the
Cooked profile. But it looks like you don't like that. We have created
our own format for storage, as I think have others. I would try to stick
with the same names used in 3195 - don't make the mistake we made to use
others... It can become very confusing, even in your own codebase ;)

Chris, while I never thought about this, would this make up for a new
ID?

Rainer

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 13, 2003 1:00 PM
> To: [EMAIL PROTECTED]
> Subject: XML for syslog? (off-topic)
>
>
> Hello,
>
> A small (off-topic) question,
>
> Does anybody know wheter there is a XML description for
> syslog? Kind of
> (defacto) standard one.
>
> I don't mean the XML used in e.g syslog-relable (which adds fields).
> But one that can be used to "store" rfc3164 messages, after
> spitting them in the
> fields as decribed in the syslog standards. So, something
> like: (psuedo
> notation)
>    <syslog>
>     <PRI><fac>8</fac><sev>5</sev></PRI>
>     <HEADER>
>          <timestamp> ....
>          <hostname> ....
>          <TAG progname="aProg">/PATH/To/AProg[1,2]</TAG>
>     </HEADER>
>    ....
>
> As you see, I is easy to create one. But, it would be nice to
> have a standandard
> one.
>
> Thanks
>
>
> ALbert
>
>
>
>
>
>


Reply via email to