Transfer of Microsoft's object messaging technology to The Open Group draws fire from open-platform advocates
New York (October 14, 1996) β Unless youβve been living in a cave not equipped with a modem recently, youβve already heard about Microsoft handing over parental control of its ActiveX, COM, and DCOM technology to The Open Group (TOG), the recently formed standards body resulting from the merger of the ailing Open Software Foundation (OSF) and the X/Open Co., the repository of the trademark for βUNIX.β
According to TOG, the proposed Active Group, which will manage the evolution of ActiveX Core technologies, will be headed by a steering committee consisting of system, application, and tools vendors and customers. It will be composed of standing and rotating members. The initial standing members of the group include Adobe Systems, Computer Associates, Digital Equipment Corp., Hewlett-Packard, Lotus Development, NCR Corp., SAP AG, Siemens Nixdorf, Software AG, and Sybaseβs Powersoft division. Additionally, Borland International, Sheridan Software Systems, VideoSoft, Visio, and Wall Data signed on for one-year stints as rotating members.
The move immediately pumps oxygen into the new standards body. And the new parents, who have defined the mission for a new entity called The Active Group, are eager adopters. Not only does TOG take over the reins of a software regime in which Microsoft has invested 00 million over the last seven years, but the word from one Microsoft executive who spoke off the record is that the company will soon join the board of TOG, paying million for the seat.
The main task before TOG, of course, is to standardize the linking of front-end Windows PCs to the massive data available primarily in non-Windows back-end systems. The Open Group intends βto manage the cross-platform evolution of ActiveX technologies, to improve interoperability with other environments, and to incorporate a wider cross-section of customers and industry in the evolution of these technologies.β
By opening up ActiveX, Microsoft strives to make its heretofore proprietary network-oriented component integration technology more attractive to developers who currently favor open technologies such as JavaSoftβs forthcoming Java component API (JavaBeans), the Object Management Groupβs Common Object Request Broker Architecture (CORBA), and the OMGβs CORBA-based Internet Inter-ORB Protocol (IIOP) β a standard for distributed object communication on the Internet supported by Hewlett-Packard, IBM, Netscape, and Sun Microsystems, among others. These technologies lack ActiveXβs Windows-centric heritage and support a wide range of platforms and operating systems.
Also involved in the open standards question is the issue of OpenDoc, an industry standard from the OMG and Component Integration Laboratories. Closely aligned with efforts at IBM and Apple Computer, OpenDoc has recently been implemented in IBMβs Arabica technology, which supports Sunβs JavaBeanβs initiative (which will be finalized this week); also recently, following the announcement that Sun and Apple will create an integrated line of products for the Internet and corporate intranets, Sun executives suggested Sun and Apple might work to create a common code base for Java and OpenDoc.
βWhat Microsoft is turning over are the [ActiveX] source and binary codes and specs, as well as reference implementations and conformance test suites,β explained James R. Bell, CEO of The Open Group. βThe Open Group provides is a fair and equitable means of licensing and distribution. Licensees will have to agree to pool relevant intellectual property; in return, they will receive standardized branding and certification procedures.β
βInteroperability is the key for success in the realm of network computing, but the Internet is a very market-driven phenomenon,β said Jamie Lewis of the Burton Group, selected by Microsoft to moderate the October 1 meeting of stakeholders. βSo the test for Microsoft and The Open Group is to make a successful transition to an open systems strategy. Obviously, IIOP and CORBA are not going to go away. But the mistake of the past has been to get into a religious war over standards. And this is a mistake the industry cannot afford to make again.β
But will another religious war break out, in which a standards body championed by Microsoft tilts at a standards body championed by Netscape and other competitors? The odds-on betting among industry cognoscenti after the meeting was that it is only a matter of time, unless The Open Group, based in Cambridge, MA, is willing to commit to negotiations with the OMG, its robust chief rival and one of the worldβs largest software standards bodies, based in nearby Framingham, MA. And, in an ad hoc polling of ISV representatives, technical analysts, and programmers, reactions to the news of Microsoftβs transfer of its rights to ActiveX to TOG ranged from the charitably diplomatic to the downright cynical.
Peaceful coexistence?
βWeβre delighted that Microsoft sees the value of an open standardization process based on consensus, and we hope that both they and The Open Group realize that years of user and vendor consensus have already gone into the Object Management Architecture, CORBA, and IIOP,β said Richard M. Stoley, chief science officer of the OMG. βWhatever comes from this new effort and however it is composed, OMG will ensure standardized interoperability with it as we have with COM and DCOM in the past. Much more important will be how the user gets the most out of Java-based systems, CORBA systems, and ActiveX immediately.β
βMore important to OMG at the moment is Java and Java Services integration with CORBA and CORBA services, given that ActiveX β at least large parts of it β are not commercially available,β said Christopher M. Stone, CEO of the OMG. βAs far as cooperation or coopetition I believe you will see a little of both down the road.β
While some Java enthusiasts perceive ActiveX and COM as competing technologies, others consider the two standards complementary. βI think Java and COM go together very well,β said Don Box, an executive at DevelopMentor Corp. and a noted C++ guru. βIn fact, Java is easily the most COM-friendly language, hands down. Which is really ironic, considering where they came from. So I donβt feel that itβs an either/or situation. The good news is that the people at The Open Group are adults, theyβve been around, and they know what theyβre doing. So letβs see what happens.β
βThis shows that people are starting to cooperate to create a market,β said Carl Cargill, a standards strategist for Netscape, an affiliate with the OMG. βAnd then compete once that market has been created. Which is a good thing. If the OMG and the group here can merge on this, we will. I donβt want to get into another standards war. Standards bodies are created for cooperation and not for competition β look at the W3C. The marketplace is really the place for competition.β
Open warpath?
βThe only difference between this meeting and a Bob Dole rally was that Microsoft didnβt hand out campaign buttons,β said Mike McCamon, director of product management for Visual Components, one of the voting enterprises working with both ActiveX and Java. βItβs not hard to see what they [the buttons] would have read: βYou Can Trust ActiveX, You Canβt Trust Java.β I think it was a political move, literally. Now Microsoft can say, βLook, we gathered these ISVs together and put the issue to a vote, and TOG was chosen: So there is nothing that is going to prevent ActiveX from becoming the new standardβ.β
βGates gave everyone a choice of either Microsoft controlling ActiveX or an organization hand-picked by the company β no alternative was offered,β said industry consultant Frank D. Greco, president of Crossroads Technologies. βDoesnβt that make you wince? The members of the Open Group are allied with the PC platform, which makes any non-PC implementation of the ActiveX specification a distant thought. Any other implementation would have to make performance or functional concessions to the spec. Standardization can be good or bad. ActiveX is not a bad technology per se, its just that it truly can only run in a Windows architecture. And that is anathema to the philosophy of the Net.β
βMicrosoftβs standards effort, like many standards efforts, should be interpreted entirely as a political, not a technical, initiative,β said David Koosis, technical director for ISC Consultants and co-author of Java Programming for Dummies. βIn the absence of strong, savvy software competitors, Microsoft has an abysmal record as far as open standards are concerned. They canβt restrain themselves from coopting standards to fit their own short-term strategic advantage. While Microsoft bashes Java for security holes, the proposed alternative, ActiveX, has no built-in security. Are we to assume that a trusted ActiveX component wonβt accidentally or maliciously cause harm? If an ActiveX component comes from a trusted vendor, say Microsoft, can I rest assured that the component wonβt overwrite TCP/IP DLLs upon which competing products depend? I think thereβs a real place for ActiveX, but from its execution I see that its standards effort is purely a sophisticated and cynical marketing campaign.β
βWhy is CORBA not good enough for Microsoft?β lamented Erik Radmall, technical partner at i33 Communications, a Web content house in New York. βIt was developed with input from a wide variety of vendors, and the OMG has had years to define and refine the specification. I donβt see a lowest-common-denominator committee result in the CORBA design. Rather, I see a specification thatβs open enough to bridge disparate architectures and truly genericize the idea of networked applications, in the same way the TCP/IP and HTTP have. OLE/DCOM, on the other hand, was developed in a vacuum by one company. It hasnβt been subjected to the scrutiny that CORBA has, and there hasnβt been enough buy-in from other hardware and software vendors to make it a viable competitor yet. Though thereβs no doubt that if Microsoft wishes to create a standard, it will pour enough money into it to make one. The gist is: who needs yet another incompatible architecture? The point of CORBA was to make networked systems talk seamlessly. The last thing we need is another API to worry about.β
βGates thrives on control,β said Greco. βItβs been his business philosophy for years; itβs how Microsoft has been successful. He is a brilliant strategist but a mediocre technologist. The thought of Microsoft asking us to accept ActiveX as a standard for Internet programming is just laughable, as ActiveX is inherently insecure β digital signatures donβt prevent bugs from trashing your machine. On the other hand, historically, the OMG has not been as influential as it originally hoped; it doesnβt do a good job marketing itself. If it werenβt for Netscape looking for a way to combat any distributed technology from Microsoft, the OMG may have withered on the vine, like the OSF. Certainly the failure of OpenStep hasnβt helped OMG.β
A year from now?
βCome back a year from now and Java will have made everything that happened here today ancient history,β said Jeffrey P. Morgenthal, a research analyst at D. H. Brown Associates, in Port Chester, NY. βMicrosoft, in attempting to avoid a perceived religious war, obviously thinks that they are going to come across as heroes for doing this. Theyβre not. The technology that they are giving away is simply not that good, while other technologies truly are. You have OMGβs CORBA, which is the currently preferred object specification, and then you have the up-and-coming Java online vision. Personally, I think the long-term winner in all of this, for many reasons, is going to look a lot like Java.β
During the stakeholdersβ meeting, Netscapeβs Carl Cargill was the only ISV representative to put forth the question of a possible future merger of the IIOP/CORBA and COM/DCOM technologies, asking whether TOG could work together with OMG on fusing their efforts toward universal interoperability between all platforms. βI think you would get a remarkable synergy if you could manage to merge the two,β noted Cargill. βHowever, if you do not merge the two, you will fundamentally hurt the entire object arena, and users will ultimately be the ones who get screwed, once again.β
TOGβs James Bell replied to Cargill by saying: βWe have a relationship with the OMG, and we are already looking at ways to expand it. The OMG is very important to the ISV community, which is something that we understand. So weβre hoping that in the long term we can move our positions closer together. Itβs difficult, given the circumstances. But the whole essence of open systems is about learning to live in a heterogeneous world. So weβre certainly willing to put forth a good-faith effort in moving things forward as swiftly as we possibly can.β
Bellβs statement will be put to the test sooner rather than later. Too many stakeholders in the future of open distributed computing are counting on it.


