[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: A simple guy with a simple problem
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: Tim Bray <firstname.lastname@example.org>, Sean McGrath <email@example.com>,firstname.lastname@example.org
- Date: Wed, 14 Mar 2001 13:42:20 -0600
So to ask as straight man:
Why does XML have a feature that permits
a "bad practice"?
2. Keeping the SGML experts happy?
3. A simple solution that has
complicated results if misapplied?
Not XML, but here is an interesting article
illustrating some results of bad practice
and what can happen if the simple
approach is preferred. (Try the simple
thing first and wait for the results...).
Stunning information. The architects tried to
make it easy then the world made it hard. So
they adjust but not before the damage is done.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Tim Bray [mailto:email@example.com]
The deeper and de facto bad practice is in having a
production system rely on defaults out of an external
DTD subset at all. Sean gives a good example of why
this is the case. Avoid this bad practice and you're