1 Overview

The Concise Data Identifer (CDI) standard provides a common means to declare data formats in binary files and in memory. The identifiers are 32 bit words which allows for quick and easy comparison at run time. Values for widely used formats are defined and can be used together with private, application specific values.

The standard also defines a few data types and a couple of container formats.

2 Identifer Value

A Concise Data Identifier is a 4 byte, big endian value containing 3 fields. The fields are the CDI Fingerprint, the data type Category, and a format Selector within the category. The Category and Selector together declare a Format.

The official list of assigned public indentifiers is the cdi.h header.

2.1 Category

The assigned categories are as follows:

The State category is for application images, saved game data, or other binary cache data.

The Private category is for experimental or application specific data.

2.2 Selector

The 12 bit selector allows 4032 universal formats to be defined within each category.

The selector range 0xFC0-0xFFF is reserved for 64 application specific data types within each category.

3 CDI Package Format

This file container format defines a series of data chunks followed by a table of contents (TOC). It is similar to the WAD format used in the Doom games.

The CDI value for a CDI Package is DA7A7000.

All offest and length fields are 32 bit, little endian values. All offset values are in bytes from the start of the file. All length values are in bytes.

3.1 Package Header

The header App_ID field denotes the types of private CDI values used within the package. If this field is zero then no private CDI values may be present in the package.

3.2 Package TOC Entry

The table of contents contains an array of CDIEntry and/or CDIEntryPath structures. If the first two bytes of an entry are DA7A then it is a CDIEntry, otherwise it will have the path fields.

The TOC entry App_ID field is a unique, application defined identifer for the chunk.

The Path1, Path2, & FileSI fields are little endian indices into a Text String Table chunk with an App_ID of “PATH” (50415448). A Path1 or Path2 value of zero indicates the respective path node is not used.

4 CDI Chunk Format

This file container format defines a series of data chunks.

The CDI value for the CDI Chunk format is DA7A7001.

All length fields are 32 bit, little endian values.

4.1 Series Header

The header App_ID field denotes the types of private CDI values used within all following chunks. If this field is zero then no private CDI values may be present in any chunks.

The Length field is the total number of bytes of all following chunks, excluding any terminator chunk.

4.2 Chunk Header

4.3 Terminator

5 Text String Table Format

This format defines a block of UTF-8, NUL terminated strings. It can be used for symbol tables.

The CDI value for the String Table format is DA7A0006.

There are three defined forms that string tables may take. All forms start with the same 32 bit header.

The index is an array of unsigned 16 or 32 bit, little endian values of the byte offsets into the strings section.

Here is the binary data for a form 1 table with three strings of “Gems”, “Hard Stop”, & “facet”:

00000000: 0100 0003 0000 0500 0f00 4765 6d73 0048  ..........Gems.H
00000010: 6172 6420 5374 6f70 0066 6163 6574 00    ard Stop.facet.

6 Image RGBA8 Format

This format defines a series of 8 bit color values with alpha. It can be used for storing image CLUTs.

The CDI value for the RGBA format is DA7A100F.

The number of color entries present is specified elsewhere, such as in a Chunk Header.