I'm looking to do the following to allow bands to update their information from a central source (i.e. their web site) and have it automatically appear on their myspace profile (so they don't have to copy/paste a bunch of times)
- Post a blog entry
- Post a bulletin
(Note: If the API doesn't allow these, could it be done by having the App display the posts itself on the band's profile page?)

- Get a friend's birthday and/or age
- Look up a user by their email address (This is to link the band's email list to their fan's myspace accounts)

Thanks!

Grant

I actually created a prototype app of similar purpose for a now dissapeared company known as usync, which  made it easy for bands to create their own webpage to sell music and post downloads, etc.

 The app I have is basically an RSS reader, that reads an RSS feed from the artists webpage, displaying the content(text, images, links, etc). I can also add the ability to post bulletins automatically and get a friends birthday or age.

 I don't think it's possible to post blog entries or search for users with the API. You can only access information about the viewer, owner, viewers friends, and owners friends.

Since the MySpace container does not yet support User Data or Activities, what you want to do will probably have to be managed by an external application server.  I've been struggling for days to get some sort of persistent storage going with the MySpace implementation of OpenSocial only to find out that they don't support half of OpenSocial yet.  That doesn't mean it can't be done, it just means you have to move persistent storage off of OpenSocial and access it via a call to makeRequest - similar to the RSS feed example someone posted above (except RSS is passive and you can't communicate changes to it, which is what would be required for a blogging application).  You can make a call to a php, asp.net, perl, xml, you name it, application to provide the data.  You would also have to provide an interface for updating of data and wrap that all up into some security token, probably the myspace friend id and auth token (to prevent hacking and unauthorized access of data). 

 So, your architecture will look something like this:

Your Band Gadget <==> MySpace API Servers <==> Your Application on another server

Hope that helps with your design.  Drop me an email if you want to discuss anything more in depth.