anchor.diff:  | `format( /eventDate, "yyyy-MM-dd'T'HH:mm:ss'Z'")` | 2017-10-20T00:00:00Z
   | `format( /eventDate, "yyyy-MM-dd")` | 2017-10-20
   | `format( /eventDate, "yyyy-MM-dd HH:mm:ss Z", "GMT+8:00")` | 2017-10-20 08:00:00 +0800
  -| `format( /eventDate, "yyyy-MM-dd", "GMT+8:00")` | 2017-10-20 
  +| `format( /eventDate, "yyyy-MM-dd", "GMT+8:00")` | 2017-10-20
   |==========================================================
   
   In the case where the field is declared as a String, the toDate function must be called before formatting.
  
positive.code: In the above example, the first RecordPath returns two separate field names: "workAddress" and "homeAddress". The second
  RecordPath, in contrast, returns the value of a "city" field and uses the `fieldName` function as a predicate. The second
  RecordPath finds a "city" field whose parent does not have a name that begins with "work". This means that it will return
  the value of the "city" field whose parent is "homeAddress" but not the value of the "city" field whose parent is "workAddress".  
  
  
  === toDate
  
negative.code: == Descendant Operator
  In addition to providing an explicit path to reach the `zip` field, it may sometimes be useful to reference the `zip` field without knowing
  the full path. In such a case, we can use the `descendant` operator (`//`) instead of the `child` operator (`/`). To reach the same `zip`
  field as above, we can accomplish this by simply using the path `//zip`.
  
  There is a very important distinction, though, between the `child` operator and the `descendant` operator: the `descendant` operator may match
  many fields, whereas the `child` operator will match at most one field. To help understand this, consider the following Record:
  