anchor.diff:  Next, we look at its `titles` field, which is defined to be a `Set`.
   As you might expect, the cardinality of the underlying property becomes `set`.
   Similarly, the `locations` field takes on the `list` cardinality.
  -Further, each element in the `locations` list has it's own meta-properties, and ergo deserves a link:./src/test/java/org/apache/tinkerpop/gremlin/object/vertices/Location.java[Location] class of it's own.
  +Further, each element in the `locations` list has it's own meta-properties, and ergo deserves a link:gremlin-objects/src/test/java/org/apache/tinkerpop/gremlin/object/vertices/Location.java[Location] class of it's own.
   
   [source, java]
   ----
  
positive.code:     .addEdge(Uses.of(Expert), "tinkergraph")
  ----
  
  To see how the `modern` and the `crew` reference graphs may be created using the object `Graph` interface, go link:./src/test/java/org/apache/tinkerpop/gremlin/object/graphs/[here].
  
  TIP: Since the object being added may already exist in the graph, we provide link:./src/main/java/org/apache/tinkerpop/gremlin/object/structure/Graph.java[various options] to resolve "merge conflicts", such as `MERGE`, `REPLACE`, `CREATE`, `IGNORE` AND `INSERT`.
  
  ==== Querying Objects
  
  There are two ways to get a handle to the link:./src/main/java/org/apache/tinkerpop/gremlin/object/traversal/Query.java[Query] interface.
  You can inject it like so:
  
  [source, java]
  
negative.code:     .select();
  ----
  
  To see more examples showcasing how the object `Query` interface may be used, go link:gremlin-objects/src/test/java/org/apache/tinkerpop/gremlin/object/ObjectGraphTest.java[here].
  
  === Providers
  
  