AS/NZS ISO/IEC 14753:2003

1 - AS/NZS ISO/IEC 14753:2003 INFORMATION TECHNOLOGY-OPEN DISTRIBUTED PROCESSING-INTERFACE REFERNCE AND BINDING
4 - PREFACE
5 - CONTENTS
7 - 1 Scope and Field of application
7 - 1.1 Scope
7 - 1.2 Field of Application
7 - 2 References
8 - 2.1 Identical Recommendations | International Standards
8 - 2.2 Specifications of the Object Management Group
8 - 3 Definitions
8 - 3.1 Definitions in this Recommendation | International Standard
8 - 3.2 Definitions from other Recommendations | International Standards
9 - 4 Abbreviations
10 - 5 Conventions
10 - 6 Overview of interface references and binding
10 - 6.1 Rationale
10 - 6.2 Overview of the binding process
10 - 6.2.1 Obtaining interface references
11 - 6.2.2 Binding process
11 - 6.2.3 Negotiating the properties of the binding
11 - 6.2.4 Renegotiating the properties of the binding
11 - 6.2.5 Quality monitoring and control
12 - 6.2.6 Destroying a binding
12 - 7 Enterprise viewpoint
12 - 7.1 Communities
12 - 7.2 Roles
12 - 7.2.1 Binding initiator
12 - 7.2.2 Unbinding initiator
12 - 7.2.3 Binding controller
12 - 7.2.4 Target interface creator
13 - 7.2.5 Target interface
13 - 7.2.6 Binding factory
13 - 7.2.7 Binding liaison
13 - 7.2.8 Channel
13 - 7.3 Activities
13 - 7.3.1 Interface creation
13 - 7.3.2 Binding
14 - 7.3.3 Unbinding
14 - 7.3.4 Binding management
14 - 7.3.5 Event notification
14 - 7.4 Policies
15 - 7.5 Rules
15 - 8 Information viewpoint
17 - 8.1 Binding contract
17 - 8.2 Environment contracts
17 - 8.3 Binding type
17 - 8.4 Channel type
17 - 8.5 Channel template
18 - 8.6 Interface references
18 - 8.6.1 General interpretation
19 - 8.6.2 Definition of structures
19 - 8.6.3 Definition of fields
21 - 8.6.4 Structuring interface types
22 - 8.6.5 Reducing the size of the interface reference representation
22 - 8.7 Schemata
22 - 8.7.1 Invariant schemata
23 - 8.7.2 Static schemata
23 - 8.7.3 Dynamic schemata
23 - 9 Computational Viewpoint
23 - 9.1 Computational activities related to binding
24 - 9.2 Binding establishment
24 - 9.2.1 Notations
24 - 9.2.2 Binding protocol
26 - 9.3 Channel establishment
26 - 9.4 Channel optimizations
26 - 9.4.1 Pre-allocation of channel resources
26 - 9.4.2 Re-binding
26 - 9.4.3 Use of recursive binding
27 - 9.4.4 Elimination of unnecessary channel components
27 - 9.5 Reducing amount of interface reference related data
27 - 9.6 Security
27 - 9.7 Failures
27 - 9.8 Functions
28 - 10 Federation
28 - 10.1 Transfer of interface references
29 - 10.2 Name resolution and locating the endpoints of the binding
29 - 10.3 Construction of the binding and resource allocation
30 - 11 Compliance
31 - Annex A - Mapping of interface reference abstract syntax to CORBA IIOP-IOR format
31 - A.1 Direct interface references
31 - A.2 Non-interpreted interface references
32 - A.3 Binding procedures
33 - A.4 Marshalling
33 - A.5 Unmarshalling
34 - Annex B - Binding interpreter interface
35 - Annex C - Bibliography
36 - Annex D - Examples
36 - EXAMPLE 1 – STREAM INTERFACE RULES
36 - EXAMPLE 2 – STREAM INTERFACE RULES
37 - Index

Provides interface references that embody the information needed to establish bindings, including binding to objects at nodes that support several different communication protocols and binding to objects in different management domains. It further embodies the information required for the engineering mechanism to maintain bindings between computational objects in the presence of distribution transparencies such as migration transparency.

Interface references are crucial to interworking between ODP systems and federation of groups of ODP systems. An interface reference embodies the information needed to establish bindings, including binding to objects at nodes thatsupport several different communication protocols and binding to objects in different management domains. An interface reference further embodies the information required for the engineering mechanism to maintain bindings between computational objects in the presence of distribution transparencies such as migration transparency. They are the foundation of ODP location and relocation transparency.This Recommendation | International Standard includes:- a framework for binding interfaces and a generic binding protocol (for both stream and operational interfaces);- a specification of the generic information structure of interface references (for both stream and operational interfaces);- representation(s) for interface references when transferred using standardized protocols;- identification of procedures for the management and transfer of interface references with respect to individual transparencies;- identification of node management interfaces related to binding and federation which create or transform interface references;- identification of requirements for quality of service information and for invocation of QoS or related measurement procedures.This Recommendation | International Standard provides an engineering description of the functionality needed to support the computational binding of objects in ODP systems. Security and support for group communication are important issues, but not within the scope of this Recommendation | International Standard.

First published as AS/NZS ISO/IEC 14753:2003.