anchor.diff:  link:https://issues.apache.org/jira/browse/TINKERPOP-892[TINKERPOP-892]
   * `tx()` - as discussed in the earlier paragraph
   
  +[[gremlin-language-subset]]
   == Gremlin Language Subset
   
   On link:https://issues.apache.org/jira/browse/TINKERPOP-1417[TINKERPOP-1417], it was suggested that we "Create a
  
positive.code: * path, simplePath, cyclicPath
  * groupCount, sum, group, count, max, min, etc. (reducing barriers)
  
  === Comments
  
  This has an interesting potential impact on GLVs because "Little Gremlin" could be implemented within them for
  client-side traversals over remote subgraphs, where the subgraph is like a remote transaction. All graph mutations
  
negative.code: Build it locally then submit it remotely and have the server sort out the merging. It's perhaps the most natural way
  to load data. With "Gremlinito" you then get the added power of being able to traverse a local subgraph.
  
  [[serialization]]
  == Serialization
  
  Have we yet found the appropriate serialization model? We didn't have it in 2.x at all. In 3.x we went with a use case
  based approach that made a lot of sense in the first few releases of 3.x, but the use cases couldn't have conceived
  of what was to come with the development of GLVs. GLVs rendered Gryo, the decided "network option" from the use cases,
  to be pretty useless given that it is of the JVM only and GraphSON has gone through three versions now trying to find
  the appropriate format to cover the various features we've attempted to support. While GraphSON 3.0 seems to have met
  the mark for supporting our needs, it seems bloated with Java types and doesn't perform terribly well in some cases.
  
  An ideal serialization format would be:
  
  * Compact for network transport
  * Human readable (which competes with "compact" at some level)
  * Language agnostic
  * Exposes a small set of types that makes the format easy to maintain and test
  * Extendable or perhaps built in such a way that graph providers could coerce their types to and from the types
  that TinkerPop exposes
  * Upgrade friendly so that it is possible to easily detect the version of a format and have the system act
  transparently so as to avoid the heavy configuration that users currently have to do to be sure their versions of
  TinkerPop and their version of their serializers align
  
  == Uniform Object Model
  
  On link:https://issues.apache.org/jira/browse/TINKERPOP-1909[TINKERPOP-1909], it was suggested that we are going to
  use reference (id/label) based object model. And, the direction is move towards more tidy object model contracts going
  forward. Reference model definitely provides big performance improvements especially with multi-property
  vertices/edges.  One thing that we can consider is to provide a configurable object model. Enabling users to
  configure the object model (OutputFormat) as server settings (Exposing server setting is being discussed here
  link:https://issues.apache.org/jira/browse/TINKERPOP-1636[TINKERPOP-1636]). There will three types of output format.
  
  * Reference: includes id and label
  * GraphSONCompact: object reference along with properties
  * GraphSON: object reference, properties and edge details(inE/outE).
  
  === Comments [as]
  
  This will enable the clients model based on their needs and avoid multiple query if they are sure what is expected 
  from a gremlin query. If we need more details like edges/property as part of response, we can override the server 
  configuration as part of the gremlin request arguments as hint.
  
  === Comments [spm]
  
  A more full object model may be necessary as we consider implementing the options of the
  <<gremlin-language-subset,Gremlin Language Subset>>. A more robust object model, or at least the option to open up a
  more robust object model, could be necessary to support features there. We should also consider that the future is not
  necessarily a GraphSON format and could be something else as described in the <<serialization,Serialization>> section.
  
  == Testing Framework
  
  