Pity that's not XML, though.
It was in XML1.0 and is still widely used. I agree that XML Schema is the current way, but it is very, although more flexible and powerful. It can be used for the same things, though.

There goes scriptability and so many of the lovely Unix administration tools we've grown to love over the past few decades.
I'm not sure why. If we want the validation of, say, a DTD, then we need a (possibly) new tool for that. What validates crontab, for example? When I build a major app, I often build validation tools for the config files. I find it easier to use XML and a DTD than going through the difficulty of writing my own parsing and validating code.

Yes, I do understand and agree that the application needs to validate all input. I just like the idea of an external tool to do the first pass.


In reply to Re^5: Config Files Redux by traveler
in thread Config Files Redux by traveler

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.