anchor.diff:  This only affects embedded usage, where you can already start to wrap read operations in transactions to be prepared for the future.
   
   The `!` and `?` property operators in Cypher::
  -In future releases, expressions like `node.property = "value"` will not fail when a node is encountered without the property, and will instead return null. This is the same behaviour as `node.property! = "value"`, and thus the `!` property operator is deprecated and will be removed.
  +In future releases, expressions like `node.property = "value"` will not fail when a node is encountered without the property, and will instead return null. This is the same behavior as `node.property! = "value"`, and thus the `!` property operator is deprecated and will be removed.
   Expressions using the `?` property operator, such as `node.property? = "value"`, are also deprecated. Please use `not(has(node.property)) OR node.property = "value"` instead.
   
   Cypher CREATE syntax::
  
positive.code: 
  Using parameters to identify nodes in patterns::
  In future releases, parameters can not be used to identify nodes in a pattern (ie. `MATCH ({node})-->(other))`).
  Note that this form was only possible when mixing the embedded Java API and cypher, and thus does not affect users Neo4j Server.
  
  Iteration syntax in `FOREACH`, `EXTRACT`, etc::
  In future releases, the iterating functions will use a `|` instead of a `:` to separate the components of the statement. For example, `EXTRACT(n in ns : n.prop)` is replaced with `EXTRACT(n in ns | n.prop)`. The iterating functions include `FOREACH`, `EXTRACT`, `REDUCE`, `ANY`, `ALL`, `SINGLE` and `NONE`. Note the alternative form using `|` is also possible in Neo4j 1.9.2 and later.
  
negative.code: 
  The Reference Node::
  With the introduction of Labels in Neo4j 2.0 the Reference Node becomes obsolete and will be removed.
  Instead, labeled nodes become the well-known starting points in your graph.
  
  