Information Object Class (ASN.1) - Introduction

Introduction

The simplest way of thinking of ASN.1 Information Object Classes is to regard them as a way to represent IDL specification in ASN.1 using concepts derived from the relational databases theory and SQL syntax in particular.

The concepts used in ASN.1 are more flexible than the ones used in IDL, because, continuing the analogy, they allow to "customize grammar" of the "IDL specification". ASN.1 encoding rules are used as a transfer syntax for remote invocations that resemble CORBA/IIOP.

In the light of this comparison, we can draw an approximate analogy between concepts used in Information Object Classes and SQL and IDL concepts as shown in Table 1.

Table 1: Analogy between concepts in ASN.1 Information Object Classes, SQL, and IDL
ASN.1 term Analogy in SQL Analogy in IDL

Information Object Class (IOC)

SQL table structure descriptor (CREATE TABLE statement)

IDL grammar specification (BNF rules)

IOC field declaration

SQL table column descriptor in CREATE TABLE statement (type of a column)

IDL grammar production

Information Object (IO)

SQL table row (INSERT INTO statement)

IDL operation declaration

IO field definition

Cell of SQL table row in INSERT INTO statement (cell value)

Portion of IDL operation declaration, typically related to declaration of an operation type code, parameter list, operation return value, or list of exceptions

Information Object Set (IOS) (collection of Information Objects)

Completely defined SQL table (collection of rows) (see Note 1)

IDL interface definition (collection of operations)

ASN.1 data type using references to IOC fields parameterized with IOS (typically a collection of semantically related types designating request, response, and exception, all parameterized with the same IOS)

-

High-level format (grammar specification) of a frame (marshalling buffer) carrying CORBA request, response, or exception

ASN.1 encoding rules and transfer syntaxes (BER, PER)

-

Low-level encoding of requests, responses and exception indicators suitable for physical transfer over the medium

Note 1. The analogy between IOS and an SQL table is not quite correct. SQL permits only one instance of a table of given type (OPERATION in the example below), while ASN.1 permits multiple Information Object Sets derived from the same Information Object Class, what should be most correctly related to multiple instances of the same table in terms of SQL (OPERATION in the example below).

Read more about this topic:  Information Object Class (ASN.1)

Famous quotes containing the word introduction:

    “Such is oftenest the young man’s introduction to the forest, and the most original part of himself. He goes thither at first as a hunter and fisher, until at last, if he has the seeds of a better life in him, he distinguishes his proper objects, as a poet or naturalist it may be, and leaves the gun and fish-pole behind. The mass of men are still and always young in this respect.”
    —Henry David Thoreau (1817–1862)

    “For better or worse, stepparenting is self-conscious parenting. You’re damned if you do, and damned if you don’t.”
    —Anonymous Parent. Making It as a Stepparent, by Claire Berman, introduction (1980, repr. 1986)

    “For the introduction of a new kind of music must be shunned as imperiling the whole state; since styles of music are never disturbed without affecting the most important political institutions.”
    —Plato (c. 427–347 B.C.)