DDEX Standard

Skip to end of metadata
Go to start of metadata

6.6.3.1 Record Delimiter

Each Record is being placed into one line terminated by a line feed (Unicode U+000A) or a carriage return and line feed pair (Unicode U+000D 000A).

6.6.3.2 Primary (Cell) Delimiter

Cells within a Record are separated by tab characters (Unicode U+0009).

6.6.3.3 Secondary  Delimiter

Should a Cell contain two or more data elements, these data elements shall be separated by a pipe character (Unicode U+007C). This is referred to as a Secondary Delimiter.

All data elements in a multi-value Cell shall be of the same primitive data type.

6.6.3.4 Namespace Delimiter

Should a Cell contain a data element whose providence needs to be provided, the data element shall be preceded by a string that provides a "namespace" and two colon characters (Unicode U+003A). The double colon is referred to as a Namespace Delimiter.

Examples include specifically identifiers where, e.g., a party ID can be communicated as  "ISNI::0000000081266409", indicating that the identifier (0000000081266409) is an International Standard Name Identifier (ISNI).

6.6.3.5  Spaces and Delimiters (I)

Delimiters shall not be surrounded by extra space characters. The same principle applies to the Secondary Delimiter.

Example: The writer pair Lennon/McCartney should be communicated as "Lennon|McCartney" and not as "Lennon | McCartney".

6.6.3.6 Spaces and Delimiters (II)

If a Message Sender has received data with extra white spaces, they are encouraged to trim any such extra white space characters when compiling a Sales/Usage Report. They may, however, also use the data with these extra white space characters in such cases. The same principle applies to the Secondary Delimiter.

Example: When the Message Sender received Lennon as “Lennon “ and McCartney as “McCartney “, then the writer pair may be communicated as “Lennon |McCartney “).

  • No labels