MySpaceID is a new Open Platform feature which allows MySpace users to grant permissions to other external websites in order to display information available from a user's profile - such as user pictures, status, etc.
Data Portability is a new term which is widely used all over the internet right now with a variety of different definitions- depending on who is asked. All definitions ultimately lead to the same basic concept of taking information from one site and bringing it to another. MySpace is actively involved in investigating the feasibility of Data Portability.
We've created some initial information which is available on the "What is MySpaceID?" page. It includes basic information to guide you through the new process in order to make your data accessible to external sites as well as a table of all available information using MySpaceID.
If you have already signed up to be a MySpace Developer, you don't need to do a thing! Simply go to your app details page, and check the Use External Sites checkbox. This reveals the External URL and External Domain fields described in the documentation above.
If you have never developed an application for MySpace before, you will be asked to fill out the developer sign-up form before proceeding you can Build your application. Developer registrations are processed within 24 to 48 hours.
Yes. You must adhere to the MySpaceID Terms of Use. Failure to comply with these guidelines may result in your application being suspended or disabled.
Specifically you must:
No. Your site may never serve as a proxy for any MySpace data. Users must grant explicit permission for every site that wishes to display their information, and that site must then request the data.
Every external site that uses MySpaceID must include the following icon (image/link) on their site where a user would click to enable MySpaceID. Upon clicking to enable, they'll be redirected to a MySpace page requiring verification that the user wishes to grant permissions.
You must use OAuth for authentication.
Yes, but you must still follow the same restrictions as a Web site.
Please read the MySpaceID Off-Site Service Developer Addendum to MySpace.com Terms of Use Agreement. All uses of MySpaceID are subject to this agreement, the Developer Addendum to MySpace.com Terms of Use Agreement and Off-Site Service Guidelines.
We have answers! Check out our MySpaceID forums on the MySpace Development Platform and ask away.
All of the data available through the MySpaceID REST APIs can be cached for 24 hours. When the 24 hour period expires, you will have to do another API request to refresh the data. This will help ensure that you don't have stale content. As a best practice, we encourage you to check back frequently to ensure that the data you are leveraging is up-to-date.
Please see: Portable Contacts REST Resources for more information on what data is available for caching.
Please check: Portable Contacts REST Resources for the most up-to-date list of what data can be permanently stored. Certain data will be able for scoping by default for storage even after the caching policy expires, while other pieces of data require that the member expressly opt-in so that data may be shared. Even though this subset of data can be stored, you should still check back and refresh your own cache or storage to ensure that you are not serving stale content to your members. While this might not make sense for something like "date of birth", it would for something like the profile picture.
For all data designated as part of the core portable profile and able to be stored, you can retain that data even after the link is broken. For all other data, you must remove the data the next time you make a request to refresh your cache.
