We can stop generating the dtd in every nightly build, because the dtd being generated is not being maintained. Just check in the latest dtd to svn somewhere, then take out the part of the nightly build that builds the dtd.

Relevant email thread:
Our current dtd is better than nothing at all, although, since it is not being maintained, you could save yourself some trouble by generating it once and just checking it in to svn.

On 2007-12-11, at 13:10 EST, Benjamin Shine wrote:


Right, but is our current DTD at all worthwhile? If it's not at all worthwhile, we shouldn't bother building it at all ever.

On Dec 11, 2007, at 5:21 AM, David Temkin wrote:

We get more requests for a DTD (by far) than for anything else. I can't speak to the technical merits of either -- just reflecting what I hear from the outside. But it does seem like more editors support DTDs than other options... and that should probably be the driver here...


On Dec 11, 2007, at 6:13 AM, P T Withington wrote:

Surely the Nexb guys will have am opinion? We should MAE what they can use.

On Dec 10, 2007, at 19:05, "Henry Minsky" <henry.minsky@gmail.com> wrote:

I don't know, but I'd like to make a new processs to generate a DTD or
whatever is
actually useful, directly from the in-core schema. It should be pretty
straightforward, but I just
don't know what it is we want to be generating.

On Dec 10, 2007 6:47 PM, Benjamin Shine <ben@laszlosystems.com> wrote:

Do we still use the dtd for *anything*?
Is it *ever* worthwhile to generate it using our current rng2dtd step
in WEB-INF/schema ?