[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: SOAP Message Transmission Optimization Mechanism

• To: xml-dev@l...
• Subject: RE: SOAP Message Transmission Optimization Mechanism
• From: "Simon St.Laurent" <simonstl@s...>
• Date: Tue, 22 Jul 2003 13:02:24 -0400
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE022DC612@h...>

clbullar@i... (Bullard, Claude L (Len)) writes:

>At least it is easy to see now how SGML became as 
>complex as it did over time.  What doesn't get 
>put into XML shows up in the applications.  It 
>will be fun as some of us get closer to retirement 
>and watch the next generation of "we can do this 
>simpler and better".
>
>Cars and jets never get simpler overall.  Why 
>do people believe software should?

In general, I don't expect it should.  In this case, I think it's funny,
because a group threw away all those features, claiming they were too
obscure, and then reinvented them in a form that seems even more
obscure.

Reinventing the wheel is fine, as long as you come up with a better
wheel.  I think XML 1.0 (and perhaps XSLT 1.0) set a standard for
improving wheels by simplification that hasn't been matched since.

-- 
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org

• References:
  • RE: SOAP Message Transmission Optimization Mechanism
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: An approach to describing the relationships betweenunits-of-measure
• Next by Date: Simplification and Composability (RE: SOAP Message Transmission Optimization Mechanism)
• Previous by thread: RE: SOAP Message Transmission Optimization Mechanism
• Next by thread: Re: An approach to describing the relationships betweenunits-of-measure
• Index(es):
  • Date
  • Thread