Jean-Pierre, this looks a lot like the deduction of resulting permissions in a nested Access Control List. There is a brief example on that at http://wiki.neo4j.org/content/ACL that might be in that direction?
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Fri, May 13, 2011 at 2:20 AM, Jean-Pierre Bergamin <jpberga...@gmail.com>wrote: > Dear neo4j users > > We are in the course of evaluating neo4j for our application. Our model is > quite similar to a fault tree ( > http://en.wikipedia.org/wiki/Fault_tree_analysis), where states ("ok" or > "not_ok") in leaf nodes get pushed up the tree. There are rules what state > the parent gets, depending on the states of its children: > * the parent is only ok, when all children are ok ("and" conjunction) > * the parent is ok, when any child is ok ("or" conjunction) > * the parent is ok, when at least 3 of the 5 children are ok > * etc. > > We are now looking for ways to model such a fault tree so that those rules > can be applied. > Since we just started with neo4j I'd like to ask if there is a "good known > practice" to model someting like this, before we start to head in a totally > wrong direction. > > > Best regards, > James > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
