Skip to primary content
ConsortiumInfo.org
Search
Sponsored by Gesmer Updegrove
  • Blog
  • About
  • Guide
  • SSO List
  • Meta Library
  • Journal
meta library

Why Java Was – Not – Standardized Twice

Title
Why Java Was – Not – Standardized Twice
Author
Tineke M Egyedi, Department of ICT, Delft University of Technology
Date
1/01/2005
(Original Publish Date: 2001)
Abstract
Proprietary de facto standards are seldom formalized. This paper examines a case, the Java? Technology ofSun 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? and increase confidence in an open, stable Java specification process. But it turned to proprietary 'compatibility control' in reaction to standards politics and developments in themarket.
Link
Full Text (PDF) from IEEE Computer Society
Technical Areas
  • Case Studies
  • Process of Standard Setting
Gesmer Updegrove
  • Terms of Use and Privacy Policy
  • Contact
  • Sitemap