Structured

Structured parameters are defined in the XML configuration by using the SParam element. No attributes (except for the ID) are required for structured parameter definitions. They may also optionally contain nested parameters.

However, structured parameters generally require a code mapping configuration to be associated with the design space. String parameters are the only exception.

Strings

Strings are structured parameters that use the built-in 'String' type. This makes them a special case, because structured parameters normally do not use the type attribute, except when specifying array dimensions.

When the parameter is initialized, the value is taken from the ID attribute.

Examples

    <SParam id='Hello World' type='String' />

Fixed Values

Fixed values are only applicable to choices. That is, they only make sense when the structured parameter contains nested SChoice elements.

Suggestions for Future Versions

Because the ID attribute should be limited to certain strings, using the ID to initialize the parameter imposes a limit on the possible parameter values. The value could perhaps be specified in the fixed attribute.

This example shows a parameter definition that should arguably be illegal in future versions; the string, and therefore the parameter ID, starts with a numeral.

    <SParam id='99 bottles of beer on the wall' type='String' />

Relevant Tests

• Structured-Parameter Tests
• Value Consistency Tests
• Structured-Parameter Initialization Tests
• Accessor Tests