|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 5
Maui, Hawaii
January 03-January 06
ISBN: 0-7695-0981-9
| ASCII Text | x | ||
| T. Egyedi, "Why Java Was Not Standardized Twice," 2013 46th Hawaii International Conference on System Sciences, vol. 5, pp. 5015, 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 5, 2001. | |||
| BibTex | x | ||
| @article{ 10.1109/HICSS.2001.926529, author = {T. Egyedi}, title = {Why Java Was Not Standardized Twice}, journal ={2013 46th Hawaii International Conference on System Sciences}, volume = {5}, year = {2001}, issn = {1530-1605}, pages = {5015}, doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2001.926529}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - 2013 46th Hawaii International Conference on System Sciences TI - Why Java Was Not Standardized Twice SN - 1530-1605 SP EP A1 - T. Egyedi, PY - 2001 KW - Java KW - de facto standard KW - compatibility strategies KW - JTC1 KW - ECMA KW - technical compatibility KW - market coordination VL - 5 JA - 2013 46th Hawaii International Conference on System Sciences ER - | |||
Proprietary de facto standards are seldom formalized. This paper examines a case, the Java(tm) Technology of Sun Microsystems, where this was attempted. Sun approached the ISO/IEC JTC1 standards body and later the ECMA standards consortium to formalize Java. It withdrew both times. In this paper, I examine what motivated Sun's actions. A conceptual framework is applied that distinguishes two levels of coordination in standardization: 'technology-oriented compatibility control' and 'orchestration of market orientation'. Sun's actions addressed both levels. It initially used standardization to focus attention on Java(tm) and increase confidence in an open, stable Java specification process. However, it turned to proprietary 'compatibility control' in reaction to standards politics and developments in the market.
Index Terms:
Java, de facto standard, compatibility strategies, JTC1, ECMA, technical compatibility, market coordination
Citation:
T. Egyedi, "Why Java Was Not Standardized Twice," hicss, vol. 5, pp.5015, 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 5, 2001
Usage of this product signifies your acceptance of the Terms of Use.