[joe_the_user]

Well, the graph API reports things as JSON. Your app has to page through the resulting json and see what information is relevant and meaningful.

I'm barely starting the Facebook API but the solution I'll use is to put the code for interpretating a given query into a series of configuration files using a DSL to interpret the Json. It's mostly a series of entries like:

    foo = [bar or baz or "default"] 

This way any change in graph structure can be dealt with quickly (this would be a problem for XML/XSLT except they are too slow AND they don't do incremental interpretation).