Mailing-List: contact commits-help@tinkerpop.incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: dev@tinkerpop.incubator.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1740606 - in /incubator/tinkerpop/site: gremlin.html
 providers.html
Date: Fri, 22 Apr 2016 20:38:03 -0000
To: commits@tinkerpop.incubator.apache.org
From: okram@apache.org
Message-Id: <20160422203803.B6B1C3A0873@svn01-us-west.apache.org>

Author: okram
Date: Fri Apr 22 20:38:03 2016
New Revision: 1740606

URL: http://svn.apache.org/viewvc?rev=1740606&view=rev
Log:
removed all vendor references. replaced with provider.

Modified:
    incubator/tinkerpop/site/gremlin.html
    incubator/tinkerpop/site/providers.html

Modified: incubator/tinkerpop/site/gremlin.html
URL: http://svn.apache.org/viewvc/incubator/tinkerpop/site/gremlin.html?rev=1740606&r1=1740605&r2=1740606&view=diff
==============================================================================
--- incubator/tinkerpop/site/gremlin.html (original)
+++ incubator/tinkerpop/site/gremlin.html Fri Apr 22 20:38:03 2016
@@ -393,7 +393,7 @@ g.V().hasLabel("person").
          The user can write their traversals in any way they choose. However, ultimately when their traversal is compiled, and depending up the underlying execution engine 
          (i.e. an OLTP graph database or an OLAP graph processor), the user's traversal is rewritten by a set of <em><a href="http://www.planettinkerpop.org/reference/#traversalstrategy">traversal strategies</a></em> which do their best to determine the most optimal execution
          plan based on an understanding of graph data access costs as well as the underlying data systems's unique capabilities (e.g. fetch the Gremlin vertex from the graph database's "name"-index). 
-         Gremlin has been designed to give users flexibility in how they express their queries and vendors flexibility in how to efficiently evaluate traversals against their TinkerPop-enabled data system.
+         Gremlin has been designed to give users flexibility in how they express their queries and graph system providers flexibility in how to efficiently evaluate traversals against their TinkerPop-enabled data system.
       </div>
       <br/>
       <div class="container">

Modified: incubator/tinkerpop/site/providers.html
URL: http://svn.apache.org/viewvc/incubator/tinkerpop/site/providers.html?rev=1740606&r1=1740605&r2=1740606&view=diff
==============================================================================
--- incubator/tinkerpop/site/providers.html (original)
+++ incubator/tinkerpop/site/providers.html Fri Apr 22 20:38:03 2016
@@ -192,17 +192,17 @@
             </div>
             <br/>
             It is (relatively) easy for a data system to become TinkerPop-enabled. There are two interface packages that need to be implemented with one of them being optional. Once implemented 
-            the Gremlin traversal machine can talk to the vendor's system and thus, so can any of their users' Gremlin traversals as well as any existing tools/technologies that have been designed 
+            the Gremlin traversal machine can talk to the provider's system and thus, so can any of their users' Gremlin traversals as well as any existing tools/technologies that have been designed 
             to interact with a TinkerPop-enabled system.
             <br/>
             <br/>
             <ol>
-               <li><strong>The Graph (required)</strong>: These foundational interfaces define the semantics of the operations on a graph, vertex, edge, and property. Once implemented, the vendor's data system can immediately be queried using Gremlin OLTP. However, vendors may want to provide a collection of vendor-specific compiler optimizations called traversal strategies which can leverage their product's unique features (e.g. global indices, vertex-centric indices, sort orders, sequential scanners, push-down predicates, etc.).</li>
+               <li><strong>The Graph (required)</strong>: These foundational interfaces define the semantics of the operations on a graph, vertex, edge, and property. Once implemented, the provider's data system can immediately be queried using Gremlin OLTP. However, providers may want to leverage a collection of provider-specific compiler optimizations called traversal strategies which can leverage their product's unique features (e.g. global indices, vertex-centric indices, sort orders, sequential scanners, push-down predicates, etc.).</li>
                <br/>
                <li><strong>The GraphComputer (optional)</strong>: All OLAP-based graph processors must implement the primary graph interfaces mentioned above as well as a set of parallel-processing message-passing interfaces. However, it is possible for a data system to only implement the primary graph interfaces and still provide OLAP support to their users by integrating their system with an existing GraphComputer implementation such as, for example, SparkGraphComputer or GiraphGraphComputer (both are provided in Apache's distribution of TinkerPop).</li>
             </ol>
             <br/>
-            Finally, there are other tools and technologies that the vendor can leverage from TinkerPop such as Gremlin Server, Gremlin Console, and the like. The purpose of Apache TinkerPop is to make it easy for vendors to add graph functionality to their product and/or to build a product from scratch and immediately have a query language, server infrastructure, metrics/reporting integration, cluster-based analytics and more.
+            Finally, there are other tools and technologies that the provider can leverage from TinkerPop such as Gremlin Server, Gremlin Console, and the like. The purpose of Apache TinkerPop is to make it easy for providers to add graph functionality to their product and/or to build a product from scratch and immediately have a query language, server infrastructure, metrics/reporting integration, cluster-based analytics and more.
          </div>
          <br/>
          <div class="container">