On Fri, Jun 09, 2006 at 05:18:18PM -0400, James Carlson wrote: > Nicolas Williams writes: > > > Failing to produce those sorts of schema leaves you with just a > > > handful of code numbers plus free-form text wrapped prettily in XML. > > > > Each message could reference the schema/dtd that it conforms to... > > > > And existing MIBs could be re-used, perhaps. > > I await that MIB to XML converter. ;-}
There's an XML encoding for ASN.1. Thus such converters are feasible :) (Not that we have the necessary development tools in ON, mind you.) Also, nowadays DER encodings of XML schemas (FastInfoSet) is all the rage. Plus çhange... So maybe such convertions can be obviated altogether ;) > > Ew, BEEP. Only RFC3195 (Reliable Delivery for syslog) mentions XML or > > BEEP. The SYSLOG WG I-Ds make no mention of XML, much less BEEP. > > Oh! Someone else on this thread mentioned the reliable delivery > (syslogng) mode, and I thought you were also referring to that. > > The SYSLOG WG I-Ds are far less ambitious than that. I have no real > objection to those at all. Oh! Well then... But those deal in structured data also... Nico -- _______________________________________________ networking-discuss mailing list [email protected]
