Re-using social media data
•Download as PPTX, PDF•
12 likes•7,439 views
the practical reuse of social media data and how it can create better user experience. Combining Google’s Social Graph API with open data sources like RSS and Microformats to provide a wealth information about your users.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Re-using social media data
Similar to Re-using social media data (20)
More from Glenn Jones
Recently uploaded
Recently uploaded (20)
Re-using social media data
- 1. Re-using social media data Glenn JonesCodebits– Lisbon, Portugal4 Dec 2009
- 2. Objects Social Media Aggregation Conversation Activity
- 3. Identity Relationships Objects Social Media Aggregation Conversation Activity
- 4. Most of us have built identities across the web, we fill in profiles, upload photos, videos, reviews and bookmarks
- 5. Identity Identity Distributed Identity Identity Our web identity is fragmented or distributed
- 7. The power of XFN rel=me < a href=“http://www.glennjones.net/” rel=“me”>http://www.glennj... </a>
- 10. A graph (map) of rel=me linkages Found Site Found Site Start Site Found Site Found Site Found Site Found Site Found Site
- 11. Types of social graph linkages Start Site Found Site rel=me Outward claim Start Site Found Site rel=me Inward claim Start Site Found Site rel=me Reciprocalclaim
- 12. Google Social Graph API http://socialgraph.apis.google.com/otherme? q=http://twitter.com/glennjones
- 13. Google Social Graph API JSON { "http://delicious.com/glennjonesnet": { "attributes": { "rss": "http://feeds.delicious.com/rss/glennjonesnet", "url": "http://delicious.com/glennjonesnet", "profile": "http://delicious.com/glennjonesnet" } }, "http://huffduffer.com/glennjones": { "attributes": { } }, ...
- 14. A JavaScript library that retrieves and aggregates profiles from across the web
- 16. 10 identities - outward rel=me links 20 identities - combined outward and inward rel=me links 5 additional identities – side effect profile parsing
- 17. Profile parsing
- 20. ufXtractmicroformat API { "microformats": { "vcard": [{ "fn": "Glenn Jones", "n": { "given-name": ["Glenn"], "family-name": ["Jones"] }, "adr": [{ "locality": "Brighton", "country-name": "United Kingdom" }], ...
- 21. Google Social Graph API endpoint descriptions are not as complete as they could be { "http://delicious.com/glennjonesnet": { "attributes": { "rss": "http://feeds.delicious.com/rss/glennjonesnet", "url": "http://delicious.com/glennjonesnet", "profile": "http://delicious.com/glennjonesnet" } }, "http://huffduffer.com/glennjones": { "attributes": { } }, ...
- 22. Ident Engine – data overlayof endpoint descriptions { "name": "Last.fm", "domain": "last.fm", "urlmappings": [{ "urltemplate": "http://www.last.fm/user/{username}", "schema": "hCard", "contenttype": "Profile", "mediatype": "Html" }, { "urltemplate":"http://www.last.fm/user/{username} ", ...
- 27. Auto fill forms
- 29. The most common details shared across social media sites – work personas
- 30. The most common details shared across social media sites – social personas
- 31. Parsing user generated content from discovered endpoints
- 32. Ident Engine – user generated content endpoint descriptions { "name": "Vimeo", "domain": "vimeo.com", "urlmappings": [{ "urltemplate": "http://vimeo.com/{username}/videos/rss", "schema": "Atom", "contenttype": "Video", "mediatype": "Atom" } ...
- 34. Audio
- 35. Bookmarks
- 36. Entries
- 37. Events
- 38. Friends
- 39. Friends Status
- 40. Images
- 41. Interests
- 42. Lifestream
- 43. Profile
- 44. Resume
- 45. Services
- 46. Slides
- 47. Status
- 48. Video
- 49. Atom
- 50. RSS
- 51. XFN
- 52. XFN-hCard
- 53. hAtom
- 54. hCalendar
- 55. hCard
- 56. hResume
- 58. Yahoo’s YQL API
- 60. Dealing with imposters androgue relationships
- 63. Let the user decide
- 64. Only use reciprocal or outward rel=me links only
- 65. Only use outward or reciprocal rel=me links only
- 66. Now it’s your turn to use identity discovery to build a little magic into your applications
- 67. Microformats Parsershttp://microformats.org/wiki/parsers Microformats Parser - Optimus - XSLT http://microformatique.com/optimus/ Microformats Parser - Cognition - Perlhttp://buzzword.org.uk/cognition/ Google Social Graph APIhttp://socialgraph.apis.google.com/ Social Graph Node Mapper http://code.google.com/p/google-sgnodemapper/ YQL http://developer.yahoo.com/yql/ Ident Enginehttp://identengine.com/ UfXtract http://ufxtract.com/ Madgex Labshttp://lab.madgex.com/ Bloghttp://www.glennjones.net/
- 68. Creative Commons Attribution-Non-Commercial 2.0 UK: England & Wales Licence.Copyright Glenn Jones 2009www.glennjones.net
Editor's Notes
- Apart from social media sites adding rel=me links to their profile pages and individuals marking up blogs with the elsewhere on the web patternA number of specialist sites are now listing peoples Distributed Identities to help project web personsa and also mark services that they aggregating information from
- So now I have explained how this work how do we programmatically access this dataWell just over a year ago Google release the Social Graph APIIt has 3 major methods, the otherme method is the simplest In the example on the slide q= the starting point URL for its search
- There are many software libraries that can parser microformatsUfXtract is a c sharp parser I wrote an I also host a web based API at ufxtract.comThe example URL in the slide shows how call for JSON respentation of the hCard on the slideshare profile we where just looking at
- For sites which are more about interaction outside of work you could be looking at a smaller subset.Dropping job title, company and the bio
- This is the last of the demos from the Ident Engine siteThe librarySearches for identities using the social graph APIIt then looks through the data overlays for information it can retrieve and builds a lifestream for that individualSo it has returned tweets, bookmarks and photo’s from flickrAll of this from entering a single URL
- This is a close up of the profile listing page. As you can see it has profiles for two people which is incorrect. This is because using inward links it is always possible for the social graph to pick up rogue relationshipsI trace this particular problem to 24ways sites, which was corrected. Once a error is in the Google search index it can take a very long time to get rid of itThese problems only happen rarely, but I have 3 options to fix the problem