Why are some pages in MIKE2.0 Protected?
As MIKE2.0 is a methodology, there needs to be some stability with the core content that can only be achieved by releasing content in a controlled fashion and by protecting content. At the same time, we wanted to encourage users to offer as much feedback as possible and be able to add Supporting Assets at any point in time. We believe are our current model provides us with this flexibility; the approach is explained in more detail in the Release Methodology.
