anchor.diff:  
   Using the enumeration `org.roklib.urifragmentrouting.parameter.ParameterMode` you can specify in what mode the URI action mapper tree shall operate.
   
  -Let's clarify these modes.
  +Let's describe these modes.
   
   ==== Directory Mode With Names
   
   In this mode, parameter values are contained in a URI fragment in a directory-like format. Their parameter ids are also contained in the URI fragment. Example:
   
  -    /admin/users/id/4711/showHistory/startDate/2017-01-01/endDate/2017-01-31
  +    #!/admin/users/id/4711/showHistory/startDate/2017-01-01/endDate/2017-01-31
   
   This URI fragment contains three parameters: `id`, `startDate` and `endDate`. As you can see, the parameters' ids are contained in the the URI fragment together with their concrete values.
   
  
positive.code: 
  == Advanced Action Mapper Types
  
  == Assembling a URI Action Mapper Tree by Hand
negative.code: 
  is disassembled into the following list of tokens:
  
      ["admin", "users", "id", "4711", "profile", "activeTabsheet", "address"]
  
  This list is then interpreted by the mapper tree. Parts of this list are parameter values (here ["id", "4711"] and ["activeTabsheet", "address]). The other parts make up the directory-like hierarchical URI fragment structure (here ["admin", "users", "profile"]). For each of the directory parts (_path segments_), there is one instance of a `UriPathSegmentActionMapper` which is responsible of handling this part. These _action mappers_ have different tasks. The task of the inner segments is to pass the interpretation process on to the action mapper of the next hierarchy level. For instance, the action mapper responsible for the `admin` path segment is responsible to pass the interpretation process on to the action mapper for the `users` path segment.
  
  