anchor.diff:          {"success":true,"response":[{"id":"8","notebook_id":"2","notebook_title":"Second Notebook","title":"Hello World!","content_preview":"Hello World!\n","content":"<p>Hello World!<\/p>\n","created_at":"2014-09-13 17:36:25","updated_at":"2014-09-15 20:09:49","umask":"0"},{"id":"9","notebook_id":"2","notebook_title":"Second Notebook","title":"Here I am!","content_preview":"A new note!\n","content":"<p>A new note!<\/p>\n","created_at":"2014-09-14 20:12:45","updated_at":"2014-09-19 19:05:52","umask":"0"}]}
   
   ### Create a note in a notebook [POST]
  +When creating a note, `title` and `content` are being used to automatically create a new version and link it to that note,
  +meaning that you do not have to create a version yourself. In fact, creating or updating versions isn't even possible.
  +For more info, check out the versions API documentation below.
  +
   + Request (application/json)
   
       + Headers
  
positive.code:     + Body
  
              {"success":true,"response":{"id":"20","previous_id":"19","next_id":null,"title":"Hello World!","content_preview":"Hello World!\n","content":"<p>Hello World!<\/p>\n","created_at":"2014-09-15 20:09:49","updated_at":"2014-09-15 20:09:49","deleted_at":null}}
  
negative.code:             {"success":true,"response":{"id":"11","notebook_id":"1","notebook_title":"First Notebook","title":"New Note","content_preview":"This is a new note!\n","content":"<p>This is a new note!<\/p>\n","created_at":"2014-09-20 19:43:59","updated_at":"2014-09-20 19:45:56","umask":"0","tags":[],"versions":[{"id":"24","previous_id":"23","next_id":null,"latest":true,"timestamp":1411242356},{"id":"23","previous_id":null,"next_id":"24","latest":false,"timestamp":1411242239}]}}
  
  ### Update a note within a notebook [PUT]
  When updating a new note, the `title` and the `content` are being used for creating a new version and linking it to the note.
  As with the POST for creating a new note, when PUTing to update a note, a new version gets created and linked automatically.
  
  Further on, with each update (and by that new version) all attachments linked to the antecessor will be automatically also linked to
  the newly created, latest version. By that, attachments are also being versioned.
  
  #### Example
  
  On a newly created note with an initial version (id #1), three attachments (#1, #2, #3) are being uploaded/attached. Version #1 of that
  note will then have these three versions linked to it. Now the note is being updated and by that a new version (id #2) is being created.
  Now, attachment #1, #2 and #3 are still linked to version #1, but additionaly they also get linked to the newly created version #2.
  
  When a new attachment is now being uploaded, it will _only_ be linked to the latest version of the note (#2). This means, that version #2
  now has four attachments linked to it (#1, #2, #3 and the newly uploaded #4), while version #1 still only has the first three attachments
  linked to it.
  
  This allows browsing through the full history of attachments while browsing through previous versions.
  
  + Request (application/json)
  
      + Headers
  