Hi,

This is to hear what the community thinks about tinkerpop auto capturing schema information.

Since labels, any tinkerpop graph has a schema and seeing that tinkerpop captures every vertex and edge with its label it could transparently maintain this in the db itself.

It should add little to no overhead to capturing data as schemas change seldom and are small compared to the actual data.

There are may use cases for having the schema available as part of the regular graph.

* Natural place to attach further (non tinkerpop) info like acl, audit rules, multiplicities, navigability
* Might enable code insight for gremlin.
* Store performance/analytic result.
* Easy for new users to understand any graph's schema
* Might facilitate gremlin optimization
...

I understand that may implementations have their own peculiar schema requirements. However my idea is not to walk a path outside of tinkerpop's own semantics.

Besides all that there is something sweet about a graph containing/managing its own meta data.

Thanks
Pieter

Reply via email to