Go ahead, page through APIs, pore through each elements table, make a note of every available query parameter. Deep inside, you'll feel happy knowing how much easier it is to join data using the YQL Social Tables instead of making several calls to REST URIs, parsing responses, and extracting information with conditional constructions.
Yes, you could use the YQL Social Tables before. But no one documented the tables, provided example queries, listed the available and required keys until now. Use YQL. Get social data. Enjoy.
Here are some mashups with Yahoo! social data that require one REST call with YQL, but multiple calls to individual REST URIs without YQL.
Get the weather information for your contacts and connections. This call would require three separate REST calls and extracting the location and postal elements from responses for the Profile and the GEO APIs. Run the query in the YQL Console:
select * from weather.forecast where location in (select postal from geo.places where text in (select location from social.profile where guid in (select guid from social.connections where owner_guid=me)))
Get a listing of events near your contacts and connections. Again, this query reduces the REST calls from three to one. Run this query in the YQL Console:
select * from upcoming.events.bestinplace where woeid in (select woeid from geo.places where text in (select location from social.profile where guid in (select guid from social.connections where owner_guid=me))
Get the Flickr information for your contacts. Run this query in the YQL Console:
select * from flickr.people.getInfo where user_id in (select user_id from flickr.getidfromusername where username in (SELECT fields.value from social.contacts(1000) WHERE guid=me and fields.type="yahooid"))