[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: is that a fork in the road?
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: Ken North <firstname.lastname@example.org>
- Date: Tue, 06 Mar 2001 08:21:12 -0600
The bet-your-business folks will make sure their vendors sell them the
and see to it that the consultants involved are
aware of the fact that business applications are
harder to build, and quite a bit more complex than
the road better traveled these days. That is how
competition works. The smart competitors sell more product.
It isn't complexity we have to worry about; it
is systems failure because of experiments that get
into production. We have the current mess because
people believed simple was better when what they
were seeing was third generation applications.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Ken North [mailto:email@example.com]
> XML Schema is an obvious step because it adds type information.
It's true the number of XML specs raises the complexity of application
development, but many organizations are doing much more with XML than rating
If you're building a mission critical system ("bet-your-business"), you're
going to want to exploit constraints and type-checking. You also want to
know that answers coming back from queries are correct -- the fundamental
motivation for a formal approach using a data model and query algebra.