The Template class is where your Framework's Generalized and Domain Specific knowledge will reside. Many Templates can reside here, with the same or different Interfaces. Effectively this is where the design takes place. However, a class must be open or exposed as a Template, to be extended from the MetaData.

It is hard to come up with terms, because nearly all already have some sort of baggage. This can also be called a HotSpot.

This is where further definition is required for the first layer of framework, after which it becomes too Domain specific to be standardized. The definition of a Framework must include this generalized layer, and perhaps even an aspect of the Specialized.

A Template can be implemented as a whitebox, either with TemplateMethod, Strategy (GoF), on base classes or by blackbox through composition/association, via Visitor or Decorator (GoF). A Template in this formula means whitebox, blackbox or indeed any greybox implementation.

Framework Template Types

The Structure and the Infrastructure Templates, can also be known as horizontal or vertical templates, are both a 'definition' or in current software terms 'interfaces' for the Framework, with the structure being the domain its written for and the horizontal being the cross domain infrastructure to hold it.