![](https://seccdn.libravatar.org/avatar/7406815515e8651a2b6764112a753a19.jpg?s=120&d=mm&r=g)
Back in the 1960: The standard was ASCII, IBM used EBCDIC on their 360. The Database standard was a CODASYL database standard (before ANSI standards), IBM used hierarchial. Basically, IMHO, standards are a good thing when written correctly. However, there is always a need (or desire) to add extensions. There are several Unix standards, such as SVID 3, SVID4, Unix95, Unix 98. Good standards are generally written by people in the industry who implement. Part of the problem is that the standard must be written clearly and concicely. Have you ever read the ISO C or ISO C++ standards. Not easy to understand unless you are used to dealing with those. When a standard is being written, various parties must agree to it. Not an easy job. Once the standard is published, then there needs to be some method of measuring compliance. And, standards cost. On 28 Mar 2002 at 17:31, Michael Garabedian wrote:
But with a standard set by international means that is adopted by the industries outside of IT then they won't try to subert them, but help them along, and with everyone working together it could be another open source project. Like a big sap network, with each industry getting its own brand but being able to send it to other modules and industries.
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752