I guess not, unless there is a way of aquiring a reference to Model.ContentItem.Article.Zone.Terms using a dynamic query, which might be preferable?
I've a couple of observations to offer, tho':
I've just started using Projections and they offer significant advantages over other containers in as much as they don't require content editors to know/remember which Container they need to add their content to, and as we all know, as far as users
are concerned, more to think about, more to be unhappy about.
The option of using an alternate view in the Query - Display Mode is a very attractive option. Although Properties Mode is pretty darn versatile, it has limitations and my preference would always lean towards using a view to determine
which properties of the Model to render.
Given that the approach I've used caused some unexpected behaviour when invoking @Display(Model.Content), could that be considered a bug, or am I using an 'Unsupported Feature'?