anchor.diff:  v2 = g.addV(id, 3, label, "software", "name", "lop", "lang", "java").next()
   v1.addEdge("created", v2, id, 9, "weight", 0.4)
   ----
  +
  +IMPORTANT: The `TraversalSource` is a Java `Iterator`. It does *nothing* until it is _iterated_, by calling some
  +form of `next()`. Therefore, a line of code like `x = g.addV()` does not "add a vertex" and assign that vertex to
  +the variable `x`.  It creates a `Traversal` and assigns that value to `x`.
   
   There are a number of important things to consider in the above code. First, why didn't we use `graph.addVertex()`?
   Couldn't that just as easily performed the same function? Yes - it could have, however, TinkerPop encourages
  
positive.code: ===============
  
  link:http://tinkerpop.com[Apache TinkerPop] is an open source Graph Computing Framework. Within itself, TinkerPop
  represents a large collection of capabilities and technologies and in its wider ecosystem an additionally extended
  world of link:http://tinkerpop.incubator.apache.org/#graph-systems[third-party contributed] graph libraries and
  systems. TinkerPop's ecosystem can appear complex to newcomers of all experience, especially when glancing at the
  link:http://tinkerpop.incubator.apache.org/docs/x.y.z/index.html[reference documentation] for the first time.
  
  So, where do you get started with TinkerPop? How do you dive in quickly and get productive? Well - Gremlin, the
  most recognizable citizen of The TinkerPop, is here to help with this thirty minute tutorial. That's right - in just
  thirty short minutes, you too can be fit to start building graph applications with TinkerPop. Welcome to _The Gremlin
  TinkerPop - by Gremlin_!
  
  image::gremlin-gym.png[width=1024]
  
  
negative.code: * They can try different implementations using the same code to decide which is best for their environment.
  * They can grow into a particular implementation if they so desire - start with a graph that is designed to scale
  within a single machine and then later switch to a graph that is designed to scale horizontally.
  * They can feel more confident in graph technology choices, as advances in the state of different provider
  implementations are behind TinkerPop APIs, which open the possibility to switch providers with limited impact.
  
  TinkerPop has always had the vision of being an abstraction over different graph databases. That much
  is not new and dates back to TinkerPop 1.x. It is in TinkerPop 3.x however that we see the introduction of the notion
  