Okay, before we go anywhere I need a couple of answers. A. Is Instant Personalization ("InP") built on an open protocol? In other words, if I build foo.exampl

Okay, before we go anywhere I need a couple of answers. A. Is Instant Personalization ("InP") built on an open protocol? In other words, if I build foo.example.com and it uses InP to access Facebook's social graph, and later on I decide I also want to support Google's social graph, will Google be able to serve that graph using the same InP protocol? Or can I write a middleware service that grabs data with InP, massages the data (e.g. "filter out only the friends who live in a particular zip code") and reexports the data using the InP protocol? Or will Facebook's lawyers be fighting such a move every step of the way? B. Okay, we're playing in Facebook's world, the world where everyone has a public social graph and everything in their profile is public, public, public. Fine. But does this mean that, if I use Instant Personalization to grab a user's extremely-public social graph, I'm allowed to use it as I would any other public information that I stumbled across on the web? Can I, for example, index it and search it? Or can I write a tool that populates a second social network's database with a list of friends from Facebook? Or will Facebook's InP terms of service require that I avoid doing that, because what "public" really means is "everyone can look at it, but only if they pay Facebook one cent every time they look and promise not to take any pictures or remember anything?"