anchor.diff:  
   The sentence annotation do not include offsets and mainly presented as additional information. Re-importing the WebAnno TSV file construct sentences from the token annotations.
   
  +If a sentence spans multiple lines, the text is split at the line feed characters (ASCII 12) and multiple `#Text=` lines are generated. Note that carriage return characters (ASCII 13) are kept
  +as escaped characters (`\r`). 
  +
  +.Example: Original multi-line text
  +[source,text]
  +----
  +#Text=Bell , based in Los Angeles , makes and distributes
  +#Text=electronic , computer and building products .
  +----
  +
   ==== Token and Sub-token Annotations
   
  +Tokens represent a span of text within a sentence. Tokens cannot overlap, although then can be
  +directly adjacent (i.e. without any whitespace between them). The start offset of the first
  +character of the first token corresponds to the start of offset of the sentence.
  +
   Token annotation starts with a `sentence-token` number marker followed by the begin-end offsets and the token itself, separated by a TAB characters. 
   
   .Example: Token position
  
positive.code: 1-5	23-24	.	.	_	_
  ----
  
  In this example (say token `1-1`), column 4 (`NNP`) is a value for the feature `PosValue` of the *de.tudarmstadt.ukp.dkpro.core.api.lexmorph.type.pos.POS* layer. Column 5 (`SUBJ`) records the value for the feature *DependencyType* of the *de.tudarmstadt.ukp.dkpro.core.api.syntax.type.dependency.Dependency* relation layer, where as column 6 (`1-3`) shows from which governor (`VBD`) the dependency arc is drawn.
negative.code: 1-3.2	13-14	s
  ----
  
  Here, the sub-token `play` is indicated by sentence-token number `1-3.1` and the sub-token `s` is indicated by `1-3.2`.
  
  While tokens may not overlap, sub-tokens may overlap.
  
  .Example: Overlapping sub-tokens
  [source,text]
  ----
  1-3 9-14  plays
  1-3.1 9-12  pla
  1-3.2 11-14 ays
  ----
  
  ==== Span Annotations
  
  