IEEE 1224-1993

This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.

This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.

New IEEE Standard - Inactive-Withdrawn. Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.