A global description of parameter contents (<sw-param-contents>) can be made in <msrsw> (compare 2.1.4. Parameter contents storage). Parameter contents can be allocated to a function by <sw-function-ref>. A classification of parameter contents is possible by <sw-param-contents-class>, e.g.: "Test data", "Raw application data". Parameter contents can be given several times over. This is meaningful if for instance, many sets of test data shall be given for a parameter.
The content itself is allocated to a parameter by <sw-param-ref>. Parameter structure (in <sw-param>) and parameter content (in <sw-param-contents>) must agree in structure (that is to say, these carry the same <sw-param-class> for example).
The parameter contents are broken down into as many as three axes (<sw-param-content-x>, <sw-param-content-y>, <sw-param-content-v> and <sw-param-content-text>) in order to fill the structures in 2.2.3.4. Parameter structures with data. In the case of maps, all values are stored in <sw-param-content-v> on a line-by-line basis, whereby the index for the X-Achse is faster.
The data can be specified in differing formats for each axis:

<sw-param-values-phys>
Physical values, given as floating-point numbers as required
<sw-param-values-coded>
Control-unit-internal values, given as integers or a floating-point numbers
<sw-param-values-coded-hex>
Control-unit-internal values, given as hexadecimal numbers in "C" format (e.g. "0x7f2a")
<sw-param-values-adr>
Address for the value in the control unit given as hexadecimal number in "C" format (e.g. "0x7f2a"). This address primarily serves documentation purposes (e.g. instructions for re-programming).
<sw-param-values-generic>
Additional formats can be stored here. The formats themselves are defined by the attribute [type].

The parameter contents are designed such that these can also be used even without the data dictionary so as to be able to perform physical archiving for example. The elements <sw-param-ref>, <sw-param-class>, <sw-unit> are therefore available again as options. Any possible redundancy is thereby accepted since these elements are generated automatically. The reference <sw-param-ref> can no longer be made by means of ID/IDREF because the entity can only include parameter contents and not the parameter definitions. Thus only the natural addressing remains.
Figure 19: Parameter contents (overview)
Figure 20: Parameter contents (details)
The following examples illustrate the parameters content of a characteristic values and for a characteristic:
<sw-param-content> <sw-param-ref>KUP_FEN</sw-param-ref> <sw-param-class>value</sw-param-class> <sw-param-content-v> <sw-unit-ref>grad C</sw-unit-ref> <sw-param-values-coded> <v>1</v> </sw-param-values-coded> </sw-param-content-v> </sw-param-content>
<sw-param-content> <sw-param-ref>FAGRM</sw-param-ref> <sw-param-class>curve_individual</sw-param-class> <sw-param-content-x> <sw-unit-ref>grad C</sw-unit-ref> <sw-param-values-coded> <v>1</v><v>2</v><v>3</v><v>4</v><v>5</v><v>6</v> </sw-param-values-coded> </sw-param-content-x> <sw-param-content-v> <sw-param-values-coded> <v>1</v><v>2</v><v>3</v><v>4</v><v>5</v><v>6</v> </sw-param-values-coded> </sw-param-content-v> </sw-param-content>