Resources
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
abstract character: The set of information, usually including one or more graphic symbols, character names, or related function definitions, that are associated with a cell in a table used to define a character repertoire.
(See X.680, 3.6.1)
abstract syntax value: Synonymous with "abstract value". A value of an abstract syntax (defined as the set of values of a single ASN.1 type), which is to be encoded by BER, CER, DER or PER, or which is to be generated by BER, CER, DER, or PER decoding.
(See X.691, 3.6.2)
abstract value: A value defined only on the basis of its type, and not dependent on its representation by any encoding rule. Note that when the term "abstract value" is used, it commonly indicates that what is being described varies by the encoding rule being used.
(See X.680, 3.6.2)
ACSE: Association Control Service Element.
alignment point: The point in an encoding (usually its start) which serves as a reference point when an encoding specification requires alignment to some boundary.
(See X.692, 3.2.1)
ANSI: American National Standards Institute
(See X.680, 4)
API: Application Program Interface
(See X.680, 4)
ASN.1: Abstract Syntax Notation One
(See X.680, 4)
ASN.1 C++ API: An API that supports access to abstract data in the form of Abstract Syntax Notation One (ASN.1) types and values.
ASN.1 character set: The set of characters used to form the ASN.1 notation.
(See X.680, 3.6.3)
ASN.1 schema: The definition of the content and structure of data using an ASN.1 type definition.
(X.693, 3.2.1)
ASN.1 specification: An ASN.1 module, or collection of related ASN.1 modules, used to form the set of messages in an application protocol.
(See X.680, 3.6.4)
associated table: An abstract table, derivable from the object or object set by flattening the hierarchical structure resulting from the presence of link fields.
(See X.681, 3.4.1)
associated type: An ASN.1 type used only for defining the value and subtype notation of some other type. Associated types are defined in standards as necessary to make it clear that there may be significant differences between the type ASN.1 defines and the way it is encoded. Associated types are not part of user specifications.
(See X.680, 3.6.5)
auxiliary field: A field of a replacement structure (that is added in the ECN specification) whose value is set directly by the encoder without the use of any abstract value provided by the application.
(See X.692, 3.2.2)
AVA: Attribute Value Assertion
BCD: Binary Coded Decimal
(See X.692, 4)
BER: Basic Encoding Rules of ASN.1
(See X.680, 4)
bit-field: The product of the PER encoding mechanism that consists of an ordered set of bits that are not necessarily a multiple of eight, and do not necessarily begin on an octet boundary in the complete encoding of the abstract syntax value.
(See X.691, 3.6.3)
bitstring type: A simple type whose distinguished values are an ordered sequence of zero or more bits.
(See X.680, 3.6.6)
Boolean type: A simple type that has two distinguished values, true or false.
(See X.680, 3.6.7)
bounds condition: A condition on the existence of bounds of an integer field (and whether they allow negative values or not) which, if satisfied, means that specified encoding rules are to be applied.
(See X.692, 3.2.5)
BMP: Basic Multilingual Plane
(See X.680, 4)
canonical encoding: A complete encoding of an abstract syntax value obtained by the application of encoding rules that have no implementation-dependent options; such rules result in the definition of a 1-1 mapping between unambiguous and unique bitstrings in the transfer syntax and values in the abstract syntax.
(See X.691, 3.6.4)
CCITT: International Telegraphic and Telecommunications Consultative Committee (now known as ITU-T)
CER: Canonical Encoding Rules of ASN.1
(See X.691, 4)
character property: A member of a set of elements used for the organization, control or representation of data.
(See X.680, 3.6.8)
character abstract syntax: A set of characters described independently of their encodings.
(See X.680, 3.6.9)
character repertoire: A set of characters described independently of their encodings.
(See X.680, 3.6.10)
character transfer syntax: A transfer syntax for some character abstract syntax, in which all character strings are encoded as an integral multiple of 8 bits.
(See X.680, 3.6.12)
choice determinant: A bit-field which determines which of several possible encodings (each representing different abstract values) is present in some other bit-field.
(See X.692, 3.2.6)
choice types: Types that are defined by referencing a list of distinct types, so that each value of the choice type is derived from the value of one of the component types.
(See X.680, 3.6.13)
CMIP: Common Management Information Protocol
CMIS: Common Management Information Services
CMISE: Common Management Information Service Element
combined encoding object set: A temporary set of encoding objects produced by the combination of two sets of encoding objects for the purpose of applying encodings
(See X.692, 3.2.7)
component relation constraint: A constraint on a component of a SET or SEQUENCE that establishes a relationship between the value or type of that component (the referencing component) and the value or type of one or more other components of the same SET or SEQUENCE (referenced components).
(See X.682, 3.4.1)
component type: One of the types referenced when a choice, set, sequence, set-of, or sequence-of is defined.
(See X.680, 3.6.14)
composite type: A set, sequence, set-of, sequence-of, choice, embedded-pdv, external or unrestricted character-string type.
(See X.691, 3.8.5)
composite value: The value of a composite type.
(See X.691, 3.6.6)
concrete syntax: Those aspects of the rules used in the formal specification of data which embody a specific representation of that data in some system environment. Within a real open system, data defined in terms of an abstract syntax will be represented within the local system environment by a local concrete syntax. In communication between real open systems, there are three concrete syntax versions of the data: the concrete syntax used by the sender, the concrete syntax used by the receiver, and the concrete syntax used between the sender and receiver (transfer syntax). In practice, all three of these local concrete syntax versions may be identical, or transformations between these syntax versions may be required.
(See X.200, 7.2.1.1)
conditional encoding: An encoding which is to be applied only if some specified bounds condition or size range condition is satisfied
(See X.692 3.2.8)
contents octets: That part of a data value encoding which represents a particular value, to distinguish it from other values of the same type.
(See X.690, 3.3)
constrained type: The innermost "Type" which contains the referencing component and all of the referenced components of a component relation constraint.
(See X.682, 3.4.2)
constrained whole number: A whole number which is constrained by PER-visible constraints to lie within a range from "lb" to "ub" with the value "lb" less than or equal to "ub", and the values of "lb" and "ub" as permitted values.
(See X.691, 3.6.7)
constraining set: The information object set referenced in a component relation constraint.
(See X.682, 3.4.3)
constraining table: The conceptual table formed from an information object set including all information object sets that it may directly or indirectly reference).
(See X.682, 3.4.4)
constraint: A notation used in association with some type, to define a subtype of that type.
(See X.680, 3.6.15)
constructed encoding: A data value encoding in which the contents octets are the complete encoding of one or more data values.
(See X.690, 3.2)
containing type: An ASN.1 type (or encoding structure field) where a contents constraint has been applied to the values of that type (or to the values associated with that encoding structure field).
(See X.692 3.2.9)
contents constraint: A constraint on a bit string or octet string type that specifies either that the contents are to be an encoding of a specified ASN.1 type, or that specified procedures are to be used to produce and process the contents
(See X.680, 3.6.16)
control characters: Named characters, which are not spacing characters, that appear in some character repertoires, but that have not been assigned a graphic symbol, such as the NEWLINE and TAB control characters.
(See X.680, 3.6.17)
Coordinated Universal Time (UTC): The time scale maintained by the Bureau Internationale de l'Heure (International Time Bureau) that forms the basis of a coordinated dissemination of standard frequencies and time signals.
(See X.680, 3.6.18)
CSTA: Computer Supported Telecommunications Applications
CTI: Computer Telephony Integration
current application point: The point in an encoding structure at which a combined encoding object set is being applied.
(See X.692, 3.2.10)
data value: Information specified as the value of a type; the type and the value are defined using ASN.1.
(See X.690, 3.4)
DCC: Data Country Code
(See X.680, 4)
DER: Distinguished Encoding Rules of ASN.1
(See X.691, 4)
default syntax: The notation which shall be used for defining information objects of classes whose definers did not provide a WITH SYNTAX specification in the class definition.
(See X.681, 3.4.2)
defined syntax: A notation provided by the definer of a class by means of a WITH SYNTAX specification.
(See X.681, 3.4.3)
differential encoding-decoding: The specification of rules for a decoder that require the acceptance of encodings that cannot be produced by an encoder conforming to the current specification.
(See X.692, 3.2.11)
DIS: Draft International Standard
DMI: Definition of Management Information
(See X.721 | 10165-2 [DMI])
DN: Distinguished Name
DNIC: Data Network Identification Code
(See X.680, 4)
dynamic conformance: A statement of the requirement for an implementation to adhere to the behavior prescribed by the ASN.1 standard in an instance of communication.
(See X.690, 3.5)
ECN: Encoding Control Notation of ASN.1
(See X.680, 4)
EDM: Encoding Definition Module
(See X.692, 4)
ELM: Encoding Link Module
(See X.692, 4)
EFD: Event Forwarding Discriminator
effective size constraint : A single finite size constraint that could be applied to a built-in string type and whose effect would be to permit all and only those lengths that can be present in the constrained string type.
(See X.691, 3.6.8)
effective PermittedAlphabet constraint: A single PermittedAlphabet constraint that could be applied to a built-in known-multiplier character string type and whose effect would be to permit all and only those characters that can be present in any character position of any of the values in the constrained restricted character string type.
(See X.691, 3.6.9)
element: A distinguished member of an element class, that can be identified from all other elements of its class.
(See X.680, 3.6.19)
element set: One or more distinguished elements of an element class.
(See X.680, 3.6.20)
embedded-pdv type: A type whose set of values is the union of the sets of values in all possible abstract syntaxes. Such types are part of an ASN.1 specification, though they may carry values whose types may be defined externally to that ASN.1 specification.
(See X.680, 3.6.21)
encoding: The bit-pattern resulting from the application of a set of encoding rules to a value of a specific abstract syntax.
(See X.680, 3.6.22)
encoding (of a data value): The complete sequence of octets used to represent the data value.
(See X.690, 3.6)
encoding class: The set of all possible encodings for a specific part of the procedures needed to perform the encoding or decoding of an ASN.1 type.
(See X.692, 3.2.12)
encoding class category: Encoding classes with some common characteristics.
(See X.692, 3.2.13)
encoding constructor: An encoding class whose encoding objects define procedures for combining, selecting, or repeating parts of an encoding.
(See X.692, 3.2.14)
Encoding Definition Modules (EDM): Modules that define encodings for application in the Encoding Link Module.
(See X.692, 3.2.15)
Encoding Link Module (ELM): The (unique, for any given application) module that assigns encodings to ASN.1 types.
(See X.692, 3.2.16)
encoding object: The specification of some part of the procedures needed to perform the encoding or decoding of an ASN.1 type.
(See X.692, 3.2.17)
encoding object set: A set of encoding objects.
(See X.692, 3.2.18)
encoding rules: ASN.1 rules which specify the representation during transfer of the values of ASN.1 types, and also enable the values to be recovered from the representation, given knowledge of the type.
(See X.680, 3.6.23)
encoding space: The number of bits (or octets, words or other units) used to encode an abstract value into a bit-field.
(See X.692, 3.2.20)
encoding structure: The structure of an encoding, defined either from the structure of an ASN.1 type definition, or in an EDM using bit-field classes and encoding constructors.
(See X.692, 3.2.21)
end-of-contents octets: A data value encoding delimiter used to determine the end of an encoding.
(See X.690, 3.7)
enumerated types: Simple types whose values are given distinct identifiers as part of the type notation.
(See X.680, 3.6.24)
enumeration index: The non-negative whole number associated with an "EnumerationItem" in the PER encoding of an enumerated type. The enumeration indices are determined by sorting the "EnumerationItem"s into ascending order by their enumeration value, then by assigning an enumeration index starting with zero for the first "EnumerationItem", one for the second, and so on up to the last "EnumerationItem" in the sorted list.
(See X.691, 3.6.10)
explicitly generated encoding structure: An encoding structure derived from an implicitly generated encoding structure by use of the renames clause in an EDM.
(See X.692, 3.2.22)
extensible for PER encoding: A property of a type whose definition contains an extension marker that affects the PER encoding.
(See X.691, 3.6.11)
extensibility: Provisions in an early version of a standard that are designed to maximize the interworking of implementations of that early version with the expected implementations of a later version of that standard.
(See X.692, 3.2.23)
extension addition: One of the added notations in an extension series. For set, sequence and choice types, each extension addition is the addition of either a single extension addition group or a single component type. For enumerated types it is the addition of a single further enumeration. For a constraint it is the addition of (only) one subtype element.
(See X.680, 3.6.25)
extension addition group: One or more components of a set, sequence or choice type grouped within version brackets. An extension addition group is used to clearly identify the components of a set, sequence or choice type that were added in a particular version of an ASN.1 module, and can identify that version with a simple integer.
(See X.680, 3.6.26)
extension addition type: A type contained within an extension addition group or a single component type that is itself an extension addition (in such a case it is not contained within an extension addition group).
(See X.680, 3.6.27)
extensible constraint: A subtype constraint with an extension marker at the outer level, or that is extensible through the use of set arithmetic with extensible sets of values.
(See X.680, 3.6.28)
extension insertion point (or insertion point): The location within a type definition where extension additions are inserted. This location is the end of the type notation of the immediately preceding type in the extension series if there is a single ellipsis in the type definition, or immediately before the second ellipsis if there is an extension marker pair in the definition of the type.
(See X.680, 3.6.29)
extension marker: A syntactic flag (an ellipsis) that is included in all types that form part of an extension series.
(See X.680, 3.6.30)
extension marker pair: A pair of extension markers between which extension additions are inserted.
(See X.680, 3.6.31)
extension-related: Two types that have the same extension root, where one was created by adding zero or more extension additions to the other.
(See X.680, 3.6.32)
extension root: An extensible type that is the first type in an extension series. It carries either the extension marker with no additional notation other than comments and white-space between the extension marker and the matching "}" or ")", or an extension marker pair with no additional notation other than a single comma, comments and white-space between the extension markers.
(See X.680, 3.6.33)
extension series: A series of ASN.1 types which can be ordered in such a way that each successive type in the series is formed by the addition of text at the extension insertion point.
(See X.680, 3.6.34)
external reference: A type reference, value reference, information object, etc., that is defined in some other module than the one in which it is being referenced.
(See X.680, 3.6.36)
external type: A type which is a part of an ASN.1 specification that carries a value whose type may be defined externally to that ASN.1 specification.
(See X.680, 3.6.37)
false: One of the distinguished values "true" or "false" of the Boolean type.
(See X.680, 3.6.38)
field: A component of an information object class.
(See X.681, 3.4.5)
field-list: An ordered set of bit-field and/or octet-aligned-bit-field values that is produced as a result of applying these encoding rules to components of a value.
(See X.691, 3.6.12)
field name: A name which identifies a field of some class
(See X.681, 3.4.6)
FIPS: Federal Information Processing Standards
fixed-length type: A type such that the value of the outermost length determinant in an encoding of this type can be determined from the type notation (after the application of PER-visible constraints only) and is the same for all possible values of the type.
(See X.691, 3.6.14)
fixed value: A value such that it can be determined that this is the only permitted value (after the application of PER-visible constraints only) of the type governing it.
(See X.691, 3.6.15)
fully-qualified name: A reference to an encoding class, object, or object set that includes either the name of the EDM module in which that encoding class, object, or object set was defined, or (in the case of an implicitly generated encoding class) the name of the ASN.1 module in which it was generated.
(See X.692, 3.2.24)
GDMO: Guidelines for the Definition of Managed Objects
generated encoding structure: An implicitly or explicitly generated encoding structure whose purpose is to define the encodings of the corresponding ASN.1 type through application of encodings in the ELM.
(See X.692, 3.2.25)
Generic API: An API that provides access to an open set of managed object classes and/or ASN.1 types, i.e., managed object classes and types are not necessarily known at compile time.
governing; governor: Relative to some object, object set, value set, value or subtype, the information object class or type which controls its interpretation by restricting the items(s) involved to be value notation of that class or type, respectively.
(See X.680, 3.6.39)
Green API: (See GDMO C++ API)
GUI: Graphical User Interface
GULS: Generic Upper Layer Security
HOB: Hierarchical Operational Binding
I18N: Internationalization
ICD: International Code Designator
(See X.680, 4)
identification handle: Part of an encoding which serves to distinguish encodings of one encoding class from those of other encoding classes.
(See X.692, 3.2.27)
identifier field: A fixed-type value field of a class, selected to provide unique identification of information objects in that class.
(See X.681, 3.4.8)
identifier octets: Part of a data value encoding which is used to identify the type of the value.
(See X.690, 3.8)
implicitly generated encoding structure: The encoding structure that is implicitly generated and exported whenever a type is defined in an ASN.1 module.
(See X.692, 3.2.28)
initial application point: The point in an encoding structure at which any given combined encoding object set is first applied (in the ELM and in EDMs) .
(See X.692, 3.2.29)
IDL: Interface Definition Language
IEC: International Electrotechnical Commission
(See X.680, 4)
indefinite-length: An encoding whose length is greater than 64K-1 or whose maximum length cannot be determined from the ASN.1 notation.
(See X.691, 3.6.13)
information object: An instance of some information object class, being composed of a set of fields which conform to the field specifications of the class.
(See X.681, 3.4.9)
information object class (class): A set of fields, forming a template for the definition of a potentially unbounded collection of information objects, the instances of the class.
(See X.681, 3.4.10)
information objet field: A field which contains an information object of some specified class.
(See X.681, 3.4.11)
information object set: A non-empty set of information objects, all of the same information object class.
(See X.681, 3.4.11)
information object set field: A field which contains an information object set of some specified class.
(See X.681, 3.4.13)
instance-of type: A type, defined by referencing an information object class which associates object identifiers with types.
(See X.681, 3.4.14)
integer type: A simple type with distinguished values which are the positive and negative whole numbers, including zero (as a single value).
(See X.680, 3.6.41)
IS: International Standard
ISO: International Organization for Standardization
(See X.680, 4)
ISP: International Standardized Profile
ISV: Independent Software Vendor
items: Named sequences of characters from the ASN.1 character set, which are used to form the ASN.1 notation.
(See X.680, 3.6.42)
ITU-T: Telecommunication Standardization Sector of the International Telecommunication Union
(See X.680, 4)
known-multiplier character string type: A restricted character string type where the number of octets in the encoding is a known fixed multiple of the number of characters in the character string for all permitted character string values. The known-multiplier character string types are IA5String, PrintableString, VisibleString, NumericString, UniversalString and BMPString.
(See X.691, 3.6.16)
LDN: Local Distinguished Name
length determinant: A count (of bits, octets, characters, or components) determining the length of part or all of a PER encoding.
(See X.691, 3.6.17)
length octets: Part of a data value encoding following the identifier octets which is used to determine the end of the encoding.
(See X.690, 3.9)
lexical items: Named sequences of characters from the ASN.1 character set, which are used to form the ASN.1 notation.
(See X.680, 3.6.42)
link field: An object or object set field.
(See X.681, 3.4.14)
Manager Role: The manager role application operates on the managed object references, without being aware of where the managed objects are instantiated.
MHS: Message Handling Systems
(See X.400)
MIM: Management Information Model
(See X.720)
MIT: Management Information Tree (also known as Naming Tree).
(See X.400)
MOCS: Managed Object Conformance Statement
module: One or more instances of the use of the ASN.1 notation for type, value, etc., encapsulated using the ASN.1 module notation.
(See X.680, 3.6.43)
Naming Tree: (See MIT)
non-negative-binary-integer encoding: The encoding of a constrained or semi-constrained whole number into either a bit-field of a specified length, or into an octet-aligned-bit-field of a specified length, or into the minimum number of octets that will accommodate that whole number encoded as a non-negative-binary-integer which provides representations for whole numbers greater than or equal to zero.
(See X.691, 3.8.21)
normal reference name: A reference name defined, without parameters, by means of an "Assignment" other than a "ParameterizedAssignment". Such a name references a complete definition and is not supplied with actual parameters when used.
(See X.683, 3.4.1)
normally small length: A length encoding which represents values of an unbounded length, but where small lengths are more likely to occur than large ones.
(See X.691, 3.6.19)
normally small non-negative whole number: A part of an encoding which represents values of an unbounded non-negative integer, but where small values are more likely to occur than large ones.
(See X.691, 3.6.18)
non-negative-binary-integer encoding : The encoding of a constrained or semi-constrained whole number into either a bit-field of a specified length, or into a bit-field (octet-aligned in the ALIGNED variant) of a specified length, or into the minimum number of octets that will accommodate that whole number encoded as a non-negative-binary-integer which provides representations for whole numbers greater than or equal to zero.
(See X.691, 3.6.20)
null type: A simple type consisting of a single value, also called null.
(See X.680, 3.6.44)
object: A well-defined piece of information, definition, or specification which requires a name in order to identify its use in an instance of communication.
(See X.680, 3.6.45)
object class field type: A type specified by reference to some field of an information object class.
(See X.681, 3.4.16)
object descriptor type: A type whose distinguished values are human-readable text providing a brief description of an object.
(See X.680, 3.6.46)
object identifier: A value (distinguishable from all other such values) which is associated with an object.
(See X.680, 3.6.47)
object identifier type: A simple type whose distinguished values are the set of all object identifiers allocated in accordance with the rules of the X.680 standard.
(See X.680, 3.6.48)
octet-aligned-bit-field: The product of some part of the encoding mechanism that consists of an ordered set of bits that are not necessarily a multiple of eight, but which are required to begin on an octet boundary in the complete encoding of the abstract syntax value.
(See X.691, 3.8.20)
octetstring type: A simple type whose distinguished values are an ordered sequence of zero or more octets, each octet being an ordered sequence of eight bits.
(See X.680, 3.6.49)
OER: Octet Encoding Rules of ASN.1
(See Rec. ITU-T X.696 | ISO/IEC 8825-7 Octet Encoding Rules (OER) Base Protocol)
OID: Object Identifier
(See X.680, 4)
OMG: Object Management Group
open type notation : An ASN.1 notation used to denote a set of values from more than one ASN.1 type.
(See X.680, 3.6.51)
optional bit-field: A bit?field that is sometimes included (to encode an abstract value) and is sometimes omitted.
(See X.692, 3.2.34)
OS: Operating System or Operations System
OSI: Open Systems Interconnection
(See X.680, 4)
parameterized reference name: A reference name defined using a parameterized assignment, which references an incomplete definition and which, therefore, must be supplied with actual parameters when used.
(See X.683, 3.4.2)
parameterized type: A type defined using a parameterized type assignment and thus whose components are incomplete definitions which must be supplied with actual parameters when the type is used.
(See X.683, 3.4.3)
parameterized value: A value defined using a parameterized value assignment and thus whose value is incompletely specified and must be supplied with actual parameters when used.
(See X.683, 3.4.4)
parameterized value set: A value set defined using a parameterized value set assignment and thus whose values are incompletely specified and must be supplied with actual parameters when used.
(See X.683, 3.4.5)
parameterized object: An information object defined using a parameterized object assignment and thus whose components are incompletely specified and must be supplied with actual parameters when used.
(See X.683, 3.4.7)
parameterized object class: An information object class defined using a parameterized object class assignment and thus whose field specifications are incompletely specified and must be supplied with actual parameters when used.
(See X.683, 3.4.6)
parameterized object set: An information object set defined using a parameterized object set assignment and thus whose objects are incompletely specified and must be supplied with actual parameters when used.
(See X.683, 3.4.8)
parent type (of a subtype): A type that is being constrained when defining a subtype of a parent type, which may itself be a subtype of some other type.
(See X.680, 3.6.52)
PDU: Protocol Data Unit
(See X.692, 4)
PDV: Presentation Data Value
PER: Packed Encoding Rules of ASN.1
(See X.680, 4)
PER-visible constraint: An instance of use of the ASN.1 constraint notation which affects the PER encoding of a value.
(See X.691, 3.6.22)
presence determinant: A bit-field that determines whether an optional bit-field is present or not.
(See X.692, 3.2.36)
primitive encoding: A data value encoding whose contents octets directly represent the encoded value.
(See X.690, 3.10)
primitive class: An encoding class which is not an encoding structure, and which cannot be de-referenced to some other class
(See X.692, 3.2.37)
primitive field name: The name specified directly in an information object class definition without use of a link field.
(See X.681, 3.4.17)
production: A part of the formal notation used to specify ASN.1.
(See X.680, 3.6.53)
RDN: Relative Distinguished Name
real type: A simple type whose distinguished values are members of the set of real numbers.
(See X.680, 3.6.54)
receiver: An implementation that decodes the octets produced and transferred by a sender.
(See X.690, 3.11)
recursive definitions: A set of ASN.1 definitions which cannot be reordered so that all types used in a construction are defined before the definition of the construction.
(See X.680, 3.6.55)
recursive instantiation (of a parameterized reference name): An instantiation of a reference name, where resolution of the actual parameters requires resolution of the original reference name.
(See X.692, 3.2.38)
Red API: (See CMIS C++)
referenced component: A component of a set type or sequence type identified in a component relation constraint.
(See X.682, 3.4.5)
relative object identifier: A value which identifies an object by its position relative to some known object identifier.
(See X.680, 3.6.56)
relative object identifier type: A simple type whose values are the set of all possible relative object identifiers.
(See X.680, 3.6.57)
relay-safe encoding: A complete encoding of an abstract syntax value which can be decoded (including any embedded encodings) without knowledge of the presentation layer defined context set that formed the environment in which the encoding was performed.
(See X.691, 3.6.23)
replacement structure: A parameterized structure used to replace some or all parts of a construction before encoding the construction.
(See X.692, 3.2.40)
restricted character string type: A character string type whose values are zero or more characters taken from a fixed collection of characters. The collection is a repertoire identified in a type specification. The restricted character string types are GeneralString, GraphicString, IA5String, ISO646String, NumericString, PrintableString, TeletexString, T61String, UniversalString, and VisibleString.
(See X.680, 3.6.58)
RGB API: (See TMN C++)
ROA: Recognized Operating Agency
(See X.680, 4)
ROSE: Remote Operations Service Element
RTTI: Run Time Type Identification
self-delimiting encoding: An encoding for a set of abstract values such that there is no abstract value that has an encoding that is an initial sub-string of the encoding of any other abstract value in the set.
(See X.692, 3.2.41)
selected rows: Those rows of a constraining table which contain, in the appropriate columns, the values of all of the referenced components.
(See X.682, 3.4.7)
selection types: Types defined by reference to a component type of a choice type, and whose values are precisely the values of that component type.
(See X.680, 3.6.59)
semi-constrained whole number: A whole number which is constrained by PER-visible constraints to exceed or equal some value "lb" with the value "lb" as a permitted value, and which is not a constrained whole number.
(See X.691, 3.6.24)
sender: An implementation that produces octets for transfer by encoding some data value.
(See X.690, 3.12)
sequence types: Types defined by referencing an ordered list of types (some of which may be declared to be optional); each value of the sequence type is an ordered list of values, one from each component type.
(See X.680, 3.6.60)
sequence-of types: Types defined by referencing a single component type; each value in the sequence-of type is an ordered list of zero or more values of the component type.
(See X.680, 3.6.61)
serial application (of constraints): The application of a constraint to a parent type which is already constrained.
(See X.680, 3.6.62)
set arithmetic: The formation of new sets of values or information objects using the operations of union, intersection and set difference (use of EXCEPT).
(See X.680, 3.6.63)
set types: Types defined by referencing a fixed, unordered, list of distinct types (some of which may be declared to be optional); each value in the set type is an unordered list of values, one from each of the component types.
(See X.680, 3.6.64)
set-of types: Types defined by referencing a single component type; each value in the set-of type is an unordered list of zero, one or more values of the component type.
(See X.680, 3.6.65)
simple reference name: A reference to an encoding class, object, or object set that includes neither the name of the EDM module in which that encoding class, object, or object set was defined, nor (in the case of an implicitly generated encoding class) the name of the ASN.1 module in which it was generated.
(See X.692, 3.2.42)
simple type: Any type that is not a composite type.
(See X.691, 3.6.25)
size range condition: A condition on the existence of effective size constraints on a string or repetition field (and whether the constraint includes zero, and/or allows multiple sizes) which, if satisfied, means that specified encoding rules are to be applied.
(See X.692, 3.2.43)
SMASE FU: System Management Application Service Element Functional Unit
SMF: System Management Functions
SMK: Shared Management Knowledge
(See Knowledge Management Function)
SMO: Systems Management Overview
(See X.701)
source governor (or source class): The governor that determines the notation for specifying abstract values associated with a source class when mapping them to a target class.
(See X.692, 3.2.44)
spacing character: A character in a character repertoire which is intended for inclusion with graphic characters in the printing of a character string but which is represented in the physical rendition by empty space; it is not normally considered to be a control character.
(See X.680, 3.6.67)
Specific API: The Specific API provides access to a closed set of managed object classes that are selected at compile time.
start pointer: An auxiliary field indicating the presence or absence of an optional bit-field, and in the case of presence, containing the offset from the current position to the bit-field.
(See X.692, 3.2.45)
static conformance: A statement of the requirement for support by an implementation of a valid set of features from among those defined by the ASN.1 standard.
(See X.690, 3.13)
subtype (of a parent type): A type whose values are a subset (or the complete set) of the values of some parent type.
(See X.680, 3.6.68)
T.120: Transmission Protocols For Multimedia Data
T.121: Generic Application Template
T.122: Multipoint Communication Service for Audiographics Conferencing
T.123: Protocol Stacks for Audiographic Teleconferencing
T.124: Generic Conference Control
T.125: Multipoint Communication Service Protocol Specification
T.126: Multipoint Still Image and Annotation Protocol
T.127: Multipoint Binary File Transfer
T.128: Audio Visual Control for Multipoint Multimedia Systems
table constraint: A constraint applied to an object class field type which demands that its values conform to the contents of the appropriate column of some table.
(See X.682, 3.4.8)
tag: A type denotation which is associated with every ASN.1 type.
(See X.680, 3.6.69)
tagged types: A type defined by referencing a single existing type and a tag; the new type is isomorphic to the existing type, but is distinct from it.
(See X.680, 3.6.70)
target governor (or target class): The governor that determines the notation for specifying abstract values associated with a target class when mapping to them from a source class.
(See X.692, 3.2.46)
tagging: Replacing the existing (possibly the default) tag of a type by a specified tag.
(See X.680, 3.6.71)
textually dependent: A term used to identify the case where if some reference name is used in evaluating an element set, the value of the element set is considered to be dependent on that reference name, regardless of whether the actual set arithmetic being performed is such that the final value of the element set is independent of the actual element set value assigned to the reference name.
(See X.691, 3.6.26)
TMN: Telecommunications Management Network
TMN C++ API: A set of APIs (CMIS C++, GDMO C++, ASN.1 C++) that supports access CMIS, managed object and abstract data types respectively.
top-level type(s): Those ASN.1 type(s) in an application that are used by the application in ways other than to define the components of other ASN.1 types.
(See X.692, 3.2.47)
trailing zero bit: The zero bit found in the last position of a bitstring value, even when the bitstring consists of only a single bit.
(See X.690, 3.14)
transfer syntax: The abstract syntax and concrete syntax used in the transfer of data between open systems.
Note that the term "transfer syntax" is sometimes used to mean encoding rules, and sometimes used to mean the representation of bits in data while in transit.
(See X.680 3.6.72)
transforms: Encoding objects of the class #TRANSFORM which specify that the encoding of the abstract values associated with some class is to be the encoding of different abstract values associated with the same or a different class (or of transform composites).
(See X.692, 3.2.48)
transform composites: An ordered list of elements that can itself be the source or the result of transforms.
(See X.692, 3.2.49)
true: One of the distinguished values "true" or "false" of the Boolean type.
(See X.680, 3.6.73)
TSAPI: Telephony Services Applications Programming Interface allows client applications use of a common, host-based set of telephony services.
Twos-complement-binary-integer encoding: The encoding of a whole number into an octet-aligned-bit-field of a specified length, or into the minimum number of octets that will accommodate that whole number encoded as a 2's-complement-integer, which provides representations for whole numbers that are equal to, greater than, or less than zero, as specified in clause 10.4.
(See X.691, 3.8.1)
type: A named set of values.
(See X.680, 3.6.74)
type field: A field which contains an arbitrary type.
(See X.681, 3.4.20)
type reference name: A name associated uniquely with a type within some context.
(See X.680, 3.6.75)
typesharing: The ability of the ASN.1 compiler to generate in the header file a structure that is used to define multiple types by taking advantage of shared similarities. By default, typesharing is enabled. To disable typesharing, specify the -compat noSharedTypes option.
UCS: Universal Multiple-Octet Coded Character Set
(See X.680, 4)
ULA: Upper Layer Architecture
(See X.691, 4)
unconstrained whole number: The value of an integer type not constrained by PER-visible constraints.
(See X.691, 3.8.27)
Unicode: The values expressed as two-octet codes by the ASN.1 BMPString type. Unicode, maintained by the Unicode Consortium, is a system for the coding of 16-bit characters. Most of the worlds written languages can be interchanged, processed and displayed using BMPString.
unconstrained whole number : A whole number which is not constrained by PER-visible constraints.
(See X.691, 3.6.27)
unrestricted character string type: A type whose abstract values are values from a character abstract syntax, together with an identification of the character abstract syntax and of the character transfer syntax to be used in its encoding.
(See X.680, 3.6.76)
user (of ASN.1): The individual or organization that defines the abstract syntax of a particular piece of information using ASN.1.
(See X.680, 3.6.77)
user-defined constraint: A constraint which requires a more complicated statement than can be accommodated by the other forms of constraint, and which must therefore involve specification by some means outside of ASN.1.
(See X.682, 3.4.9)
UTC: Coordinated Universal Time
(See X.680, 4)
UTF-8: UCS Transformation Format, 8-bit form.
(See X.693, 4)
valid XML document (for an ASN.1 schema): An XML document which is well-formed (see W3C XML 1.0) and whose content conforms to the XER specification for the encoding of the ASN.1 type specified by an ASN.1 schema.
(See X.693, 3.2.3)
value: A distinguished member of a set of values.
value field: A fixed-type or of variable-type field which contains a value.
(See X.681, 3.4.21)
value encoding: The way in which an encoding space is used to represent an abstract value.
(See X.692, 3.2.50)
value mapping: A 1-1 relationship between values in two types that enables a reference to one of those values to be used as a reference to the other value. This can, for example, be used in specifying subtypes and default values.
(See X.680, 3.6.78)
value reference name: A name associated uniquely with a value within some context.
(See X.680, 3.6.79)
value set: A collection of values of a type. Semantically equivalent to a subtype.
(See X.680, 3.6.80)
value set field: A fixed-type or of variable-type field which contains a non-empty set of values of some type.
(See X.681, 3.4.22)
variable constraint: A constraint employed in specifying a parameterized abstract syntax, and which depends on some parameter of the abstract syntax.
(See X.683, 3.4.9)
version brackets: A pair of adjacent left and right brackets ("[[" or "]]") used to delineate the start and end of an extension addition group. The pair of left brackets can optionally be followed by a number giving a version number for the extension addition group.
(See X.680, 3.6.81)
version number: A number which can be associated with a version bracket
(See X.680, 3.6.82)
white-space: Any formatting action that yields a space on a printed page, such as the SPACE or TAB character, or multiple uses of such characters.
(See X.680, 3.6.83)
X.200: ITU-T Recommendation X.200 (1994) | ISO/IEC 7498-1:1994, Information Technology - Open Systems Interconnection- Basic Reference Model: The basic model
X.207: ITU-T Recommendation X.207, Open Systems Interconnection- Application Layer Structure
X.208: CCITT Recommendation X.208, Open Systems Interconnection- Specification of Abstract Syntax Notation One (ASN.1) (no longer the ASN.1 standard)
X.209: CCITT Recommendation X.209, Open Systems Interconnection- Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1) (no longer the BER standard)
X.215: ITU-T Recommendation X.215, Open Systems Interconnection- Session Service Definition
X.216: ITU-T Recommendation X.216, Open Systems Interconnection- Presentation Service Definition
X.217: ITU-T Recommendation X.217, Open Systems Interconnection- Service Definition for the Association Control Service Element
X.226: ITU-T Recommendation X.226, Open Systems Interconnection- Connection-oriented presentation protocol: Protocol specification
X.680: ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002, Information Technology - Abstract Syntax Notation One (ASN.1): Specification of Basic Notation
X.681: ITU-T Recommendation X.681 (2002) | ISO/IEC 8824-2:2002, Information Technology - Abstract Syntax Notation One (ASN.1): Information Object Specification
X.682: ITU-T Recommendation X.682 (2002) | ISO/IEC 8824-3:2002, Information Technology - Abstract Syntax Notation One (ASN.1): Constraint Specification
X.683: ITU-T Recommendation X.683 (2002) | ISO/IEC 8824-4:2002, Information Technology - Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 Specifications
X.690: ITU-T Recommendation X.690 (2002) | ISO/IEC 8825-1:2002, Information Technology - ASN.1 Encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)
X.691: ITU-T Recommendation X.691 (2002) | ISO/IEC 8825-2:2002, Information Technology - ASN.1 Encoding Rules: Specification of Packed Encoding Rules (PER)
X.700: ITU-T Recommendation X.700 | ISO/IEC 7498-4 Information Technology - Management Framework for OSI.
X.701: ITU-T Recommendation X.701 | ISO/IEC 7498-4 Information Technology - Systems Management Overview (SMO)
XER: XML Encoding Rules
(See X.693, 4)
XML: Extensible Markup Language
(See X.680, 4)
XML document: A sequence of characters which conforms to W3C XML 1.0 definition of document.
(See X.693, 3.2.4)
We stand with Ukraine