X/Open

Last updated

X/Open group (also known as the Open Group for Unix Systems [1] [2] and incorporated in 1987 as X/Open Company, Ltd. [3] [4] ) was a consortium founded by several European UNIX systems manufacturers in 1984 [3] [5] to identify and promote open standards in the field of information technology. More specifically, the original aim was to define a single specification for operating systems derived from UNIX, to increase the interoperability of applications and reduce the cost of porting software. Its original members were Bull, ICL, Siemens, Olivetti, and Nixdorf—a group sometimes referred to as BISON. [6] Philips and Ericsson joined in 1985, [6] at which point the name X/Open was adopted.

Contents

The group published its specifications as X/Open Portability Guide, starting with Issue 1 in 1985, and later as X/Open CAE Specification.

In 1987, X/Open was incorporated as X/Open Company, Ltd. [3] [4]

By March 1988, X/Open grew to 13 members: AT&T, Digital, Hewlett-Packard, Sun Microsystems, Unisys, NCR, Olivetti, Bull, Ericsson, Nixdorf, Philips, ICL, and Siemens. [7]

By 1990 the group had expanded to 21 members: [8] in addition to the original five, Philips and Nokia from Europe; AT&T, Digital, Unisys, Hewlett-Packard, IBM, NCR, Sun, Prime Computer, Apollo Computer from North America; Fujitsu, Hitachi, and NEC from Japan; plus the Open Software Foundation and Unix International.

In October 1993, a planned transfer of UNIX trademark from Novell to X/Open was announced; [9] it was finalized in 2nd quarter of 1994. [10]

In 1994, X/Open published the Single UNIX Specification, which was drawn from XPG4 Base and other sources. [11]

In 1996, X/Open merged with the Open Software Foundation to form The Open Group. [5] [3]

X/Open was also responsible for the XA protocol for heterogeneous distributed transaction processing, which was released in 1991. [12]

X/Open Portability Guide

X/Open published its specifications under the name X/Open Portability Guide (or XPG). Based on the AT&T System V Interface Definition, [13] the guide has a wider scope than POSIX, which is only concerned with direct operating system interfaces. The guide specifies a Common Application Environment (CAE) intended to allow portability of applications across operating systems. The primary aim was compatibility between different vendors' implementations of UNIX, though some vendors also implemented the standards on non-UNIX platforms.

Issue 1 of the guide covered basic operating system interfaces, the C language, COBOL, indexed sequential file access method (ISAM) and other parts [14] and was published in 1985. [15] Issue 2 followed in 1987, [15] and extended the coverage to include Internationalization, Terminal Interfaces, Inter-Process Communication, and the programming languages C, COBOL, FORTRAN, and Pascal, as well as data access interfaces for SQL and ISAM. [16] In many cases these were profiles of existing international standards. Issue 3 (XPG3) followed in 1989, [15] its primary focus being convergence with the POSIX operating system specifications; it added Window Manager, ADA Language and more. [17] Issue 4 (XPG4) was published in July 1992. The Single UNIX Specification was based on the XPG4 standard. The XPG3 and XPG4 standards define all aspects of the operating system, programming languages and protocols which compliant systems should have.

Multiple levels of compliance and corresponding labels were available, depending on the scope of the guide that was covered: Base and Plus; labels Component and Application are for SW components and applications that make use of the portability guide. [18]

Issue 1 was published as a single publication with multiple parts, ISBN   0-444-87839-4.

Issue 2 was published in multiple volumes:

Issue 3 was published in multiple volumes:

The XPG4 Base specification includes the following documents:

The above three documents were published not under the label X/Open Portability Guide but rather as CAE Specification. [15] Nonetheless, the term X/Open Portability Guide, Issue 4 sees some use in reference to 1992 year of publication. [19] [20]

Further X/Open publications under the label X/Open CAE Specification rather than X/Open Portability Guide:

See also

Related Research Articles

<span class="mw-page-title-main">IBM AIX</span> Series of Unix operating systems from IBM

AIX is a series of proprietary Unix operating systems developed and sold by IBM for several of its computer platforms.

<span class="mw-page-title-main">Executable and Linkable Format</span> Standard file format for executables, object code, shared libraries, and core dumps.

In computing, the Executable and Linkable Format, is a common standard file format for executable files, object code, shared libraries, and core dumps. First published in the specification for the application binary interface (ABI) of the Unix operating system version named System V Release 4 (SVR4), and later in the Tool Interface Standard, it was quickly accepted among different vendors of Unix systems. In 1999, it was chosen as the standard binary file format for Unix and Unix-like systems on x86 processors by the 86open project.

The Portable Operating System Interface is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines both the system and user-level application programming interfaces (APIs), along with command line shells and utility interfaces, for software compatibility (portability) with variants of Unix and other operating systems. POSIX is also a trademark of the IEEE. POSIX is intended to be used by both application and system developers.

<span class="mw-page-title-main">Plan 9 from Bell Labs</span> Distributed operating system

Plan 9 from Bell Labs is a distributed operating system which originated from the Computing Science Research Center (CSRC) at Bell Labs in the mid-1980s and built on UNIX concepts first developed there in the late 1960s. Since 2000, Plan 9 has been free and open-source. The final official release was in early 2015.

The Single UNIX Specification (SUS) is a standard for computer operating systems, compliance with which is required to qualify for using the "UNIX" trademark. The standard specifies programming interfaces for the C language, a command-line shell, and user commands. The core specifications of the SUS known as Base Specifications are developed and maintained by the Austin Group, which is a joint working group of IEEE, ISO/IEC JTC 1/SC 22/WG 15 and The Open Group. If an operating system is submitted to The Open Group for certification, and passes conformance tests, then it is deemed to be compliant with a UNIX standard such as UNIX 98 or UNIX 03.

The Common Object Request Broker Architecture (CORBA) is a standard defined by the Object Management Group (OMG) designed to facilitate the communication of systems that are deployed on diverse platforms. CORBA enables collaboration between systems on different operating systems, programming languages, and computing hardware. CORBA uses an object-oriented model although the systems that use the CORBA do not have to be object-oriented. CORBA is an example of the distributed object paradigm.

<span class="mw-page-title-main">OpenStep</span> Defunct object-oriented application programming interface specification

OpenStep is a defunct object-oriented application programming interface (API) specification for a legacy object-oriented operating system, with the basic goal of offering a NeXTSTEP-like environment on non-NeXTSTEP operating systems. OpenStep was principally developed by NeXT with Sun Microsystems, to allow advanced application development on Sun's operating systems, specifically Solaris. NeXT produced a version of OpenStep for its own Mach-based Unix, stylized as OPENSTEP, as well as a version for Windows NT. The software libraries that shipped with OPENSTEP are a superset of the original OpenStep specification, including many features from the original NeXTSTEP.

The V operating system is a discontinued microkernel distributed operating system that was developed by faculty and students in the Distributed Systems Group at Stanford University from 1981 to 1988, led by Professors David Cheriton and Keith A. Lantz. V was the successor to the Thoth operating system and Verex kernel that Cheriton had developed in the 1970s. Despite similar names and close development dates, it is unrelated to UNIX System V.

In computer networking, the Transport Layer Interface (TLI) was the networking API provided by AT&T UNIX System V Release 3 (SVR3) in 1987 and continued into Release 4 (SVR4). TLI was the System V counterpart to the BSD sockets programming interface, which was also provided in UNIX System V Release 4 (SVR4). TLI was later standardized as XTI, the X/Open Transport Interface.

In Unix and Unix-like operating systems, iconv is a command-line program and a standardized application programming interface (API) used to convert between different character encodings. "It can convert from any of these encodings to any other, through Unicode conversion."

A software requirements specification (SRS) is a description of a software system to be developed. It is modeled after the business requirements specification(CONOPS). The software requirements specification lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.

ex, short for EXtended, is a line editor for Unix systems originally written by Bill Joy in 1976, beginning with an earlier program written by Charles Haley. Multiple implementations of the program exist; they are standardized by POSIX.

In computer networking, STREAMS is the native framework in Unix System V for implementing character device drivers, network protocols, and inter-process communication. In this framework, a stream is a chain of coroutines that pass messages between a program and a device driver. STREAMS originated in Version 8 Research Unix, as Streams.

The System V Interface Definition (SVID) is a standard that describes the AT&T UNIX System V behavior, including that of system calls, C libraries, available programs and devices. While it was not the first attempt at a standardizations document, it was an important effort in early standardization of UNIX in a period when UNIX variants were multiplying rapidly and portability was problematic at best. By 1986, AT&T required conformance with SVID issue 2 if vendors were to actually brand their products "System V R3". By the 1990s, however, its importance was largely eclipsed by POSIX and the Single UNIX Specification, which were based in part upon the SVID. Part of the reason for this was undoubtedly their vendor-independent approach.

<span class="mw-page-title-main">Common Lisp Interface Manager</span>

The Common Lisp Interface Manager (CLIM) is a Common Lisp-based programming interface for creating user interfaces, i.e., graphical user interfaces (GUIs). It provides an application programming interface (API) to user interface facilities for the programming language Lisp. It is a fully object-oriented programming user interface management system, using the Common Lisp Object System (CLOS) and is based on the mechanism of stream input and output. There are also facilities for output device independence. It is descended from the GUI system Dynamic Windows of Symbolics' Lisp machines between 1988 and 1993.

... you can check out Common Lisp Interface Manager (CLIM). A descendant of the Symbolics Lisp machines GUI framework, CLIM is powerful but complex. Although many commercial Common Lisp implementations actually support it, it doesn't seem to have seen a lot of use. But in the past couple years, an open-source implementation of CLIM, McCLIM – now hosted at Common-Lisp.net – has been picking up steam lately, so we may be on the verge of a CLIM renaissance. – From Practical Common Lisp

<span class="mw-page-title-main">Unix</span> Family of computer operating systems

Unix is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969 at the Bell Labs research center by Ken Thompson, Dennis Ritchie, and others.

The X/Open Transport Interface (XTI) is an Open Group specification for network application programming present in UNIX System V operating systems. It provides OSI transport layer services with protocol independence. Although Open Group considers this specification withdrawn, an implementation is part of the standard programming interfaces on modern UNIX System V operating systems where it is implemented using the STREAMS character input/output mechanism.

Common Programming Interface for Communications (CPI-C) is an application programming interface (API) developed by IBM in 1987 to provide a platform-independent communications interface for the IBM Systems Application Architecture-based network, and to standardise programming access to SNA LU 6.2. CPI-C was part of IBM Systems Application Architecture (SAA), an attempt to standardise APIs across all IBM platforms.

The Application Programming Interface for Windows (APIW) Standard is a specification of the Microsoft Windows 3.1 API drafted by Willows Software. It is the successor to previously proposed Public Windows Interface standard. It was created in an attempt to establish a vendor-neutral, platform-independent, open standard of the 16-bit Windows API not controlled by Microsoft.

Thoth is a real-time, message passing operating system (OS) developed at the University of Waterloo in Waterloo, Ontario Canada.

References

  1. ↑ Kornel, Amiel (3 February 1986). "Unix advancing in drive toward European market acceptance". Computerworld. p. 51.
  2. ↑ Sandholtz, Wayne (1992). "Spinoffs". High-Tech Europe: The Politics of International Cooperation. University of California Press.
  3. 1 2 3 4 "The Daemon, the GNU and the Penguin, Excursus: UUNET & Ch. 11". Groklaw . 2 June 2005.
  4. 1 2 McKinnon, Linda; McKinnon, Al (2004). Installing and Administering Linux. John Wiley & Sons. p. 5. ISBN   9780471453994.
  5. 1 2 "The UNIX System -- History and Timeline -- UNIX History". unix.org.
  6. 1 2 Tottenham, John (August 1987). "X/OPEN - What, Who, Why, When". Australian Unix systems User Group Newsletter. Vol. 8, no. 3–4. p. 158.
  7. ↑ Ackerman Jr., Robert (March 21, 1988). "X/Open Makes Bid for Common Applications Environment". InfoWorld . Vol. 10, no. 12. p. S9.
  8. ↑ Pasquali, Virgilio (Summer 2005). "ICL and Europe". RESURRECTION, the Bulletin of the Computer Conservation Society (35). ISSN   0958-7403. Contains more on history of X/Open.
  9. ↑ Karish, Chuck (October 12, 1993). "The name "UNIX" is now the property of X/Open". Newsgroup:  comp.std.unix.
  10. ↑ "Frequently Asked Questions". unix.org.
  11. ↑ "The Single UNIX Specification". unix.org.
  12. ↑ Kleppmann, Martin (April 2, 2017). Designing Data-Intensive Applications (1 ed.). O'Reilly Media. p. 361. ISBN   978-1449373320.
  13. ↑ Libes, Don; Ressler, Sandy (1989). Life With UNIX: A Guide For Everyone. Prentice Hall. p. 74. Bibcode:1989lwug.book.....L. ISBN   978-0135366578.
  14. ↑ X/Open Portability Guide, issue 1. Elsevier. July 1985. ISBN   0444878394.
  15. 1 2 3 4 Referenced Documents.{{cite book}}: |work= ignored (help)
  16. ↑ Marshall, Martin (September 19, 1988). "X/Open Verification Branding Is Established". InfoWorld . Vol. 10, no. 38. p. 42.
  17. ↑ Marshall, Martin (May 29, 1989). "X/Open Seeks Accord Between OSF, UII, Japan". InfoWorld . Vol. 11, no. 22. p. 41.
  18. ↑ Cox, John (September 19, 1988). "X/Open to make mark". Network World . Vol. 5, no. 38. p. 59.
  19. ↑ Standards Conformance Guide (PDF). Sun Microsystems. November 1995.
  20. ↑ Seebach, Peter (2010). Beginning Portable Shell Scripting: From Novice to Professional. Apress. p. 163. ISBN   978-1-4302-1044-3.
  21. ↑ Distributed Transaction Processing: The XA Specification (PDF). December 1991. ISBN   1-872630-24-3.{{cite book}}: |website= ignored (help)}
  22. ↑ Systems Management: Management Protocol Profiles (XMPP) (PDF). October 1993. ISBN   1-85912-018-0.{{cite book}}: |website= ignored (help)
  23. ↑ X/Open DCE: Remote Procedure Call (PDF). August 1994. ISBN   1-85912-041-5.{{cite book}}: |website= ignored (help)
  24. ↑ X/Open CAE Specification System Interface Definitions, Issue 4, Version 2 (PDF). September 1994. ISBN   1-85912-036-9.{{cite book}}: |website= ignored (help)
  25. ↑ X/Open CAE Specification System Interfaces and Headers, Issue 4, Version 2 (PDF). September 1994. ISBN   1-85912-037-7.{{cite book}}: |website= ignored (help)
  26. ↑ X/Open CAE Specification Commands and Utilities, Issue 4, Version 2 (PDF). September 1994. ISBN   1-85912-034-2.{{cite book}}: |website= ignored (help)
  27. ↑ X/Open CAE Specification Networking Services, Issue 4 (PDF). September 1994. ISBN   1-85912-049-0.{{cite book}}: |website= ignored (help)
  28. ↑ Data Management:SQL Call Level Interface (CLI) (PDF). March 1995. ISBN   1-85912-081-4.{{cite book}}: |website= ignored (help)
  29. ↑ File System Safe UCS Transformation Format (UTF-8) (PDF). March 1995. ISBN   1-85912-082-2.{{cite book}}: |website= ignored (help)
  30. ↑ Distributed Transaction Processing: The TX (Transaction Demarcation) Specification (PDF). April 1995. ISBN   1-85912-094-6.{{cite book}}: |website= ignored (help)
  31. ↑ X.25 Programming Interface using XTI (XX25) (PDF). November 1995. ISBN   1-85912-136-5.{{cite book}}: |website= ignored (help)
  32. ↑ Distributed Transaction Processing: The TxRPC Specification (PDF). November 1995. ISBN   1-85912-115-2.{{cite book}}: |website= ignored (help)
  33. ↑ Distributed Transaction Processing: The XATMI Specification (PDF). November 1995. ISBN   1-85912-130-6.{{cite book}}: |website= ignored (help)
  34. ↑ Distributed Transaction Processing: The XCPI-C Specification Version 2 (PDF). November 1995. ISBN   1-85912-135-7.{{cite book}}: |website= ignored (help)
  35. ↑ X/Open Curses, Issue 4. X/Open Company. 1995. ISBN   9781859120774.
  36. ↑ X/Open Curses, Issue 4, Version 2 (PDF). 1996. ISBN   1-85912-171-3.{{cite book}}: |website= ignored (help)
  37. ↑ Data Management: Structured Query Language (SQL) Version 2 (PDF). March 1996. ISBN   1-85912-151-9.{{cite book}}: |website= ignored (help)
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.