CURVE supported : implies CURVE_DESCRIPTION in supported parameters ?

[ericthegeek]

It is possible to support DMX_PERSONALITY without also supporting DMX_PERSONALITY_DESCRIPTION. This would be a poor design choice, and would require the user to lookup what each personality means in external documentation, but it is allowed by the the standard.

The reverse is also true, you can support DMX_PERSONALITY_DESCRIPTION without supporting DMX_PERSONALITY. This might be desirable it a responder that has only one personality and wants to give that personality a name (i.e. "Standard Mode").

I'd discourage implementers from using either of these corner cases (If you support one PID, you really should support the other), but those implementing controllers should consider this possibility.