anchor.diff:  That is to say; implementations must follow the spirit (in addition to the letter) of the implementation. Any dichotomy thus introduced
   is to be resolved by discussion amongst the authors.
   
  -An HTTP 401 will be returned to all clients not sending an appropriate 'Authorization: jwt' header, unless
  +An HTTP 401 will be returned to all clients not sending an appropriate 'Authorization: token' header, unless
   the request is directed to /session under the POST method.
   
  -'Authorization: jwt' headers should be sent as follows:
  -
  -'Authorization: jwt token=[jwt-token]', where [jwt-token] is that returned from the /session endpoint.
  +'Authorization: token' headers should be sent as follows:
  +
  +'Authorization: token [token]', where [token] is that returned from the /session endpoint.
   
   Various financial documents have "status" fields (e.g. POs, claims). They have the following possibilities:
   
  
positive.code:         
  + Response 201 (application/json)
  
          [JWT Response][]
  
  ### Renew session [POST]
  
  
negative.code: # Group Sessions
  Resource for creating and destroying sessions.
  
  ## Token Response
  
          { "token": "xxxxxxxxxxxx", "expires": "2014-01-02T15:33:23" }
  
  ## Session [/session]
  ### Get details of your session [GET]
  