CAS attribute naming

[Rod Widdowson]

> we need to come up with a separate and easier-to-configure strategy for that. 

This ties in with the whole "want to source 'attributes on the wire directly' from DataConnectors" issue.

Every time I go there I come up dry of ideas on how to do this.  Options include (and they are not mutually exclusive)

- Entirely exbedding encoding from the attribute definition (and thus collapsing the somewhat weird distinction between "attributes
from a dataconnector" and "attributes from a definition" - although that then gets into some very subtle dependency issues.

- Having some sort of "per protocol (or profile?)" encoder with some automagical mechanism to generate the name.  You could consider
CAS to be a degenerate case of that.  I falter at the "automagic" bit though.  Velocity? 

There are a lot of deployers out there.  How would you want to see this addressed?

/Rod