[Cmb-users] Dealing with passwords in attributes

[David Thompson]

> But in that case the roles will be different for each data item - assuming that the roles are enumerations and not just strings.  I’m wondering if your use case would be better served by creating a new item - “geometric coordinate" that could have additional meta data (is it spatial or parametric, etc..).

I am fine with strings instead of enums as long as the strings are documented. :-)

It does seem like we need to be careful to keep the UI out of the data. Passwords really are not UI-specific; the UI and I/O layers might build behavior for dealing with items in that role but most/all of that logic should not be part of the attribute itself. If none of the logic needs to go with the attribute, then I vote for avoiding a new class.

	David