In the previous post we defined a number as a sequence of base-64 digits. In this post I will name the numeric policy indicators and illustrate the use of the dimension policy with raw, eight-bit byte arrays.

The policy indicator marks the start of a field of data. Since the start of the successor field marks the end of the current field, policy indicators are also field separators. More importantly policy indicators dictate the form into which the data will morph when decoded. Following are the numeric policy indicators (ASCII special characters) ordered by their septet values.

- NumericPolicyIndicator:
`64 #`

IEEE-754 real number policy

`65 ^`

Angle policy

`66 :`

Date and Timestamp policy

`67 ~`

Logical set (bit-vector) policy

`68 ?`

Boolean policy

`69 -`

Twos-complement sign-extended integral value policy

`70 +`

Unsigned integral value policy

`71 @`

Indexed element policy

`72 *`

Array dimension policy

A numeric field can have a plurality of numeric elements provided each element has the same policy. In that event the prefix for subsequent elements is septet 75, the intra-field separator, comma.

- NumericField:
- NumericPolicyIndicator Number
_{opt}

NumericField , Number_{opt}

For example, consider a two-dimensional array with dimensions 63×15.

Septet 74 *space* is called the raw data separator because it terminates the inner most dimension and marks the transition to an eight-bit raw data policy. Thus, the first 15-byte array begins

`*z,F`

15 bytes

The eight-bit raw data policy is limited to the 15 bytes needed to populate the 15 byte array. Once populated, the decoder reverts to the seven-bit dimension policy and expects the second of 63 arrays. Since the array lengths of the 63 arrays may change, the length of subsequent byte arrays must be specified.

The default length is 15 bytes. We can accept the default value by omitting the length (i.e. the number between the comma and the space) as in the following example

`,`

15 bytes

or override the default value with a new value (e.g. 11 bytes)

`,B`

11 bytes

An omission does not always signal the use of a default value. It can also mean that the data are unknown. For example, to specify an unknown number of arrays the first of which is 15 bytes long we omit the number between the * and the ,

`*,F`

15 bytes

Alternatively, the policy indicator can be a placeholder for the field’s data and the fact that the number is omitted may throw an exception that prevents validation.

In my next post, we will look at how CBF-8 differentiates text from numbers.

prev continue