On 26 Apr 2007 at 11:57, Darien Hager wrote: > Brainstorming idea: XML with Schema validation?
Please no. > * The config would be a plain file and portable. > * It would be relatively easy for admins to write tools to read and > write from the config. > * With a library that supports validation, XML schemas can do a lot > of the hard work of checking data values and structure. > * Validation by XML schema can check referential integrity and > uniqueness constraints. > * Rules and situations for quoting and escaping slashes and spaces > etc. are fairly well defined. > * But would be more verbose. > > Now, I'm not in the "XML for everything" camp by any means, but in > this particular situation it may be worth looking into. Disclosure: > I'm reading through a book on XML schemas, so I have a minor bias. > If > this seems "worth exploring" to Bacula devs, I'd be happy to help. Fruity is the configuration tool for Nagios. I suggest that such a tool for Bacula would be useful too. However, all configuration files should be plain text. Much like what Fruity does. -- Dan Langille two conferences, one trip, great value: May 2007 BSDCan - The BSD Conference - http://www.bsdcan.org/ PGCon - The PostgreSQL Conference - http://www.pgcon.org/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users