You can't request more than 20 challenges without solving them. Your previous challenges were flushed.

The gray scale of interoperability and IT standards

June 13, 2005, 09:43 AM —  ITworld.com — 

In this article, I want to take a look at what interoperability and IT standards really mean for business users and the benefits that adopting standards may (or may not) bring to an organization.

In order to stay sane and keep the ratio of content-to-terminology ratio fairly high, I need to take some liberties with language. In particular, I will use the word 'standard' to cover everything from ISO International Standards to IETF RFCs to W3C Recommendations. This use of language may be distasteful to some, but life is too short to write about standards in full-on pedant mode.

I will also use the phrase 'de facto standard' to cover things like Microsoft Excel, Adobe Photoshop, etc. This too may be distasteful to some but again, life is too short.

Let us start with the business case. What is the business case for IT standards? Standards are things that help us get complex IT systems to 'just work' - to inter-operate. We want to take X and put it into/onto/under Y and for the whole X/Y thing to 'just work'. The idea is as applicable to hardware as it is to software - USB keys, JPEGs, Excel files, HTML pages, the IBM PC are all examples of standards or de-facto standards at one level or another.

In the software world, there are two main approaches to getting the simple idea of things that 'just work' together to, well, just work. The first is to build applications from the same base application code. Microsoft Office and Open Office are both common examples of this. If I have the same base software as you, we stand a better chance of plugging our stuff together than if we did not share a common base of software.

The other approach is to build everything from the same base data/protocol. HTML, HTTP, CSV, MP3 are examples of this. If I have software that understands the base data/protocol, and you have software that understands the base data/protocol, we stand a better chance of plugging our stuff together than if we did not share a common base data/protocol.

Now things get complicated. Applications can be proprietary and applications can be non-proprietary. Either way, they can be used as the basis for interoperability. Although it is often faster to get interoperability off the ground by using the same application base, you can end up tied in to that application base. It is important to realize that this is true even if the underlying application is non-proprietary.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

I like it!
Post a comment
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
peer-to-peer

jfruh
Apple syncing patent can't come soon enough

pasmith
New Twitter features borrow from 3rd party clients

Esther Schindler
Open Source Changes the Software Acquisition Process

mikelgan
How to set up continuous podcast play on the new iTunes

David Strom
Five important Windows 7 mobility features

sjvn
Guard your Wi-Fi for your own sake                        

Sandra Henry-Stocker
Grepping on Whole Words

 

Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325

Join the conversation here

The Daily Tip

The Daily TipQuick, practical advice for IT pros. Made fresh daily.

Hot tips:

Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.

Newsletters

Subscribe to ITWORLD TODAY and receive the latest IT news and analysis.

I would like to receive offers via email from ITworld partners.
By clicking submit you agree to the terms and conditions outlined in ITworld's privacy policy.
Featured Sponsor

AISO founders envisioned a Web hosting company that was environmentally friendly. While the company employed energy-efficient innovations like solar panels, its infrastructure produced unacceptable power and cooling requirements. Find out how AISO leveraged AMD technology to overcome their challenge in this case study white paper.

In this whitepaper, Scalar explores the opportunity to change the landscape with respect to mission critical databases built around Oracle. Leveraging technologies such as Linux, high-end commodity processing power and Oracle RAC technology to architect, design, build and maintain database infrastructure that delivers maximum availability, reliability and performance at a fraction of traditional cost.

On a typical day, weather.com, the Web site for The Weather Channel in Atlanta, serves up between 15 million and 20 million page views. But in September 2004, when back-to-back hurricanes ransacked Florida, the peak traffic on one day more than tripled: over 70 million page views by more than 7 million unique visitors. Read the full success story now.

Marketplace