• To: xml-dev@l...
• Subject: Client XML vs Message XML
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Thu, 22 Sep 2005 11:20:36 -0500

At some point, it is necessary to confront the 
specification and standards authors and make 
them understand that object-oriented client 
design and message or document (really, say 
data) XML design aren't the same thing and 
are bad practice to conflate.  The results 
of conflating these are very big honkin' 
schemas that beggar the implementation, 
don't get market traction, and cause the 
unwary agency to spend a lot of taxpayer 
dollars on projects that don't get good 
results fast.

XML doesn't know about semantics or object-oriented 
objects, and it's a crummy way to declare 
a client specification for much beyond the 
bits on the wire.  Using it to advance the cause 
of object-oriented databases ahead of their time 
is a profoundly bad idea.  It just makes the pig mad.

len

• Follow-Ups:
  • RE: Client XML vs Message XML
    • From: "Darryl Champagne" <dgc03052@a...>

• Prev by Date: RE: Wrapping Scripted Media in RSS: Secure?
• Next by Date: RE: Client XML vs Message XML
• Previous by thread: RE: Wrapping Scripted Media in RSS: Secure?
• Next by thread: RE: Client XML vs Message XML
• Index(es):
  • Date
  • Thread