An editorial by Joseph Ottinger in Java Developers Journal provides an interesting challenge to anyone involved in standards work:
Standards are best generated from what people are using, not from what people in a boardroom think should be used. The market moves faster than a standards document can.
The key is when to innovate and when not to.
The smart thing to do is obviously to standardize what is already known to work, rather than trying to design solutions by (often very big!) committees. That's why WS-I is proving so successful I think.
This idea echoes one of my favourite phrases: "The only true test is production deployment." - meaning everything can seem fine in the development labs, but it's only real world usage experience that really proves "fitness for purpose".
The same thing applies to all technology and standards too, IMHO.
Pushing forward innovation in such a standards prone environment is also difficult too, but sometimes a discontinuity or quantum leap is both necessary and good. The hard part is obviously getting this decision right!
All content is
Copyright (c) 2008 Jorgen Thelin. All rights reserved.
Content is provided "as-is", without any representations or warrenties of any kind.
Contents of Weblog Feed are
Licensed under a
Creative Commons License.