DLC value usage/definition not according to ISO11898

While reading the standards and checking the ixxat interface for fd support, I've seen that the definition of the dlc of the message class in not as in the ISO standard and not as the common unterstanding is.
The length of the data is already encoded in the message data itself, so storing it additionally is reduntant and may lead to errors.
As well the behavior of the classes regarding the data and dlc is somewhat undefinded.
So please agree, that the dlc should be used as in the ISO standard. With the folloeing definitions:
dlc | length of data
0 .. 8 | 0 .. 8
9 | 12
10 | 16
11 | 20
12 | 24
13 | 32
14 | 48
15 | 64

No file, test, or entry point is named. Start by locating the message classes and their DLC and data handling, then compare their behavior with the ISO 11898 table in this issue. Done means the classes consistently use the specified DLC-to-data-length mapping without redundant or conflicting values.

Scritto dal modello di indicizzazione a partire dal testo della issue.