Hello, On Apr 30 15:51 Lukas Ocilka wrote (excerpt):
Not having XML makes it human-readable and reduces the cost of reading/writing.
I like simplistic doctrine very much - it makes things so easy! I neither state XML is the right solution to replace YCP data nor do I state usual XML data is well human-readable but I would appreciate it if decisions that must be future-proof are based on thorough analysis and not on individual personal preferences. For example if import/export of YaST data is of importance (or will become of importance in the future), XML+DTD may have advantages. In this case it could be good when there is only one single data format that is also used for import/export. One can include the DTD inline in the XML so that such an XML+DTD document is one single piece of data that can be sent anywhere (exported), changed there and validated there, and then re-imported. Perhaps YaST modules that run on host A may like to export configuration data to another host where the configuration data can be changed and validated and then the other host sends the changed configuration data back to the YaST module on host A where the imported data gets validated again (not only syntactically validated again but also validated against the actual environment on host A) and finally the changed configuration could be applied on host A. If XML with inline DTD would be used to store and exchange YaST data, arbitrary XML-compatible tools on arbitrary operating systems could be used to change any YaST data form any YaST version in a vaild way. Scary hint: Running a frontend on a Windows management host that communicates this way with various YaST backend modules running on various Linux hosts. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org