Comments by Brian Risley (Top 2 by date)

Our plan is to support the security to a certain extent in the xaml, as we have varying site security needs. We will have standard Xaml, but will have an option to load the Xaml from the database if an override is present. If a site wants to specifically control fields that appear in the Xaml, they will be able to do so. They may also add their own security flags which our logic will not have to know about. Certain tasks and some data may be restricted in the viewmodel by similar flags. Some of these controls aren't just for security information, we have customers who don't use some of our properties and don't want to see them. This way they can set a flag at the highest level in the Xaml override, and not see them or they can even redo the Xaml and remove them. We have no Single customer to design our views for, we have certain ideas and patterns, but the individual customer has the ability to control the fields. With this approach, we don't have to build the Xaml from scratch, just modify an existing template/base style. Our code won't be changed because one customer has to have field x removed or moved on a view.
Brian