Parameter storage (<sw-param-contents>, compare 2.2.5. Specification of parameter contents) can be stored both locally within <sw-function-variant> (2.2.4.1.6. Function-related (local) parameter contents) as well as globally within <msrsw> 2.2.5. Specification of parameter contents.
The following conventions apply for this:
1.
 
The allocation of parameters to functions is exclusively by means of references in the function descriptions (<sw-param-ref> in <sw-function-variant>).
2.
 
It is possible to give <sw-param-content>s in <sw-function-variant>. Only <sw-param>s may be referenced here that are referenced in <sw-function-variant> as well. The provision of parameter contents in functions must therefore be consistent with the assignment of parameters to functions.
3.
 
If a content is specified for a parameter (<sw-param>) both in <sw-function-variant> as well as in <sw-param-content-spec>, then the latter takes precedence.
4.
 
If contents are given in two different functions for the same parameter, then one entry must also be included in <sw-param-content-spec>. This ensures that the straightforward precedence rule given above can be applied.
5.
 
By inserting a <sw-param-contents>, the author of a <sw-function-variant> has the possibility of controlling those parameter contents which shall be displayed locally when formatting.
Differing processes can be operated with the DTD since <sw-param-contents> is possible both for the functions as well as globally for the entire software (within <msrsw>). The following is recommended:
 
Parameter contents are given as programming requirements within <sw-function-variant>. By this, the relation is retained even for fragmentation at the function level.
 
Parameter contents as the result of the application phase are given within <msrsw> as closed and function-overriding. <sw-param-contents> within <msrsw> (compare 2.2.5. Specification of parameter contents) thus assumes an application data status.