[
https://issues.apache.org/jira/browse/TINKERPOP3-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491100#comment-14491100
]
David Crouch commented on TINKERPOP3-524:
-----------------------------------------
[~spmallette] due to some obstacles with TP3 I ended up rolling my own graph
strategy implementation and the custom DSL work I have done now does not align
with M8. I would like to make a contribution and had wanted to use the code I
developed but it now requires a lot of re-work. The gist of most of my
development is trying to support meta-properties on edges. This functionality
makes a lot of my use cases easier to implement - security, history etc.
I think I'm going to wait and see what the state of the API is at GA. I have
also discovered the wonderful world of NodeJS, which opens up some very
interesting design alternatives.
> Include description in docs on using vertex vs. edge relating to properties
> ---------------------------------------------------------------------------
>
> Key: TINKERPOP3-524
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-524
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: documentation
> Reporter: davidcrouch
>
> This is from the discussion in TINKERPOP3-489. I think it is easy to walk
> down 80% of the development path and then get to a point and say "I need
> meta-properties on edges".
> Per the discussion in TINKERPOP3-489 and the points made by [~mbroecheler] on
> the difference between the vertex and edge concepts (and vertex properties
> vs. edge properties), when the question above is asked the edge should really
> be broken out and represented as a vertex since it is being used to try and
> represent a higher-level concept.
> This is a very easy trap to fall into and worth a paragraph in the docs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
