FOAF following

1 view
Skip to first unread message

David Janes

unread,
Mar 11, 2008, 5:40:00 AM3/11/08
to Social Graph API
I'm looking at this FOAF file here [1] which is packed full of goodies
(via foaf:Person -> foaf:mbox_sha1sum & rdfs:seeAlso). The FOAF file
[2] is referenced from the "user"'s home page. Yet when I do a query
I'm not seeing anything. Is there something wrong with this FOAF file
or with my understanding of how this should be interpreted.

Regards, etc...

[1] http://buzzbot.buzznet.com/user/foaf.xml
[2] <link rel="meta" type="application/rdf+xml" title="FOAF"
href="http://buzzbot.buzznet.com/user/foaf.xml" /
[3] http://buzzbot.buzznet.com/user/
[4] http://socialgraph-resources.googlecode.com/svn/trunk/samples/findyours.html?q=http%3A%2F%2Fbuzzbot.buzznet.com%2Fuser%2Ffoaf.xml

judie...@gmail.com

unread,
Mar 12, 2008, 9:53:54 AM3/12/08
to Social Graph API
I have not had time to make a study of it myself, but my two FOAF at
http://www.grey-cat.com/foaf.rdf
http://www.grey-cat.com/foaf-more.rdf

seem also to fail to show any links in the several sample tools.
Previously, I'd always used FOAF explorer to make human readable
versions of the files.

http://xml.mfd-consult.dk/foaf/explorer/?foaf=http://www.grey-cat.com/foaf-more.rdf

I too would like to know more about FOAF interpretation.

Cheers,

judith

(Who realizes the gmail address probably isn't in the FOAF. Hmmm)

Brad Fitzpatrick

unread,
Mar 12, 2008, 12:45:56 PM3/12/08
to social-g...@googlegroups.com
Sorry, for the past couple weeks the entire index hasn't been parsed regularly.  I just checked your URLs and it's not a parse problem, but just that they're not in the set that's being parsed.

I'm working on redoing part of the pipeline to reduce the overall latency from the time something's crawled (including support for crawling things specifically for the Social Graph API) to the time it's available via the API.  During that process I've scaled back which content is parsed.

Things have been going well the past few days... I expect to get back to including the full index this week, and hopefully have some new stuff available for you guys to play with diagnostic-wise to see how things are being parsed behind the scenes.  (exposing the parser by itself via a new API endpoint)

- Brad
Reply all
Reply to author
Forward
0 new messages