[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Use of XML ?
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: firstname.lastname@example.org
- Date: Thu, 02 Aug 2001 10:53:57 -0500
Something to keep in mind, the model of contract-based
communication espoused in countless articles on XML,
WSDL, SOAP, etc. isn't new or even novel to markup systems.
There is literature on all of this in the CALS days
related to the C3I model of military command, control
and communications. In C3I, the central problem is
not efficiency; it is mission success given capability.
Cost is relative to criticality.
To work out some of the probable results, one looks
at the contrasting styles of the cold war militaries,
eg, Soviet and American, and compares understands where
and how each was successful. One can have a *loosely coupled*
chain of command with varying degrees of autonomy and
cohesion, and that works very well for some situations.
In other situations, say where coordination of assets
and effort are required, one can optimize efficiency by
reducing the autonomy, or one can increase the assets
and accept losses as the cost of achieving the mission.
The "pioneers" of XML should study these models. There
are costs in loose contracts and costs in tight contracts.
The question is one of what kinds and types of losses can
be sustained given availability and sustainment costs.
The Korean conflict (1950-53) is particularly illuminating.
Intergraph Public Safety
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h