Richard Light writes:
> >obviously has problems. Maybe a parameter entity with a switch, and a
> >recommendation to switch it to IDREF for new documents?
> That approach would get my vote. Surely TEI folks won't have a problem
> with parameter entities ...
But think of the precedent it sets. If you permit this, there are a
thousand other places where a similar request might be made.
I strongly agree with Francois: any project should consider writing
its own post-DTD validation processor (XSLT makes this easy). This is
- DTDs only do one type of validation, and that fairly weakly in
- I bet most projects have `private' constraints; or things which are
warnings rather than errors. For instance, I want an author on my
web site to get an email warning if (s)he checks in a document
with a table containing more than 10 columns.