DiSo Dashboard Outline


Published on

Here's some ideas I've been formulating - for years

Published in: Technology
1 Comment
  • Manual trackback https://singpolyma.net/2009/10/diso-dashboards-and-the-future/
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

DiSo Dashboard Outline

  1. Outline format for DiSO Dashboards A format to tie the distributed web together
  2. Current focus of DiSO <ul><li>Find agreement on Activity stream feed formats </li></ul><ul><li>Verbs and Objects </li></ul><ul><li>Atom media extensions </li></ul><ul><li>Most major platforms lining up </li></ul>
  3. Feeds in a distributed world <ul><li>Activity stream reflects what a user or group is doing, with a unique item for each update </li></ul><ul><li>Output from a wide range of sources </li></ul><ul><li>User subscribes to these feeds – and aggregates them in a ‘dashboard’ or some other form of aggregator or lifestream mngr </li></ul><ul><li>These aggregators can be social networks or blogging platforms </li></ul>
  4. Dashboards can be a common notion that can connect users together <ul><li>All users will have some sort of Dashboard or centralized place for “all their stuff” </li></ul><ul><li>Dashboards can be: </li></ul><ul><ul><li>a start page (iGoogle, NetVibes, MyYahoo) </li></ul></ul><ul><ul><li>a social network (Facebook, MySpace) </li></ul></ul><ul><ul><li>a blog (Wordpress, TypePad) </li></ul></ul><ul><ul><li>a meta-aggregator (FriendFeed) </li></ul></ul><ul><ul><li>or practically anything else </li></ul></ul>
  5. Dashboards can represent…. <ul><li>An Individual </li></ul><ul><li>A Group </li></ul><ul><li>An Enterprise </li></ul><ul><li>An NGO or other kind of org or even a government agency </li></ul><ul><li>But it’s clearly a node in the user’s distributed web </li></ul><ul><li>Which can be used as a mechanism for collecting and sharing in the distributed web </li></ul>
  6. By connecting Dashboards together <ul><li>We can have a metaphor to connect any kind of app and/or web service to any kind of community and/or end-user </li></ul><ul><li>Each Dashboard would have an outline which could act as a data pivot point for connecting distributed systems together </li></ul>
  7. Each Dashboard’s outline <ul><li>Would represent the Dashboard’s info: </li></ul><ul><ul><li>User’s state and presence </li></ul></ul><ul><ul><li>Profile data and social info </li></ul></ul><ul><ul><li>Content and media </li></ul></ul><ul><ul><li>Feeds and access privileges </li></ul></ul><ul><ul><li>Modules and Configuration settings </li></ul></ul><ul><li>Could be ‘discovered’ </li></ul><ul><li>And would help facilitate: </li></ul><ul><ul><li>Dataportability </li></ul></ul><ul><ul><li>Interoperability </li></ul></ul><ul><ul><li>Shared Social Graphs </li></ul></ul><ul><ul><li>Distributed friending and messaging </li></ul></ul><ul><ul><li>Aggregated Groups and Communities </li></ul></ul><ul><ul><li>Other kinds of distributed ‘goodness’ </li></ul></ul>
  8. Outline format – the beginning <ul><li>Type of Dashboard </li></ul><ul><li>Feeds Subscriptions </li></ul><ul><li>Access privileges to those Feeds </li></ul><ul><ul><li>who gets ‘access to what’ in the feeds </li></ul></ul><ul><ul><li>the Dashboard’s access privs would regulate access to data objects, people, web pages or practically anything else – controlled by the user </li></ul></ul><ul><ul><li>sort of like Facebook Connect for us all </li></ul></ul>
  9. Outline format – and an ID Hub <ul><li>JanRain is offering something, which we (BBM) started building with PeopleAggregator </li></ul><ul><li>A collection of ID technologies called an ID Hub </li></ul><ul><li>ID Hubs would support both open and proprietary ID systems – and connect them together </li></ul>
  10. ID Hubs are important <ul><li>They support the Open Stack and help bring user centric IDs to all </li></ul><ul><li>But they also recognize the market leaders and are pragmatic for today’s installed base </li></ul>
  11. So every Dashboard will store a user’s ID Hub <ul><li>ID Hubs should be a part of the Dashboard’s outline </li></ul><ul><li>Each ID system would be kept </li></ul><ul><li>track of </li></ul><ul><li>And an aggregated social graph </li></ul><ul><li>would be developed </li></ul>
  12. And every Dashboard should also help facilitate distributed Friending <ul><li>Distributed Friending will store each person’s set of Friends on their own ‘dashboard’ </li></ul><ul><li>Sort of like Google Friend Connect – only WE get a copy of our own social graph, not Google </li></ul>
  13. 4 different buttons, same technology <ul><li>Distributed Friending can facilitate different kinds of social relationships, at the same time </li></ul>
  14. Outline format – and Social info <ul><li>A full range of Social info would </li></ul><ul><li>be stored in the Dashboard’s Outline </li></ul><ul><li>In addition to distributed friending </li></ul><ul><li>What Groups or Networks they’re </li></ul><ul><li>a member of </li></ul><ul><li>What their Favs are </li></ul><ul><li>What their Bookmarks are </li></ul><ul><li>All sorts of info about the user and other people </li></ul>
  15. Outline format – and Content <ul><li>All of the User’s Content would be </li></ul><ul><li>represented in their Dashboard’s </li></ul><ul><li>Outline </li></ul><ul><li>All kinds of text posts, notes, Twits </li></ul><ul><li>and Messages </li></ul><ul><li>Comments </li></ul><ul><li>Reviews and Events </li></ul><ul><li>Testimonials and Shoutouts </li></ul><ul><li>Connected to the Dashboard’s Access controls </li></ul>
  16. Outline format – and Media <ul><li>And all sorts of media, both </li></ul><ul><li>payloads and pointers </li></ul><ul><li>With collections of media item </li></ul><ul><li>- as well </li></ul><ul><ul><li>Playlists of Video and Audio </li></ul></ul><ul><ul><li>Albums and Galleries of Images </li></ul></ul><ul><li>Connected to the Dashboard’s </li></ul><ul><li>Access controls </li></ul>
  17. Outline format – Modules & Widgets <ul><li>The Dashboard’s Outline would also </li></ul><ul><li>represent what modules, widgets </li></ul><ul><li>and code were present </li></ul><ul><li>What Flash and Ajax/Javascript </li></ul><ul><li>Widgets are included </li></ul><ul><li>What platform specific ‘Gadgets’ </li></ul><ul><li>What OpenSocial Apps and </li></ul><ul><li>Facebook apps </li></ul><ul><li>What code segments, Java apps, </li></ul><ul><li>ActiveX controls </li></ul>
  18. Outline format – UI Elements <ul><li>And what UI Elements were </li></ul><ul><li>‘ surfaced’ to the users </li></ul><ul><li>All of the Elements which make </li></ul><ul><li>up the Dashboard’s UI </li></ul>
  19. Outline format – Dashboard Configuration <ul><li>And finally what: </li></ul><ul><ul><li>Those UI settings are </li></ul></ul><ul><ul><li>Which web services and </li></ul></ul><ul><ul><li>APIs are supported </li></ul></ul><ul><ul><li>What Templates are being </li></ul></ul><ul><ul><li>utilized </li></ul></ul><ul><ul><li>What meta-data – about </li></ul></ul><ul><ul><li>the entire Dashboard </li></ul></ul><ul><ul><li>What Devices are supported </li></ul></ul><ul><ul><li>Geo information </li></ul></ul><ul><ul><li>Directories of everything; </li></ul></ul><ul><ul><li>where everything is </li></ul></ul>
  20. All in one Outline <ul><li>By combining all of this distributed data – in one outline, a wide range of inter-connectivity can be facilitated – with one format </li></ul><ul><li>The outline serves as an aggregation of standard info – accessible the same way across a wide range of dashboards </li></ul><ul><li>Not necessarily a file or page tags (maybe both) </li></ul><ul><li>Can/should be OPML and XOXO compatible too! </li></ul><ul><li>And created/edited in a new kind of tool </li></ul>
  21. DiSO Dashboard