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: }
  ----
  
  You can find more examples of gremlin object vertices link:./src/test/java/org/apache/tinkerpop/gremlin/object/vertices/[here] and edges link:./src/test/java/org/apache/tinkerpop/gremlin/object/edges/[here].
  
  ==== Updating Objects
  The link:./src/main/java/org/apache/tinkerpop/gremlin/object/structure/Graph.java[Graph] interface lets you update the graph using `Vertex` or `Edge` objects.
  You can get it via dependency injection, assuming you've an `Object` provider for `GraphTraversalSource`:
  
  [source, java]
  
negative.code: 
  ==== Service Provider Interface
  A provider that wishes to plug into `gremlin-objects` through dependency injection, will need to provide a `GraphTraversalSource` of it's choice, through the `Object` qualifier.
  For users that don't use dependency injection, they may manually pass the `GraphTraversalSource` to the link:gremlin-objects/src/main/java/org/apache/tinkerpop/gremlin/object/provider/GraphFactory.java[GraphFactory].
  
  ==== Registering Native Types
  Typically, gremlin property values are Java primitives.
  