anchor.diff:  
   == Background
   
  -In a way, Cypher already has existential subqueries - pattern predicates allow checking for the existence of subgraphs.
  +In a way, Cypher already has existential subqueries - pattern predicates checking for the existence of subgraphs.
   This form is helpful, but not exhaustive in the types of subqueries that users want to be able to express.
   
   == Proposal
   
  -To make this feature more powerful, add a new function named `exists`, and a keyword named the same, which allows for two different predicates:
  +To make this feature more powerful, this CIP suggests the addition of a new function `exists()`, and a keyword `EXISTS {}`, allowing for two different predicates:
   
  - * Property existence checking
  - * Subquery existence checking
  +* Property existence checking
  +* Subquery existence checking
   
   === Syntax
   
  
positive.code: RETURN person
  ----
  
  This proposal also allows for powerful subqueries, for example using aggregation inside the EXISTS query.
  E.g. find all teams that have at least two members who have worked on successful projects.
  
  [source, cypher]
  ----
  MATCH (team:Team)
  
negative.code: ----
  
  === Interaction with existing features
  
  The `EXISTS {}` subquery clause renders obsolete the current pattern predicate syntax.
  This allows the pattern predicates to be deprecated and/or removed in favour of `EXISTS {}`.
  
  == What others do
  
  This is very similar to what SQL does with its `EXISTS` functionality.
  
  This is also very similar in syntax to what SPARQL does with its `EXISTS` functionality; the rules regarding variables are identical, and the inner query also takes a subquery as input.
  
  == Benefits to this proposal
  
  