Information technology — Abstract Syntax Notation One (ASN.1) — Part 4: Parameterization of ASN.1 specifications
Introduction: Application designers need to write specifications in which certain aspects are left undefined. Those aspects will later be defined by one or more other groups (each in its own way), to produce a fully defined specification for use in the definition of an abstract syntax (one for each group). In some cases, aspects of the specification (for example, bounds) may be left undefined even at the time of abstract syntax definition, being completed by the specification of International Standardized Profiles or functional profiles from some other body. NOTE 1 – It is a requirement imposed by this Recommendation | International Standard that any aspect that is not solely concerned with the application of constraints has to be completed prior to the definition of an abstract syntax. In the extreme case, some aspects of the specification may be left for the implementer to complete, and would then be specified as part of the Protocol Implementation Conformance Statement. While the provisions of Rec. ITU-T X.681 | ISO/IEC 8824-2 and Rec. ITU-T X.682 | ISO/IEC 8824-3 provide a framework for the later completion of parts of a specification, they do not of themselves solve the above requirements. Additionally, a single designer sometimes requires to define many types, or many information object classes, or many information object sets, or many information objects, or many values, which have the same outer level structure, but differ in the types, or information object classes, or information
Scope: This Recommendation | International Standard is part of Abstract Syntax Notation One (ASN.1) and defines notation for parameterization of ASN.1 specifications.
Contents: