Information technology — Object management group — Interface definition language (IDL) 4.2
Introduction: The rapid growth of distributed processing has led to a need for a coordinating framework for this standardization and ITU-T Recommendations X.901-904 | ISO/IEC 10746, the Reference Model of Open Distributed Processing (RM-ODP) provides such a framework. It defines an architecture within which support of distribution, interoperability, and portability can be integrated. RM-ODP Part 2 (ISO RM-ODP Part 2 (ISO/IEC 10746-2) defines the foundational concepts and modeling framework for describing distributed systems. The scopes and objectives of the RM-ODP Part 2 and the UML, while related, are not the same and, in a number of cases, the RM-ODP Part 2 and the UML specification use the same term for concepts which are related but not identical (e.g., interface). Nevertheless, a specification using the Part 2 modeling concepts can be expressed using UML with appropriate extensions (using stereotypes, tags, and constraints). RM-ODP Part 3 (ISO/IEC 10746-3) specifies a generic architecture of open distributed systems, expressed using the foundational concepts and framework defined in Part 2. Given the relation between UML as a modeling language and Part 3 of the RM-ODP standard, it is easy to show that UML is suitable as a notation for the individual viewpoint specifications defined by the RM-ODP. This International Standard defines a method for automating the counting of Function Points that is generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPU
Scope: 1.1 Overview This International Standard specifies the OMG Interface Definition Language (IDL). IDL is a descriptive language used to define data types and interfaces in a way that is independent of the programming language or operating system/processor platform. The IDL specifies only the syntax used to define the data types and interfaces. It is normally used in connection with other standards that further define how these types/interfaces are utilized in specific contexts and platforms: • Separate “language mapping” standards define how the IDL-defined constructs map to specific programming languages, such as, C/C++, Java, C#, etc. • Separate “serialization” standards define how data objects and method invocations are serialized into a format suitable for network transmission. • Separate “middleware” standards, such as, DDS or CORBA leverage the IDL to define data-types, services, and interfaces. The description of IDL grammar uses a syntax notation that is similar to Extended Backus-Naur Format (EBNF). 2 Conformance Criteria This International Standard defines IDL such that it can be referenced by other standards. It contains no independent conformance points. It is up to the standards that depend on this International Standard to define their own conformance criteria. However, the general organization of the clauses (by means of atomic building blocks and profiles that group them) is intended to ease conformance description and scoping. That means that no standard using IDL 4.0 will be forced to be compliant with IDL constructs that are not relevant in its usage of IDL. Conformance to this International Standard must follow these rules: 1. Future standards that use IDL shall reference this IDL International Standard or a future revision thereof. 2. Future revisions of current standards that use IDL may reference this IDL International Standard or a future revision thereof. 3. Reference to this International Standard shall result in a selection of building blocks possibly complemented by groups of annotations. a. All selected building blocks shall be supported entirely. b. Selected annotations shall be either supported as described in 8.2.2 Rules for Using S
Contents:
- Foreword
- Introduction
- Scope
- 1.1 Overview
- 6.1 Acknowledgments
- 6.2 History
- 7.1 Overview
- 7.2 Lexical Conventions
- 7.2.1 Tokens
- 7.2.2 Comments
- 7.2.3 Identifiers
- 7.2.4 Keywords
- 7.2.5 Other Characters Recognized by IDL
- 7.2.6 Literals
- 7.3 Preprocessing
- 7.4 IDL Grammar
- 7.4.1 Building Block Core Data Types
- 7.4.2 Building Block Any
- 7.4.3 Building Block Interfaces — Basic
- 7.4.4 Building Block Interfaces — Full
- 7.4.5 Building Block Value Types
- 7.4.6 Building Block CORBA-Specific — Interfaces
- 7.4.7 Building Block CORBA-Specific — Value Types
- 7.4.8 Building Block Components — Basic
- 7.4.9 Building Block Components — Homes
- 7.5 Names and Scoping
- 7.5.1 Qualified Names
- 7.5.2 Scoping Rules and Name Resolution
- 7.5.3 Special Scoping Rules for Type Names
- 8.1 Overview