有向图的规范
这是与有向图相关的相当高级的主题。我正在为一个项目研究 NOSQL 技术。特别是使用图形数据库。它非常适合支持我想要保存关系的丰富模型，并且问题域是图本身（顶点和边）。显然，这让我开始关注 Neo4j 和这个领域的其他供应商。现在我相信他们已经解决或缩小了以图形数据结构方式保存数据的差距......这是完美的。
然而，我的要求更进一步，需要理解有向图的规范以创建“有向图”的实际实例，以便在实际创建图时遵守特定的规则和约束。图形数据库本身并不关心这一点，这是正确的，并且也不需要它（很高兴它对此不可知）。问题是，这使其有点开放式，以确保图形符合图形规则（即某些节点可以具有某些关系，甚至与其他节点具有关系）。我应该使用什么来指定有向图的规范/元数据，以便在运行时创建它的实例时它正确地遵循它 规格。
任何有关可用内容或解决此问题的标准方法的帮助或建议将不胜感激
This is a fairly advanced topic related to directed graphs. I am looking into NOSQL technology for a project. In particular, using graph databases. It's a perfect fit in supporting the rich model I want to save relationships for and the problem domain is a graph itself (vertices and edges). Now obviously this made me look at Neo4j and other vendors in this space. Now I believe they def have solved or closed the gap with persisting data in a graph data structure way...which is perfect.
However my requirement goes further where there is a need to understand a specification of a directed graph to create an actual instance of a 'directed graph', such that particular rules and constraints are adhered to when actually creating the graph. The graph database doesn't concern itself with this which is correct and wouldnt want it too (happy that it's agnostic of this). The problem is this leaves it a little open ended as what ensures that the graph complies with your graph rules (ie that certain nodes can have certain relationships or even have relationships to other nodes). What should I be using that will allow me to specify the specification/metadata of the directed graph such that when creating an instance of it at runtime it adheres correctly to it's
specification.
Any help or suggestions on what is available or what is the standard way to approach this would be appreciated
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为你应该看看 Spring Data Graph， http://www.springsource.org/spring -data/neo4j 这与拥有一个强大的映射层一样接近，可以投影规则等，就像 JPA 或 Hibernate 一样。
WDYT？
/彼得
I think you should take a look at Spring Data Graph, http://www.springsource.org/spring-data/neo4j that is as close as you get in having a powerful mapping layer that can project rules etc, much like JPA or Hibernate.
WDYT?
/peter