This forum is not a perfect fit for this question but its the closest in the site. I've always been curious about the nomenclature of programming standards, expecially the relationship between an ANSI and an ISO standards ( sometimes JIS also comes into the picture and also a strange "IEC - International Electrotechnical Commision"! ). Can anyone throw some light on this, including on the scheme of the standards names?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Technical standards
- Thread starter happyabc
- Start date
fredericofonseca
IS-IT--Management
Regards
Frederico Fonseca
SysSoft Integrated Ltd
ISO is usually European in origin.
ANSI is American
JIS is Japanese
DIN is German
They often copy each other, with slight changes. Or will refer to each other.
Also - sometimes the spec is written after the product is built. A good example of that is the worldwide standard for cargo containers. They got their start in North Carolina about 50 years ago. Prior to their invention, cargo was transferred by hand, using a dolly or a cargo net. As a result, there was a lot of theft, and loading/unloading a ship took a long time. The shipping company owner (Malcolm McLean) decided it would be better to use a standard cargo container, and had some made up in 20' and 40' lengths. After his containers became a success, only then was the size of the container (and the placement of the doors, gripper holes, etc) codified on paper. See [URL unfurl="true"]http://www.alteich.com/tidbits/t060401.htm[/url]
Sometimes you'll see that the spec is written by one supplier, and given to a single large customer. The spec then becomes a requirement for the other suppliers to follow. The US Department of Defense frequently works this way. A supplier will come up with a new electronic component, and supply technical drawings and specifications to the DOD. Since the DOD mostly buys under a competitive bid process, they distribute the spec to other producers. But since they don't have the "inside information", they usually don't get the contract initially. Next round they'll be more competitive.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
ANSI is American
JIS is Japanese
DIN is German
They often copy each other, with slight changes. Or will refer to each other.
Also - sometimes the spec is written after the product is built. A good example of that is the worldwide standard for cargo containers. They got their start in North Carolina about 50 years ago. Prior to their invention, cargo was transferred by hand, using a dolly or a cargo net. As a result, there was a lot of theft, and loading/unloading a ship took a long time. The shipping company owner (Malcolm McLean) decided it would be better to use a standard cargo container, and had some made up in 20' and 40' lengths. After his containers became a success, only then was the size of the container (and the placement of the doors, gripper holes, etc) codified on paper. See [URL unfurl="true"]http://www.alteich.com/tidbits/t060401.htm[/url]
Sometimes you'll see that the spec is written by one supplier, and given to a single large customer. The spec then becomes a requirement for the other suppliers to follow. The US Department of Defense frequently works this way. A supplier will come up with a new electronic component, and supply technical drawings and specifications to the DOD. Since the DOD mostly buys under a competitive bid process, they distribute the spec to other producers. But since they don't have the "inside information", they usually don't get the contract initially. Next round they'll be more competitive.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
- Thread starter
- #4
This describes the informal dynamics of the matter. What I was curious about is the formalities of the situation. A good case is of C/C++. I understand the C++ standardization was a joint effort ( by ANSI and ISO ) but C was not. If so is there a single "ANSI/ISO" C++ standard that both bodies have adopted or are there two identical C++ standards that both bodies have adopted ( another possibility is that one body just adopts the standard of the other )?
I also wonder how IEC gets into the act?
I also wonder how IEC gets into the act?
Honestly, I've never heard of the IEC. They must be a minor player in the standards business.
And as regards ANSI vs. ISO standards for C++, I would say it's a non-issue, as none of the vendors are following the standard precisely -- you will always have some variance, depending on if you're using MS, Borland, gcc, or some other C++ compiler.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
And as regards ANSI vs. ISO standards for C++, I would say it's a non-issue, as none of the vendors are following the standard precisely -- you will always have some variance, depending on if you're using MS, Borland, gcc, or some other C++ compiler.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
IEC has only fairly recently moved into the software area. It deals mainly with mechanical and electrical specifications and drawing standards. It's not as widely known in the US as it is in Europe.
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'If we're supposed to work in Hex, why have we only got A fingers?'
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'If we're supposed to work in Hex, why have we only got A fingers?'
- Status
Similar threads
- Locked
- Question