Why is no enum needed? Referencing standard subsystem provided capabilities using class names is contrary to the EAP and WF design standards.

An exception to this would be if some capability is not "standard" e.g. long-term supportable, so we're unwilling to commit an enum value to it. But in that case the value should not be in any of our standard configs and should only be in example configs that come with clear warnings about the status of the value.