From: Jason L. <jl...@me...> - 2002-10-21 23:44:58
|
In response to: Devin Jones <dev...@ya...> 10/21/02 17:27 PM Yes, that's right. I couldn't have said it better myself. Do you have any suggestions/criticisms? I'm not sure yet what the contents of the descriptor file will be, but you are correct that it will need to specify the commands to transform the file from native to XML and back. We could also provide ways for descriptor files to "extend" another descriptor file. So, for example: inifile descriptor file (example) - defines a "readcommand" to read the configuration file and generate an XML - defines a "writecommand" to write the configuration from XML - defines that a configuration node of this type should contain a property called "config file" that specifies the file that is to be parsed samba descriptor file (we really like using Samba as an example) - it extends `inifile' - defines a default "config file" property of "/etc/samba/smb.conf" - defines descriptions, data types, and default values for properties - defines a "validate" command to check a configuration As we work out these details, I want to post them to our "System Requirements Specification", which is a document that attempts to describe very precisely the various capabilities of the system. The requirements specification is a Docbook-format file available in CVS under website/docs/requirements/requirements.sgml. Justin has posted this to the http://config4gnu.sourceforge.net website. Jason |