1 @(#)REFERENCES 1.2 95/11/08
5 Most of the relevant references here are to OMG documents, however there
6 are a few external references of some note:
8 * http://www.uci.agh.edu.pl/research/cs/TOCOOS/COPERNICUS.html
13 As of this writing, OMG is in the process of publishing new versions of the
14 base CORBA specifications, merging specifications as needed into single
15 documents and splitting out the C mapping from the CORBA/CORE specification.
17 This software has made every effort to track both the base documents and the
18 agreed corrections and revisions. Since those documents have not yet been
19 published, there will inevitably be areas in which it does not reflect the
20 versions yet to be published. See the "DIFFERENCES" file for information
21 about where this software differs from these current base documents:
23 * CORBA 2.0/Interoperability: Universal Networked Objects (UNO), OMG
24 TC Document 95-3-10. This includes the mandatory IIOP and bridging
25 support, as well as the optional DCE-CIOP protocol.
27 * CORBA 1.2 specification, OMG TC Document 93-12-43. This is the
28 base document on which the CORBA 2.0 CORE specifications build.
30 * Universal Networked Objects (UNO), OMG TC Document 94-9-32. Until
31 the CORBA 2.0/CORE document is published, replacing the CORBA 1.2,
32 initialisation, and IFR specifications, you must use this earlier
33 version of UNO to see (only!) the specification for DSI and several
34 other CORBA CORE extensions (for bridging) adopted by the OMG.
35 [ NOTE: use the IIOP specification in 95-3-10, not the one here;
36 95-3-10 has changes required by the IFR specification, 95-11-7. ]
38 * Initialisation, OMG TC Document 94-10-24. This defines the portable
39 APIs for initialising ORBs.
41 * Interface Repository, OMG TC Document 94-11-7. This updates the
42 CORBA specifications above and is referenced by the UNO document.
44 * IDL C++ Language Mapping Specification, OMG TC Document 94-9-14.
45 This defines the mapping of CORBA 1.2, including OMG-IDL, onto C++.
47 There are a few inconsistencies between these documents, which are in the
48 process of being resolved. The inconsistencies arose because different
49 groups worked on different parts of the system, at different times and
50 with some different goals. Contact the various revision committees to
51 find out how these differences are being resolved:
53 - interop@omg.org ... the interop revision task force (RTF)
54 - cxx_revision@omg.org ... the C++ RTF
55 - orb_revision@omg.org ... the general ORB RTF
57 Also, note that these ORB specifications correspond to only the lowest levels
58 of OMG's Object Management Architecture. In particular, the "Object Services"
59 define object interfaces for naming, events, persistence, relationships,
60 lifecycle, externalization, transactions, and concurrency control. Also,
61 "Common Facilities" objects will address such things as compound document
62 architecture. If you intend to develop software based on ORBs, these
63 specifications are likely to be of interest. The OMA is available in
66 Richard Soley (ed.), Object Management Architecture Guide,
67 Second Edition, John Wiley & Sons, New York, 1992.
70 ACQUIRING REFERENCE DOCUMENTS
71 -----------------------------
72 To acquire those reference documents, use the OMG document server through
73 Internet email. Send a message to "server@omg.org", with content lines
78 to get directions about how to use the server, or
82 to get a PostScript copy of any particular document. (OMG specifications
83 are available only in PostScript.)
85 The OMG document server is maintained for use by OMG members, but is also
86 available for general Internet access. Only members will be supported in
89 To find out more about the OMG, send email to "omg@omg.org", or look
90 at the Web page at "http://www.omg.org".