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-2	4-8	Haag
  ----
  
  Here `1` indicates the sentence number, `2` indicates the token number (here, the second token in the first sentence) and `4` is the begin offset of the token and `8` is the end offset of the toke while `Haag` is the token.
  
  Sub-token representations are affixed with a `.` and a number starts from 1 to N. 
  
  
negative.code: Here, the first annotation at column 4, `JJ` is avalue for a feature *PosValue* of the layer *de.tudarmstadt.ukp.dkpro.core.api.lexmorph.type.pos.POS*. For the two features of the layer *webanno.custom.Sentiment* (*Category* and *Opinion*), the values `abstract` and `negative` are
  presented at column 5 and 6 resp.
  
  ==== Disambiguation IDs
  
  Within a single line, an annotation can be uniquely identified by its type and stacking index.
  However, across lines, annotation cannot be uniquely identified easily. Also, if the exact type
  of the referenced annotation is not known, an annotation cannot be uniquely identified. For this
  reason, disambiguation IDs are introduced in potentially problematic cases:
  
  * stacked annotations - if multiple annotations of the same type appear in the same line
  * multi-unit annotations - if an annotations spans multiple tokens or sub-tokens
  * un-typed slots - if a slot feature has the type `uima.tcas.Annotation` and may thus refer to
    any kind of target annotation.
  
  The disambiguation ID is attached as a suffix `[N]` to the annotation value. Stacked annotations are separated by `|` character.
  
  .Example: Span layer declaration in file header
  [source,text]
  