Mr. Verreault touched on one of these.
Increasingly, we want to see codes move to performance outcomes rather than prescriptive outcomes. It doesn't tell you how to do it, but it tells you what you must achieve in terms of safety, environmental features, durability, and that sort of thing. That move in code will open it up for innovation.
Code should not stop you from innovating. It should tell you what you have to achieve when you innovate. It's a big transition, and I think there's a lot of interest in the code process to try doing that.
Everyone involved in the code must realize that we need to carefully balance the costs and the benefits sides of things so that we don't have a process that's always additive. Sometimes you have to make choices about how far to open the door to let through an innovation, yet keep it affordable.