My MySpace parser has been updated. It had fallen in to disrepair, mostly due to my laziness and the fact that I'm still learning Python. I find the try...except loop a bit of a pain compared to PHP’s error handling using @function(). 
It’s a perpetual beta, and all that. I can’t promise I’ve ironed out all the bugs, so please try and look for your profile and send me a comment if there’s a problem.
Anyway, the great news is I’ve added an RDF output as well. I’m using SIOC as the best way of representing data. foaf:Person has to actually represent a person, and foaf:Agent didn’t seem to do much for me. MySpace has this really insanely stupid idea of allowing corporate acounts - bands, websites, radio stations, comedy clubs, movies and all sorts of other collaborative enterprises have accounts. So, sioc:User seems to be the best representation of that - even if that makes it so that we can’t use FOAF tools.
The URL is as follows:
xml.opiumfield.com/myspace/username/format
username takes both the numerical ‘FriendID’ and the alphanumeric name used to go direct to a person’s page (eg. myspace.com/whatever).
format takes one of the following: ‘xml’, ‘json’, ‘opml’, ‘rdf’ or ‘rss’
XML and JSON both provide data about the user (sorry, the JSON isn’t very good - it’s just the XML2JSON script - if you want the data, the XML is highly recommended). The OPML version uses inclusion and is designed to be used with Grazr. The RSS version is the latest comments from the page in an RSS 2.0 feed.
The RDF is an RDF/XML file containing SIOC data. It’s pretty early at the moment - although I will be adding much more to it as we go on. I have a nasty feeling that I’ll have to make a namespace too. D’oh.
Suggestions for improvement of the RDF output are absolutely welcome.
Tags: myspace, rdf, semweb, mashup, xml, opml, grazr, rss, json, sioc
