tag:blogger.com,1999:blog-6193377.post7853660807220437007..comments2008-05-22T08:12:08.502+02:00Rainerhttp://www.blogger.com/profile/12765720626924376847noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6193377.post-48009609492051835042008-05-22T08:12:08.502+02:002008-05-22T08:12:08.502+02:00Appologize for my English...<BR/><BR/>I'll vote for XML.<BR/>Advantages:<BR/>- it's a widely usefull standard<BR/>- it's ready for automation configuration file verification by XML schema<BR/>- it's ready for automation compliance checking. I think that a different configuration file formats is a big problem for unix enviroments.Roman.Bhttp://www.blogger.com/profile/11726308046380121454noreply@blogger.comtag:blogger.com,1999:blog-6193377.post-65723970629199471402008-01-06T00:58:55.475+01:002008-01-06T00:58:55.475+01:00I'll vote for the json format. http://json.org/ The whole specification is one page compare to xml's 1400 pages. Actually, json BNF on the margin of a page is all one needs to understand it.delphi329http://www.blogger.com/profile/03017564350905119025noreply@blogger.com