As the graph will be ever evolving, it may make sense to keep track of both the time a node was updated (or reviewed for needing an update) and the last time the graph was updated.
This sounds very much like a map-reduce type problem but I don't know enough about map-reduce to decide what should be done. Maybe a Google guru will sweep down and show me how to manage a graph that may house inconsistent data due to it's ever-changing nature and the inability to keep everything up to date, (not that it needs to be).
As the graph will be ever evolving, it may make sense to keep track of both the time a node was updated (or reviewed for needing an update) and the last time the graph was updated.
This sounds very much like a map-reduce type problem but I don't know enough about map-reduce to decide what should be done. Maybe a Google guru will sweep down and show me how to manage a graph that may house inconsistent data due to it's ever-changing nature and the inability to keep everything up to date, (not that it needs to be).