anchor.diff:  
   The tag operation is also scoped to a specific release. This way new tags can be assigned to your nodes for a specific release without affecting the taggings of nodes within an older release. 
   
  -NOTE: Tags and tag families themself are not versioned. Deleting a tag will remove the tag from all nodes that previously referenced this tag.
  +NOTE: Tags and tag families are not versioned. Deleting a tag will remove the tag from all nodes that previously referenced this tag.
   
   NOTE: Taggings to nodes are not versioned.
   
  
positive.code: | ```/api/v1/:projectName/nodes/:uuid``` | Read           | Node can be read.
  | ```/api/v1/:projectName/nodes/:uuid``` | Update         | Node can be updated.
  | ```/api/v1/:projectName/nodes/:uuid``` | Delete         | Node can be deleted.
  | ```/api/v1/:projectName/nodes/:uuid``` | Read Published | _Not used_
  | ```/api/v1/:projectName/nodes/:uuid``` | Publish        | _Not used_
  |======
  
  ==== Releases
  
negative.code: 
  ==== Updating a Release
  
  A release can be _renamed_ and new schema/microschema versions can be _assigned_ to it.
  
  Renaming is useful if you want to change your development release to be the current production release.
  
  