[08/43] incubator-tinkerpop git commit: removed an IMPORTANT saying that Vertex.property(key, value) is single cardinality.

[dk...@apache.org]

removed an IMPORTANT saying that Vertex.property(key,value) is single cardinality.


Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/16939e08
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/16939e08
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/16939e08

Branch: refs/heads/preprocessor
Commit: 16939e08be282fb316605205c0fbf7df16775dca
Parents: 21a20c9
Author: Marko A. Rodriguez <ok...@gmail.com>
Authored: Tue Jun 2 08:14:02 2015 -0600
Committer: Marko A. Rodriguez <ok...@gmail.com>
Committed: Tue Jun 2 08:14:02 2015 -0600

----------------------------------------------------------------------
 docs/src/the-graph.asciidoc | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/16939e08/docs/src/the-graph.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/the-graph.asciidoc b/docs/src/the-graph.asciidoc
index 1a761f4..a7e86d2 100644
--- a/docs/src/the-graph.asciidoc
+++ b/docs/src/the-graph.asciidoc
@@ -133,8 +133,6 @@ g.V().has('name','gremlin').inE('uses').
       select().by('skill').by('name') // rank the users of gremlin by their skill level
 ----
 
-IMPORTANT: The default behavior for `Vertex.property(key,value)` is dependent on the graph implementation.  Please refer to the documentation of the graph to determine this method's behavior.
-
 Graph Variables
 ---------------
 
@@ -578,7 +576,7 @@ Namespace Conventions
 End users, <<implementations,vendors>>, <<graphcomputer,`GraphComputer`>> algorithm designers, <<gremlin-plugins,GremlinPlugin>> creators, etc. all leverage properties on elements to store information. There are a few conventions that should be respected when naming property keys to ensure that conflicts between these stakeholders do not conflict.
 
 * End users are granted the _flat namespace_ (e.g. `name`, `age`, `location`) to key their properties and label their elements.
-* Vendors are granted the _hidden namespace_ (e.g. `~metadata`) to to key their properties and labels. Data key'd as such is only accessible via the vendor implementation code and no other stakeholders are granted read nor write access to data prefixed with "~" (see `Graph.Hidden`). Test coverage and exceptions exist to ensure that vendors respect this hard boundary.
+* Vendors are granted the _hidden namespace_ (e.g. `~metadata`) to key their properties and labels. Data key'd as such is only accessible via the vendor implementation code and no other stakeholders are granted read nor write access to data prefixed with "~" (see `Graph.Hidden`). Test coverage and exceptions exist to ensure that vendors respect this hard boundary.
 * <<vertexprogram,`VertexProgram`>> and <<mapreduce,`MapReduce`>> developers should, like `GraphStrategy` developers, leverage _qualified namespaces_ particular to their domain (e.g. `mydomain.myvertexprogram.computedata`).
 * `GremlinPlugin` creators should prefix their plugin name with their domain (e.g. `mydomain.myplugin`).