1. Coaches can contain multiple Coach Views. Coach Views are reusable collection of user interfaces and can be bound to a data TYPE. They can be shared between the Coaches. But in Heritage Coaches, all UI elements need to be recreated.

2. Coaches have web 2.0 appearance and behavior and have client side data model i.e. data can be refreshed without the full page refresh. They use Dojo 1.7.3.

3. Instead of the one-button mechanism of Heritage Coaches, Coach Views use named boundary events. PROGRAMMERS use boundary events for actions such as data updates with the server and transitions to other Coaches or services

4. Coaches support COLLABORATION while Heritage Coaches do not. More than one person can work on the same Coach instance at the same time in their own browsers

5. The control ID of a view-based Coach is different from the control ID of a Heritage Coach. The control ID of a Heritage Coach is the div node ID. This is not the case in view-based Coaches because Coach Views are reusable and you can have multiple views in a Coach.

In view-based Coaches, the control ID is the value of the data-viewid attribute of a <div></div> tag. By using the data-viewid attribute, View developers can locate the nested View because data-viewid is UNIQUE within its parent or enclosing view.

Coach cannot contain Heritage Coach elements and Heritage Coaches cannot contain Coach Views. That is, a user interface must be a Coach or Heritage Coach and not a MIX of the two.

1. Coaches can contain multiple Coach Views. Coach Views are reusable collection of user interfaces and can be bound to a data type. They can be shared between the Coaches. But in Heritage Coaches, all UI elements need to be recreated.

2. Coaches have web 2.0 appearance and behavior and have client side data model i.e. data can be refreshed without the full page refresh. They use Dojo 1.7.3.

3. Instead of the one-button mechanism of Heritage Coaches, Coach Views use named boundary events. Programmers use boundary events for actions such as data updates with the server and transitions to other Coaches or services

4. Coaches support collaboration while Heritage Coaches do not. More than one person can work on the same Coach instance at the same time in their own browsers

5. The control ID of a view-based Coach is different from the control ID of a Heritage Coach. The control ID of a Heritage Coach is the div node ID. This is not the case in view-based Coaches because Coach Views are reusable and you can have multiple views in a Coach.

In view-based Coaches, the control ID is the value of the data-viewid attribute of a <div></div> tag. By using the data-viewid attribute, View developers can locate the nested View because data-viewid is unique within its parent or enclosing view.

Coach cannot contain Heritage Coach elements and Heritage Coaches cannot contain Coach Views. That is, a user interface must be a Coach or Heritage Coach and not a mix of the two.