Onaswarm is now provides a interface for finding out the social network connectivity of webpages. Connections are discovered using XFN, hCard, FOAF, optionally Google's SGN services and in some instances custom APIs if account information is available to Onaswarm.

URI

• http://onaswarm.com/admin/sgn-query/

Parameters

• uri - the URI of a page you'd like to discover social network details for
• wrapper - if "ajax", the results will be returned in JSON format
• json_pretty - boolean; the results will be pretty printed
• jsonp - if non-empty, the results will be placed in a JSONP wrapper
• reverse - boolean; the results will reflect links to this page, as opposed to outbound from this page
• google - boolean; add results from Google Social Graph API. In HTML mode, this defaults to True; in AJAX, False.
• appkey - coming soon

Example Queries

• http://onaswarm.com/admin/sgn-query/

form interface

• http://onaswarm.com/admin/sgn-query/?uri=http://twitter.com/bvl/

all links from Twitter user "bvl" in HTML, augmented with Google SGN results

• http://onaswarm.com/admin/sgn-query/?uri=http://twitter.com/bvl/&wrapper=ajax&json_pretty=1&reverse=0&google=0

all links outbound from Twitter user "bvl", without Google SGN results

• http://agwego.net/admin/sgn-query/?action=query&uri=http%3A%2F%2Fdanbri.org%2Ffoaf.rdf&wrapper=ajax&json_pretty=1

Dan Brickley's FOAF file

• http://agwego.net/admin/sgn-query/?action=query&uri=http://tantek.com/&wrapper=ajax&google=0&json_pretty=1

Notes

• if our server is experiencing unusual loads, this API will return 503 errors
• there's a lot more we could do with the FOAF files - tell us what
• if we did FOAF output, would you use it?
• we will be using appkeys to access to API in the near future, mainly to stop robots from crawling the web through our API!

• FOAF following -- why aren't Buzznet FOAF results showing up in the social graph?
• sgn://mboxsha1 format inconsistency -- what's the system for these SGN:// things anyhoo?

Brian Suda has an article on Dev.Opera about XFN - XFN encoding, extraction, and visualizations. It's a great place to start reading about XFN:

XFN stands for XHTML Friends Network[...]. It grew out of the common publishing trend of linking to other sites you enjoyed reading. On your blog, this is called a blogroll - it is common to think of people by their web sites. Their URL is a representation of that person; part of their online identity. XFN is an attempt to codify these relationships using standard HTML.

I was going to nitpick about Brian's point about tool support for XFN, but I shall get into that in upcoming posts about the social graph.

After attending SGFooCamp (photos), I've been meaning to playwith Google'snew Social Graph API a little more.

The SGAPI is a fairly simple and powerful tool:

• it looks for data captured on the web by the Google crawler, namely:
  • XFN links (normal webpage links with rel="something" markers),
  • FOAF information, which I won't go into
• this data defines a graph, with nodes being webpages (which are URLs, and URLs are people) and edges being relationships
• it's not a proprietary Google data store
• there's one RESTful GET call in the API that returns the graph given a starting URL

That sounds kind of abstract, but it's really quite simple. For example, consider all the web services you use:your blogger.com account, your flickr account, your del.icio.us account, your twitter account, and your home page. They're all"you"and should have additional information to indicate that they belong to the same person. XFN defines this asthe rel="me" relationship.

Let's look at a specific example: Mark Kuznicki'saccount. Usingthe magic of thedemo application, we can see that Mark has a number of accounts that are claiming that they're him:

Why? Because Mark entered the URL of his home page and these applications added a link marked with rel="me" on the appropriate A tag. (If you don't believe, follow thelinks and look at the source).

Now, why does it (currently -- 2008-02-20) call these "possible" connections? Simple: because Mark hasn't linked back to these sites on his home page with A linksmarked rel="me".

Why should Mark do this? Simple:

• because if he does this he can have identity consolidation on all his public social networks, that is, by giving only his home page URL we can definitely know all the social networks that Mark belongs to (and not just claim that Mark is a member of)
• and by knowing this, we can start exploring other (web) relationships that mark is involved in, such as rel="friend"
• and if he starts doing this, pretty soon we have a solution to the YANS problem: when Mark joins a site, he need merely specify his home page and his friends are automatically found -- and without having to screw around with the password anti-pattern or manually re-entering all friends.