General encoding

DiME, the open and trust-based data format building secure Application-based Public-Key Infrastructures (APKIs) in a breeze.

DiME items are generally encoded using Base64 and following this structure:

General DiME item structure and encoding

Here the dots (‘.’) are used to separate each part of the DiME item. The position of each component is important:

• First component: the item header

• Second component: Base64 encoded JSON with item claims

• Last component: item signature package

It is possible to include any number of components, separated by additional dots (‘.’), between the second component and the last component. This is the case for several DiME items:

• Identity – include a trust chain as an additional component

• Message/data – include a Base64 encoded application-specific payload as an additional component

A DiME envelope follows a similar pattern, but uses colon (‘:’) to separate items and components:

Envelope structure and encoding

The standard Base64 encoding is used, not URL safe.