anchor.diff:    it. I went for the latter, which I think is the right choice, but did not
     have the time to make the API consistent throughout.
   
  -- Much work needs to be done on the GUI. It is currently very elementary. The
  -  Angular2 code contained herein is my first experience with it and being a
  -  prototype with a small time budget, I did not:
  -  - spend much time being idiomatically consistent,
  -  - leveraging existing elements of Angular2 (like
  -    link:https://angular.io/docs/ts/latest/guide/reactive-forms.html[reactive forms]),
  -  - ... writing tests.
  -
   - Consider whether a framework like http://redux.js.org/[Redux] would be useful.
   
   - Perhaps get rid of ng\_select. I started with this before realising how easy
  
positive.code:   ng\_select may be handling large lists and one may want to do some testing
    before removing it.
  
  - Move the logic of merging an instance with its metadata (currently handled in
    sifra.structural.\_merge\_data\_and\_metadata) to the javascript. The document
    produced by that method is heavy due to its repetativeness and would hence be
    slow to pass around over the net. The logic is straight forward and would be
    easy to implment in javascript given the 'metadata' and instance.
  
  ## Required packages
  
  http://graphviz.org/download/[Graphviz]
  
negative.code: 
  ### Building the run environment using Docker
  
  Docker configuration is now the preferred way to deploy and develop the application.
  
  
  ### Testing
  
  