On Wed, 22 May 2002, Edward Avis wrote: > Well... yeah... I can't see any reason for expecting users to learn a > new markup format. XML is not ideal but it's widely known and *good > enough*, just like Perl. > > I suppose that using somebody else's markup language (YAML) is better > than making your own; then the wheel has been reinvented only once. But > still, it seems like gratuitous incompatibility. YAML ain't a markup language It's a data serialization language. And as long as no one intends that module authors actually _write_ it (by text editor) then I think it's just fine. > If there are technical reasons to avoid XML in favour of YAML, then > sure, go ahead. If it's just a question of taste, then I would suggest > that following an established standard is more important when the two > conflict. Just like you may not agree with perlstyle(1), but it works > out best when everyone follows it. Although this is just my 2c. XML requires more tools than I think Ken wants to require. At a minimum you'd need XML::Parser and possible some XML writer module. YAML is a simple all-in-one solution. > At this point it would almost be relevant for me to mention > <http://www.langdale.com.au/SOX/>. Eek, Python as XML, or XML as Python, or somehting like that ! -dave /*================== www.urth.org we await the New Sun ==================*/Thread Previous | Thread Next