Welcome!

Linux Authors: RealWire News Distribution, Pat Romanski, Adam Grocholski, Unitiv Blog, Michael Bushong

Related Topics: Linux

Linux: Article

Open Standards vs Open Source

Open Standards vs Open Source
By Tyler Jensen
Article Rating:
April 19, 2004 12:00 AM EDT
Reads:
 15,980

The benefits and market opportunities provided by open standards far outweigh those derived from open source. While the software development market has certainly benefited remarkably from open source, open standards and protocols such as TCP, HTTP, and XML have made it possible for developers and software vendors to participate in the most rapid technological progression of humanity in the history of the world.

Without question open source has been a boon to software developers. While you may not find many lines of Linux code in the proprietary applications software sold for systems running Linux and other operating systems, you will undoubtedly find developers and software products that have benefited either directly or indirectly from the buoyant properties of the open source community and its shared intellectual library of solutions to common software development challenges.

An understanding of the underpinnings of the operating system and its source code levels the playing field for the applications market. This may even lead vendors of proprietary operating systems, who also compete in the applications market, to think twice before taking unfair advantage of insider knowledge.

Despite the sizable contribution of open source to the world of technology, the assumption that open source and Linux are responsible for an economic bonanza for those companies that have embraced them is questionable. One must ponder the possibility that HP would have sold $2.5 billion in hardware, proprietary software, and services referred to as "Linux-based" with an alternative operating system if Linux and the open source concept did not exist because HP's customers would have required those goods and services regardless of the existence of open source and Linux.

Would IBM give up its quest to dominate the hardware and services market if open source and Linux had never come along? Would Oracle throw in the towel and stop selling its database for proprietary operating systems? Would Amazon.com close its virtual doors? Would governments cease critical services if they could not install an operating system without paying a license fee for it?

The real question is where would we be without open standards? Without HTTP there would be no Amazon.com. Without TCP/IP there would be no Internet. Without SMTP there would be no spam. Well, okay, maybe that would not be such a bad thing. Without Ethernet there would be no LAN for 20 bucks a node. Without XML there would be no easy way for disparate systems to work together. Without SOAP there would be no Web services. Without SSL there would be no e-commerce. Without development language standards such as ANSI, C++, and SQL 93, people like me would be lost in a sea of proprietary languages and unique development tools. Indeed, without all of these open standards and more, open source would be without purpose or direction, without a skeleton on which to build the muscle and sinew that brings technology to life.

Standards bodies such as ANSI, ISO, ECMA, W3C, and IEEE are the guardians and keepers of the technological compacts that have made it possible for us to leap from the punch cards of 40 years ago to where we are today. Let us salute them and their many members who work tirelessly to the benefit of us all. Because of their work, I can plug my computer into an Ethernet jack anywhere in the world and be on the network. I can buy books from Amazon. com securely with the browser software of my choice. And I can jump on the Internet with a wireless card in any one of thousands of locations across the globe to check my e-mail, chat with friends, post a letter to the editor, or just catch up on the news in my small rural hometown.

Published April 19, 2004 – Reads 15,980
Copyright © 2004 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.

More Stories By Tyler Jensen

Engrossed in enterprise application architecture and development for over ten years, Tyler Jensen is a senior technical consultant in a large health intelligence company, designing and developing claims processing and analysis software. In his spare time he does a little writing and outside consulting.

Comments (4) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Most Recent Comments
Ritchie 05/07/04 01:24:43 PM EDT

We need both open standards and open source that support the standards. This is not an either/or situation and discussions that say one is more important than the other are silly, IMHO. Standards drive interoperability, open source drives ubiquity and lowers the threshold for those who want to get in the game. Therefore if standards are good and useful (and not all of them are), open source can help ensure that there will be widely available, good quality implementations. Adoption of the standards will then take place faster.
Paulo 04/21/04 12:09:17 PM EDT

We cannot forget why SOAP/CORBA didn't have a great spread the first time it appeared, some coMpanie$ have made a broad campaign on unbelieving about such technologies. In a while they were fully used by free sw developers.

And what about the proprietary software hidden interfaces? Yeah, they keep secrets for they own. Look at the .net specification (which as published, is supposed to be public, so that anyone could port to other environments, etc), the try implementation "Mono" is still skidding because of lack of information, they cannot implement what is not said to be implemented.

So that's right that Open Standards help a lot (if really open), but Open Source may increase much more the progress of technology, since there are intellectual capital being carried with it, which may be rose by a community and companies interested on it.

And what about
Scott McNeil 04/21/04 11:10:50 AM EDT

The Linux Standards Base, or LSB, combines Open Source and Open Standards. In so doing the LSB has succeeded to:

1. Make application developer's lives easier
Application developers can spend more time building enhancements rather than verifying that their code works not only on the many Linux distributions but the different versions of a single distribution (i.e. Red Hat 7.3 vs. 8.0, etc.)

2. Make operating system vendors lives easier
By adhering to the standard, operating system vendors can reach a wider market, assuring that portability of applications is not an issue with their products.

3. Make end users lives easier
Customers are starting to demand LSB Certified solutions due to their promise of easier system administration, applications that run "out of the box" and lack of vendor lock-in.

4. Grow the Linux market
The LSB is setting the stage for the next wave of Linux market growth: commercial applications.

As of 2003 every major Linux distribution vendor in the world has voluntarily applied for and achieved LSB Certification. Additionally, the Free Standards Group, the organization responsible for the LSB, has been recognized by ISO and will be submitting the LSB for ISO transposition later this year.

The LSB is but one more example that the powerful combination of Open Source and Open Standards helps everyone.
David 04/20/04 08:09:20 PM EDT

All true, but OSS is one of the top implementors of open standards. Heck, Jakarta is the reference implementation for the Java servlet/JSP standards.

May standards were also created by these committees that haven't gone anywhere. PKI has myriad standards that are so complex and have interoperability issues that it's laughable.

Sure, HTML is great, but the OSI create SGML before it, and that failed big time because it was too complex.

TCP/IP is great, but the OSI came out with their own 7 layer communications stack and it never did take off. TCP/IP wasn't just a standard, but it was written into Unix and the code for it was publicly available.

LDAP has worked pretty well, though it's not truly the same as the proprietary vendors implementations, such as Microsoft's Active Directory. And again, the OSI created X.500 for this, and it went nowhere fast.

The XML standards are suffering and benefiting in a similar way. XML itself is quite easy and clean and is being used a lot. But the many other standards that surround it haven't been adopted anywhere near as quickly, and SOAP needs to be renamed because it's far from SIMPLE anymore.

And we don't need to mention that the standards bodies came out with ASN.1 for encoding and CORBA for interoperable object messaging, yet it was the early SOAP over XML, loosely based on the far simpler and more elegant XML RPC base.

OSS is great because it implements these standards in a way that people can actually check and verify. Most proprietary implementations of "open standards" often fail because they just can't help themselves making their products "better" than the standards by filling in the "missing pieces." What a joke.

Anyway, they play best together. What we're suffering with now is standards being created before they are developed and proven by working systems, and that's why many new XML standards getting more complex and less adoptable.