decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Why Open Standards are Good for Business, by Sean Lynch
Saturday, November 29 2003 @ 10:30 AM EST

There is an article on Newsfactor in which a SuSE executive points out that the Novelll-SuSE merger will be good for business, because they intend to create a stable standard that will make it easier to implement open-source applications:

"'We're just beginning the planning stages of integration with Novell right now, so there's not a whole lot of detail,' said SuSE vice president of corporate communications Joseph Eckert. 'But we do see the next arena as enabling the systems management -- enabling a greater access to those who use open-source applications by creating a standard to which all of that can be written,' he told NewsFactor. 'We believe that will enable an unlimited amount of flexibility in creating middleware solution stacks.' . . .

"As for SCO Group's allegations, Eckert pointed out that the Linux SCO uses is based on SuSE Linux, and that SCO and SuSE already have agreements in place about competing and partnering. He also sneered at the company's growing reputation for litigiousness. 'We're not planning to sue anybody, so I'm not seeing where the competition is,' he said. 'As far as I know, they're nothing more than a litigation company right now, not a software company.'"

The issue of standards is an important one. For a look at how Microsoft handles standards, here's an article in Internet Week, about MS submitting media technology back in September it hopes will become the standard instead of MPEG for video.

Here's why they would like to do this, and it isn't so all businesses can benefit:

"Microsoft Corp. said . . . it has submitted Windows Media Series 9 to a standards body, surprising industry analysts in a move that could help the software maker reverse its lackluster performance in the multimedia technology market.

"Microsoft submitted the video-compression code on which the product is built to the Society of Motion Picture Television Engineers. . . .

"Windows Media Series 9 was launched a year ago in Hollywood with much hoopla. But despite the endorsement of celebrities such as director James Cameron, the technology had done poorly against competitor MPEG2, a compression standard used as the underpinning of satellite, cable, video-editing systems and DVDs. . . .

"Under SMPTE rules, Microsoft will have to offer the technology under open-license terms, but will be allowed to collect royalties, which can be very lucrative. Consumer electronics companies, for example, pay license fees each time they use a compression technology.

"In addition, if Microsoft's technology became a de facto standard, than the Redmond, Wash., company would be in a good position to make money selling proprietary software on top of the standard, such as digital rights management, security and Windows infrastructure."

So there you are. Two ways of approaching an issue. A Groklaw reader, Sean Lynch, sent me an email, explaining the issue of standards. I thought the analogy he used made it so clear that I asked him to write it up into a short article, with links. Now that SuSE has raised the issue, it seems like a good time to share what Sean wrote on the subject of standards and why businesses benefit from open as opposed to proprietary standards.

*********************************************

Why Open Standards Are Good for Business
~ by Sean Lynch

It has been stated many times that the UNIX trademark is owned by The Open Group. The Open Group also controls the Single UNIX Specification and decides what is and is not UNIX. You can read their Guide to UNIX certification online and learn how your operating system can become a UNIX.

The reasons for standardization are numerous, but I like using car tires to point out why standards are important.

If you look on the sidewall of a car's tires you will see a series of numbers and letters. These will be something like 185/60 HR14 or 25/50 R16. These numbers stand for the width, height, internal radius, temperature rating, and so on.

These are standards agreed upon by all tire manufacturers. By using standard-size tires, buyers -- including auto makers -- can easily shop around and purchase tires from different vendors. This leads to competition and reduced prices.

If a major auto maker decided to use a proprietary standard, they would be locked in to one supplier of tires, and the car buyers would likewise have only one source of tires. This would lead to higher prices because tire manufacturers would be making many small batches of unique tires, increasing the cost of retooling.

If one tire maker achieved market dominance, they could hurt the auto industry by discontinuing a tire size, forcing the auto makers to retool the wheels on their cars. This market dominance would lead to lock-in for car makers and buyers.

By using standard size, interchangeable tires, consumers, manufacturers and investors all benefit. Open standards are generally good for business.

The UNIX standard attempts to do the same for operating system users. If you write software you can count on how an operating system will behave if it follows published standards. When I use a UNIX operating system function, I know what the input needs to be, what form the output will take, and what optional settings I can choose. This behavior is consistent across all UNIX operating systems. This leads to a certain level of commoditization in the operating system world. Also it is important to note that the code that implements the UNIX behavior can be different from one version of UNIX to another. The behavior is what matters; how you write code to achieve the standard behavior can be unique.

The Open Group on May 22nd, 2003 issued a press release that describes its position on the SCO Group's statements on their alleged UNIX "ownership". The Open Group owns the UNIX trademark, controls the single UNIX standard, and decides what is and is not UNIX. Their press release gives a good history of the UNIX trademark and contains this clear guidance: "Statements that SCO 'owns the UNIX operating system' or has 'licensed UNIX to XYZ', are clearly inaccurate and misleading." Note the helpful links at the end of the press release as well.

The entire UNIX specification is available online or it can be ordered on CD-ROM for about $60.00(US). The Single UNIX Specification is also published as a standard by several international standards bodies as IEEE Std 1003.1 and ISO/IEC 9945. Any individual or group could obtain a copy of the Single UNIX Specification and implement each and every portion of it by writing their own code. They could also use other people's code if they have permission to do so from the original copyright holder in the form of a license of some sort.

It is costly to get an operating system certified as UNIX standards compliant by the Open Group. Of course, it would also be costly in time and effort to write the code needed to implement the Single UNIX Specification. However, it is completely possible to create an operating system that can use the UNIX trademark without any involvement from The SCO Group.


  


Why Open Standards are Good for Business, by Sean Lynch | 72 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Why Open Standards are Good for Business, by Sean Lynch
Authored by: brenda banks on Saturday, November 29 2003 @ 11:04 AM EST
some standards are necessary
but not using proprietary from MS
they are a monopoly and should be barred automatically from being able to even
submit anything like this
car industries have discovered over the years that it is better for them to even
develop some standards
i call them specifications but it is the same thing
it is a balance so the world doesnt get all topsy turvy


---
br3n

[ Reply to This | # ]

I am confused - can somebody help me to understand it?
Authored by: OK on Saturday, November 29 2003 @ 11:20 AM EST
What exactly is SCO claiming to own? Trademark? Copyright? Patents? To what? To
the IP they developed? Or to the IP they PURCHASED? What exactly is their, what
exactly is purchased by them, and what exactly are they claiming to be
misappropriated?

[ Reply to This | # ]

Why Open Standards are Good for Business, by Sean Lynch
Authored by: zjimward on Saturday, November 29 2003 @ 11:26 AM EST

In the IT industry there has been talk for years about open standards. There has
been specification group after group formed, but there has always been
proprietary software and licenses to be passed around. I've seen Open Source as
a great way to finally have true open standards, but until it's more common
place you will have companies like Microsoft, Sun, SCO and others looking for
ways to take it down. Why? Because it eats away at their bottom lines. They have
built their companies on the idea that what they have come up with is unique and
no one else has the ability to use it, without them making money from it. This
is another reason that companies are taking patents out left and right. All of
the patents that I've seen so far, such as the one-click shopping at Amazon,
don't seem worth the paper for the patent. Where will it end, who knows, but
let us all hope that open source will lead to better open standards and an
better growth in the world economy.

[ Reply to This | # ]

National Institute of Standards and Technology tells of close to 800,000 global standards
Authored by: Anonymous on Saturday, November 29 2003 @ 12:19 PM EST
Here is a VERY interesting article about standards -interesting reading that
could be applied to a software standards conversation as well!
http://www.wired.com/wired/archive/10.01/standards.html

Quote from article:
"Today, according to the National Institute of Standards and Technology,
there are close to 800,000 global standards. But go back a century and a half
and you find an American economy in which there were literally none. On April
21, 1864, a man named William Sellers began to change that. Sellers initiated
the first successful standardization fight in history, over the humble screw.
That struggle was not just about a particular standard. It was about the
importance of standardization itself. To win, Sellers relied on technical savvy
- as well as political connections, clever strategy, and a willingness to put
progress ahead of the self-interest of his own friends and colleagues. [end
quote]

Why Microsoft, SCO and others want to go against the flow and do what is NOT
best for everyone is due to GREED (and a desire to maintain a MONOPOLY
position)!

[ Reply to This | # ]

Some background info on Internet Standards
Authored by: mac586 on Saturday, November 29 2003 @ 01:09 PM EST
The Open Sources Voices from the Open Source Revolution book has a very good essay on standards and their benefits. Each chapter of this book is really an essay written by a different author, and it is a terrific reference to understanding many of the historical discussions that take place here at Groklaw.

Of course, it is freely available online. Follow the link to The Internet Engineering Task Force to see how Open standards helped create the internet as we know it today.

Take the time to check out the other essays, each is well written and not overly technical. When this book came out I purchased several copies and provided to various PHBs so they could understand some the design decisions I was making in my lab.

[ Reply to This | # ]

Why Open Standards are Good for Business, by Sean Lynch
Authored by: theswede on Saturday, November 29 2003 @ 01:29 PM EST
This is exactly the point that I always try to hammer home with people when they
ask why I don't use "the industry standard". The
"standard" simply isn't. Even something as simple as the Word .DOC
files go through rather radical changes with each version. I have several
company documents from my first company that cannot be read now, in any way.
They're in Word 2.0 format.

Word 2.0 had all the features I ever have used in a word processor, except on
the fly spellchecking. If it was viable today, I would still use it - it runs
fine in 16 megs of RAM and has all the bells and whistles needed. But since the
Word .DOC format is locked in and prorietary, documents produced with Word 2.0
cannot be used in todays environment, and with Word 2.0 I can't even open Word
6.0 documents; the MS provided filter will crash on anything larger than a page
or so. For newer versions there isn't even any filters around.

Very good explanation in this letter. I'll point my friends this way when they
ask in the future.

[ Reply to This | # ]

Why Open Standards are Good for Business, by Sean Lynch
Authored by: Anonymous on Saturday, November 29 2003 @ 02:15 PM EST
If open standards are good for business, why do they and governments go against
their best interests. Is it ignorance, stupidity or laziness? Why do governments
and business continue to choose MS lockin over open standards? They could easily
refuse to buy the next office suite unless MS opens the formats and adheres to
open standards. Or better yet don't sign any long term contracts for softward
that don't use open standards. If MS doesn't want to supply open standards
then ignore them. How long does anyone think it will take for MS to conform. I
don't think it will happen in the US or in Europe but it may happen in China.
Wouldn't it be ironic for China to save the world from MS lockin.

[ Reply to This | # ]

SCO is an IP Licensing company - McBride
Authored by: jaydee on Saturday, November 29 2003 @ 02:40 PM EST
An interview with DM. (Caution you may damage your computer reading this).

http://siliconvalley.internet.com/news/article.php/3114341

Q: Talk about your methodology moving from an IP provider to an IP licensing
company. What lessons can be learned here?

The significant lesson learned here is that intellectual property does matter.
This country was built on a basis of capitalism and coming up with some idea to
protect it through patents, copyrights, trademarks, all kinds of legal
mechanisms. And that is what we are doing here. We are protecting what is
rightfully ours that we've paid hundreds of millions of dollars for over the
years. And I think this is sending a very strong message to the world that,
capitalism is alive. The ability to protect your property is still solid and we
think this important going forward.

The question is: the GPL going to reign supreme? Are copyrights going to be
destroyed? Is the whole world going to turn into a free software environment? Or
is it going to be the traditional software licensing model continuing of
protecting your IP - Being able to profit from that and then upon generating
profits gong off and doing new innovations and new technologies. We think the
latter is going to come out in then. The reason this is such a big issue in the
marketplace is that SCO is at the center point of the argument. Whichever SCO
goes on this, that side is going to build itself up a seriously amount of
momentum.

We think the GPL is not going to make it. We think that it is so unfriendly to
businesses. Companies are worried about protecting their own intellectual
property assets.

[ Reply to This | # ]

Standard GUIs for Linux
Authored by: Thomas Frayne on Saturday, November 29 2003 @ 04:22 PM EST
When IBM and Microsoft were developing OS/2, they agreed on standards for a GUI
with a uniform look and feel. Those standards have evolved into a de facto
standard now used throughout Windows, and dictated by Microsoft.

I think that Novell/SuSE are focusing on standards for commands, APIs and kernel
calls. That is very important, and I hope they will be able to come up with a
version of Linux that can be certified compliant with The Single UNIX®
Specification.

However, we should also be developing standards for the GUI, and perhaps neither
Microsoft nor the Open Group is the proper arbiter for these standards. It
might be better to form a Linux GUI Standards Group (LGSG) for this purpose.

Many will feel that GUI standards for Linux would be a step backward that would
tend to lock users into a GUI straight-jacket. The standards would have to be
designed carefully to avoid this pitfall, but standards are still needed, for
the same reason that windshield wiper controls tend to be on the right of the
steering wheel and turn signals on the left: the user can have one pattern to
remember, not a lot of random variations.

The main competitors for the look and feel of the desktop now seem to be
Windows, KDE, and Gnome. I don't think any of these should go away, for they
each appeal to a large set of users. A user should be able to choose a named
theme to define an overall look and feel, and the LGSG standard should specify
the theme names, the default theme, and the method of selecting a theme during
installation and during configuration.

The standard should also specify a set of basic themes, including Windows, KDE,
and Gnome, and allow for additional basic themes to be added to the standard.
All basic themes should support a basic set of common features with the same
look and feel: e.g., top bar, menu bar, tool bar, start menu, quick launch
panel. Further, all these features should be configurable, and the procedure
for configuration should be common.

All this is meant to help the new user who wants to move from a familiar system
to a new system to quickly become familiar with the new system. After meeting
that requirement, the standard should be as flexible as possible, so that a user
that is used to one look and feel does not have to give it up to use a system
certified to satisfy the standard. The standard has to meet the needs of
experienced users as well as those of new users.

After the basic features are in place, each basic theme should be able to add
features most appropriate to its own look and feel. Themes other than the basic
theme should not be required to support the basic features, and might support a
completely orthagonal set of features.

Basic applications should support all the basic themes, and could support other
themes as well. Other applications could support just one theme. If that theme
proves unpopular, they can add others, or lose out to competitors that do.

These standards could start from a small stable base and evolve over time. I
would not see a problem if a feature that is required in all basic themes for
version n of the standard was dropped from the basic themes for version n+1.

[ Reply to This | # ]

Why Open Standards are Good for Business, by Sean Lynch
Authored by: D. on Saturday, November 29 2003 @ 04:42 PM EST
Just so that everybody knows, there is a defined, and open, standard for a linux
distro:

http://www.linuxbase.org/

Certification is handled by the Open Group.

D.

[ Reply to This | # ]

And if that proprietary tire has a defect?
Authored by: Anonymous on Saturday, November 29 2003 @ 05:26 PM EST
"If a major auto maker decided to use a proprietary standard, they would
be locked in to one supplier of tires, and the car buyers would likewise have
only one source of tires. This would lead to higher prices ..."
You could also have mentioned that if the tires turned out to be defective, the
consumers would have the unpleasant choice of stopping driving their cars, or
driving them dangerously. Undoubtedly the manufacturer would have a clause in
its terms of sale ("license") that says the buyer assumes liability
if the second option is chosen.

[ Reply to This | # ]

Why Open Standards are Good for Business, by Sean Lynch
Authored by: Anonymous on Sunday, November 30 2003 @ 12:08 PM EST
If you look on the sidewall of a car's tires you will see a series of numbers and letters. These will be something like 185/60 HR14 or 25/50 R16. These numbers stand for the width, height, internal radius, temperature rating, and so on. These are standards agreed upon by all tire manufacturers.

If I'm not mistaken, those standards are mandated by the government, the National Highway Traffic Safety Administration, in fact.

If the government mandated an OS, it would probably be POSIX (Portable Operating System Interface).

So your analogy fails from the get go.

Document portability is the most important thing. Too bad David Boies didn't realise this during the Microsoft anti-trust trial.

[ Reply to This | # ]

Sean, What IS an Open Standard?
Authored by: bbaston on Monday, December 01 2003 @ 11:45 AM EST
There is a very serious flaw in the currently active process of software
industry standards which makes them NOT open. We have concentrated on NASA's
"Software is not software unless it comes with code." Higher
requirements must be met by inter-operating system standards, or they are not
Open Standards IMHO.

The likely consequence of Digital Rights Management (DRM) being proprietarily
added to a standard should NOT be acceptable by any standards group, nor should
a standard result in any mandatory fee being paid to any entity, nor should any
user of the standard be allowed to implement revisions which unduly restrict its
use or result in fees being paid directly because of the revisions.

I submit that truly open standards must be defined strict requirements:

1. Be overwhelmingly approved by a panel fully representative of potential
users (i.e., 95+%).
2. Give CONTROL to the USERS without encumberence.
a) Not require proprietary hardware or software to implement.
b) Not require ANY license or fee to use.
c) Not be unduly difficult to implement, i.e., may not require any licensed
code or technolgy unless that code or technology also meets all that is
described here.
3. Requires all users to provide back to the panel, and include with all
distributions made by the revisor, any and all changes made to the standard,
including whatever is required to implement the revisions, as was the standard
on which the revisions are based.
4. Standards cannot include anything that excludes use or makes use onerous for
any popular operating system (i.e., over 0.9% of installed base).

Yes, this means NOT accepting as a standard anything that includes paying a fee,
directly or indirectly. Fees are accepted, even expected now, so what we have
are not Open Standards. What we have is assignment of monopoly fees and lock-in.
We should never endorce restrictions on the user, when it limits our choice of
operating system and user control.

What happens if a standard includes patent or trade secret elements? Simple:
disqualify it from consideration unless it is offered without encumberment.

Control for the end user: that's what *open* software is to me. That's
certainly what Open Standards should be.

---
Ben B
-------------
IMBW, IANAL2, IMHO, IAVO,
imaybewrong, iamnotalawyertoo, inmyhumbleopinion, iamveryold,

[ Reply to This | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )