We're discussing how to expose traversers in the REST API. One of the ideas
that was brought up (more emails with the rest of the ideas are coming) was
to use xpath directly in the URIs. A doubt we're having about that is that
it might not be perfectly RESTful, although USEful.
We'd like to get input from you guys (looking slightly more at you dr. Jim
Webber).
We'd imaginge it would look something like this:
o From the node representation (/node/5) you discover a URI template:
/node/5/xpath/{xpath}
o You insert your xpath query into it and GET, the resulting nodes will be
returned.
Example: GET /node/5/xpath/parent/mother
would return the grand mothers of this node.
A cool feature that this would also enable is that we could expose URI
templates for doing the same kind of xpath traversals from the result set of
an index lookup by exposing a URI template like this one:
/index/node/{key}/{value}/xpath/{xpath}
Example: GET /index/node/name/Mattias/xpath/child
would return the children of all nodes with 'name' = 'Mattias'
So, what do you guys think?
--
Mattias Persson, [matt...@neotechnology.com]
Neo Technology, www.neotechnology.com
_______________________________________________
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
