anchor.diff:  Tags are one of main structural building blocks. Tags can be hierarchically structured. The root tag of this hierarchy is always bound to a specific project. Tags can also be tagged by other tags. The hierarchically structure is mainly used to organise tags.   
   
   Tags can have i18n properties which are specified by the schema.
  -
  - * TagVerticle
  +Tags can be manipulated using the  TagVerticle class.
   
   === Startpage handling
   
  
positive.code: == Contents
  
  Contents are similar to tags with one major exception. Contents can not be nested. This means a content does not have a parent child relationship to another content. Only tags have this kind of relationship. A content can only have one parent tag. Contents can be tagged by any number of tags.
  
   * ContentVerticle
  
  === Object Relationships
  
  
negative.code: 
  Following a link to a page that does not exist in the current language leads to a mediator page. The mediator page informs the user that the content is not available in the current language, but available in english, german etc.
  
  Links CAN include the target language.
  
  == Paging
  
  * /tags
  * /contents
  
  Tags have tags and children. Both can be filtered and paged individually within the tag or content response.
  
  == Schemas 
  
  