It would be very useful to let a view override the
default required/not required status of an individual
For example a site member object might have different
levels of information required for different levels of
access. A conditional view could make password a
required field for a full site member as opposed to a
This is probably next-release-level stuff, but I wanted
to get the thought as it occurred to me.