At runtime, this template is requested by the browser using a <script src="…" /> tag.
This template is requested only once and will be cached by the browser.

At runtime, requests for raw JSON data are made which constitute the data to be bound to the template.

At runtime, any combination of templates may be bound (and re-bound) to this same data without needing to request the template(s) or the data over again.

At runtime, binding occurs by combining a UI template with JSON data to produce JsonML which is then built and inserted into the document.

Model-View-Controller (MVC) Pattern

To make an analogy to a familiar concept, this roughly follows the "Model-View-Controller" (MVP) pattern. The JSON data ("Model") is completely separate from the UI template ("View") until the point at which the webpage ("Controller") combines them. Behavioral events in the UI cause the Controller to affect either the Model or the View (or both) and update the display.

Advantages

The combination of separation of concern and leveraging existing standards produces a number of benefits, such as: