anchor.diff:  <template class="object-editor"
             combination="around">
      <container id="object-name"/>
  -   <sub-template/>
  +   <next-template/>
      <container id="accept-action"/>
      <container id="cancel-action"/>
   </template>
   
  -Besides, it also makes sense to use <sub-template/> outside and :around template-combination. It is the equivalent of call-next-method
  +Besides, it also makes sense to use <next-template/> outside and :around template-combination. It is the equivalent of call-next-method
   
   The following model (imagine the corresponding components...):
   (defclass person ()
  
positive.code: </template>
  
  <template class="employee-viewer">
     <sub-template/>
     <container id="company"/>
  </template>
  
  
  Last, but not least, we should make the template system extensible. On the one hand, it should be possible to implement
  new template-combinations. On the other hand, the template system should be extensible by means of options too. So, for example, we should be able to implement layered templates extending the options engine:
  
  <template class="person-viewer"
  
negative.code: <template class="<component-class>"
            combination="<template-combination>">
     ...
     <next-template/>
  </template>
  
  Examples:
  
  We may want to have :above (equivalent to :before), :below (equivalent to :after) and :around. Besides, we can embed other templates (in the case of subclassing or :around method combinations, for example) using the special XML element <next-template/>
  
  <template class="object-editor"
            combination="above">
  