The Artima Developer Community
Sponsored Link

Weblogs Forum
Standards: Doomed to Repeat Itself?

3 replies on 1 page. Most recent reply: Jun 20, 2003 9:11 PM by Carlos Perez

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 3 replies on 1 page
Carlos Perez

Posts: 153
Nickname: ceperez
Registered: Jan, 2003

Standards: Doomed to Repeat Itself? (View in Weblogs)
Posted: Jun 20, 2003 9:11 PM
Reply to this message Reply
Summary
George Santayana, a notable philosopher, coined the phrase, "Those who do not learn from history are doomed to repeat it." A study of the history of the CORBA standard reveals that for WebService standards, history is again repeating itself.
Advertisement

William Grosso has put together a presentation about the history of the CORBA standard.  The presentation focuses on the social and environmental factors that lead to the development of the CORBA standard.  There are a lot of parallels in CORBA's history and the emerging web services standards. 

CORBA defined in 1989, however vision based on the world of 1985. A world were PCs were just starting to emerge, businesses had dedicated machines with dedicated applications and the corporate network was still being built.  The presentation explains that CORBA had several high points:

  • Limited Goals
  • Standardized Language Mappings
  • Very Efficient Protocol
  • Key Services Defined Early
  • Strong Support for Server Developers

However, Grosso says by the mid 1990’s, CORBA hype had outgrown the original ambitions and CORBA proponents were claiming amazing things. He then highlights the low points of CORBA:

  • Interoperability Took Too Long
  • Specifications evolved slowly
  • Reliance on Fat Clients
  • Lowest Common Denominator Technology
  • Using IDL Too Complicated
  • Brittle Design Methodologies
  • Very little support for Application Lifecycle
  • Bizarre Mystique
  • No Support for Network Failures
  • RPC Model

If you look at this list, every one of them, except perhaps one, applies to Web Service standards.  That leads me to a grim conclusion, for web services, we are doomed to repeat the failures of the past.

Why do standards evolve in this way? Is there something fundamentally wrong in the way we create standards?  Jim Waldo has a few keen insights on this matter. One of his main points:

A standards body is often a lousy place in which to invent a technology.

Waldo explains that there may be substantial discussion of technical merit in standard groups but he says that its really lip service.  I also think that standards groups tend to choose the lowest common denominator of innovation.  That is, standards groups tend to only approve innovation that they all collectively grasp, however in most cases innovation tends to be grasped only by a few.

Another problem is that standards groups tend to create documentation rather than implementation.  That is a fatal flaw which I explored in "Be Liberal in What You Accept, Conservative in What You Send".  The lack of a standard compliant implementation undermines interoperability, the core essence of standardization.

It's interesting that standards groups give the participants an illusion of choice.  Unfortunately, history clearly shows that their fate is preordained. I guess George Santayana, was right when he coined the phrase, "Those who do not learn from history are doomed to repeat it."


Keith Ray

Posts: 658
Nickname: keithray
Registered: May, 2003

Re: Standards: Doomed to Repeat Itself? Posted: Jun 22, 2003 10:59 AM
Reply to this message Reply
It's been said several times in the Test Driven Development and Extreme Programming community that the best "standard" would be created test-first, and that the text of the standard should include the automated unit tests and / or automated acceptance tests....

Does anyone remember NeXT's "Distributed Objects"? I'm told that system was very useful, but it was never made a standard; and it was only defined for Objective C with DO support.

Keith
http://homepage.mac.com/keithray/blog/index.html

asj

Posts: 1
Nickname: asj
Registered: Jul, 2003

Re: Standards: Doomed to Repeat Itself? Posted: Jul 9, 2003 5:48 PM
Reply to this message Reply
which, of course, describes the JCP exactly. lots of documentation, not enough implementation.

Alex Peake

Posts: 13
Nickname: alexpeake
Registered: Jul, 2003

Re: Standards: Doomed to Repeat Itself? Posted: Jul 10, 2003 6:19 PM
Reply to this message Reply
Web Services (especially the SOAP/XML part) was implemented before the Standards process (by Microsoft).

Most of the Standards process has been IBM, another real implementation, negotiating with Microsoft.

I have implemented, and had running for two years, Web Services. It was very simple to develop and has been very reliable.

Flat View: This topic has 3 replies on 1 page
Topic: Exploring the Java Research License Previous Topic   Next Topic Topic: Principles of Loosely Coupled APIs


Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2014 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use - Advertise with Us