202 Mapping Basic Types

Created
13 Sep 2005
Status
Not ApplicableClosed: the issue falls outside the scope of the standard. No further comments are taken. Show the workflow
Part
Part 8-1 (2004)
Links
None
Page
Clause
Paragraph
Category
No impact on this part

Issue

7-3 defines basic types (INT8, INT8U, INT16, STRING32, etc...)
Is that the intention that every type that is followed by an indication of its size is to be encoded with a fixed size in BER,
i.e. INT8 always as one octet, INT16 always as two octets, STRING32 always as 32 octets (how about Unicode ?) ?

Proposal

Specify the mapping between the -7-3 types, the -6 MMS types, the Data types and the ASN.1 encoding.
(see enclosed sheet)

One file is attached to this tissue. Sign in to open it.

DiscussionCreated
Triage Re-entry of non-public comment:

There is no need to add anything NORMATIVE to 8-1. ISO 9506 explicitly defines this in the Data production.

This sets a bad precident since it is well defined in 9506.

Additionally, BER does not encode INT16 into always 2 octets. (it can be three if it is a negative number of a positive value greater than 32,766).

The mappings are already in 8-1 as far as possible. There is no apparent issue.
19 Sep 05