![teaching_assistants =
[{"name":"Anne",
"phone":"801362XXXX",
"eci":"072a3730-2e9a-012f-d2da-00163e411455",
"calendar":"http://www.google.com/calendar/..."
},
{"name":"John",
"phone":"801602XXXX",
"eci":"fc435280-2b60-012f-cfeb-00163e411455",
"calendar":"http://www.google.com/calendar/..."
}
...
];](https://image.slidesharecdn.com/personaleventnetworks-busintrodatavenucopy-120808122056-phpapp02/75/Personal-Cloud-Operating-Systems-110-2048.jpg)
Uploaded byPhil Windley
Personal Cloud Operating Systems
The document discusses the concept of personal clouds as an operating system that reshapes how individuals interact with technology, services, and each other. It highlights the evolution of communications, the need for decentralized systems, and the role of event-driven APIs in personal cloud integration. Additionally, the document outlines the vision for Kynetx as a facilitator of personal cloud networks, emphasizing the importance of partnerships and application development for widespread adoption.
More Related Content
Similar to Personal Cloud Operating Systems
Personal Cloud Operating Systems
- 1. Personal Clouds Phil Windley Co-founder& CTO Kynetx
- 3. We’re building an operating system for your personal cloud
- 5. Personal Event Networks are an Operating System for your Personal Cloud
- 7.
- 8. Cloud appliances vs general-purpose computing platforms
- 9. Personal Clouds changehow we…
- 10. Personal Clouds changehow we… relate to everything in our lives
- 11. Personal Clouds changehow we… relate to everything in our lives buy & sell products & services
- 12. Personal Clouds changehow we… relate to everything in our lives buy & sell products & services communicate with each other
- 13. A Brief (and mostlywrong) History of the Web
- 14. Wired Magazine, 1995: “Webis like TV, only better”
- 16.
- 17. 1994 2000
- 18. 1994 2000 2004
- 19. 1994 2000 2004 2010
- 20. Five Trends Shapingthe Future http://itc.conversationsnetwork.org/shows/detail4930.html
- 21. Five Trends Shapingthe Future pages ➠ streams http://itc.conversationsnetwork.org/shows/detail4930.html
- 22. Five Trends Shapingthe Future pages ➠ streams PC ➠ clouds http://itc.conversationsnetwork.org/shows/detail4930.html
- 23. Five Trends Shapingthe Future pages ➠ streams PC ➠ clouds html ➠ json http://itc.conversationsnetwork.org/shows/detail4930.html
- 24. Five Trends Shapingthe Future pages ➠ streams PC ➠ clouds html ➠ json today ➠ now http://itc.conversationsnetwork.org/shows/detail4930.html
- 25. Five Trends Shapingthe Future pages ➠ streams PC ➠ clouds html ➠ json today ➠ now big data ➠ little data http://itc.conversationsnetwork.org/shows/detail4930.html
- 26. Big, crude, & manual...
- 27. Big, Small, crude, measured, & ➠ & manual... automatic
- 28.
- 29.
- 30. Changing how we relate to things
- 31. Social Products &Services
- 32. Social Products &Services
- 33.
- 38.
- 39.
- 40. ANY : ANY 1:1
- 41. ANY : ANY personalevent network
- 43. GE Apps Personal Event Network Data Owner
- 44. How do weget there?
- 45.
- 51.
- 52. Events make thephone ring
- 53. Semantic encapsulation & Loose coupling
- 54. Changing how we buy & sell
- 55. AOL MCI CompuServe
- 57.
- 58.
- 59. Task: Build a business allowingpeople to order flowers
- 62. how can webuild a network?
- 63. Customer’s Cloud shop data customer
- 64. Customer’s Cloud Flower Shop’s Cloud shop delivery rfq data customer flowerShops Flower shop
- 65. Customer’s Cloud Flower Shop’s Cloud protocol shop delivery rfq data customer flowerShops Flower shop
- 66. Customer’s Cloud Flower Shop’s Cloud shop delivery rfq data customer flowerShops Flower shop
- 67. Trust Network reputation brokerage id verification Customer’s Cloud Flower Shop’s Cloud shop delivery rfq data customer flowerShops Flower shop
- 68. Trust Network reputation brokerage id verification Customer’s Cloud Flower Shop’s Cloud protocol shop delivery rfq data customer flowerShops Flower shop
- 69. A protocol formarket interaction
- 70. ways scale better than places
- 71. VRM The Power ofIntent
- 72. Changing how we communicate
- 73. Car Twilio Tim's Personal Event Network Apps Flower Shop Phone
- 74. Independently • manage, • permission, and • respond to notifications, alerts, & reminders
- 75. Personal Cloud channels replace email & social networks in many applications
- 76. The Evolution ofCommunications
- 77. centralized The Evolution ofCommunications
- 78. centralized decentralized The Evolution of Communications
- 79. centralized decentralized single AOL mail email channel (1990) (2000) The Evolution of Communications
- 80. centralized decentralized single AOL mail email channel (1990) (2000) The Evolution of Communications
- 81. centralized decentralized single AOL mail email channel (1990) (2000) The Evolution of Communications
- 82. centralized decentralized single AOL mail email channel (1990) (2000) multiple Facebook personal clouds channel (2009) (2014) The Evolution of Communications
- 83. centralized decentralized single AOL mail email channel (1990) (2000) multiple Facebook personal clouds channel (2009) (2014) The Evolution of Communications
- 84. centralized decentralized single AOL mail email channel (1990) (2000) multiple Facebook personal clouds channel (2009) (2014) The Evolution of Communications
- 85.
- 86. Kinetic Rule Language: Ruleslink events to actions
- 87. Kinetic Rule Language: Ruleslink events to actions SQL for Dynamic Streams
- 88. select when pageview “/support/(d+)” setting(issue_number) before (phone inboundcall or email received subj.match( re/issue_number/) )
- 89. select when pageview “/support/(d+)” 1 setting(issue_number) before (phone inboundcall or 2 email received 3 subj.match( re/issue_number/) )
- 90. select when pageview “/support/(d+)” 1 setting(issue_number) before (phone inboundcall or 2 email received 3 subj.match( re/issue_number/) )
- 91. Kinetic Rule Engine: Makes events & data personal and contextual
- 93.
- 94.
- 95.
- 97. Kinetic Data Engine: Uses XDI to provide location independence & semantic data management
- 98. user = get_user_inum(); user_work_phone= xri:#{user}+work$!(+tel)
- 99. phone: (801)555-1212 xri:=windley+work$!(+tel) xri:(https://xdi.fb.com/fulling)+work$!(+tel) cell: +1.801.555.1213 xri:(mailto:wells@kynetx.com)+work$!(+tel) mobile: 801-555-1214
- 100. Personal Cloud: Linksowners to apps, their data, & each other
- 101.
- 102.
- 103. Personal Cloud Federationfor TAs
- 104. Class Cloud On-call TADispatcher Twilio Personal Cloud Federation for TAs
- 105. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud On Call: Demo Notify On-call TA Dispatcher Twilio calendar pdm Personal Cloud Federation for TAs
- 106. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo Notify On-call TA Dispatcher Twilio calendar pdm Personal Cloud Federation for TAs
- 107. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo Notify On-call TA Dispatcher Twilio calendar pdm SMS Student Phone Personal Cloud Federation for TAs
- 108. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo Notify On-call TA Dispatcher Twilio schedule:inquiry calendar pdm SMS Student Phone Personal Cloud Federation for TAs
- 109. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo Notify On-call TA Dispatcher Twilio schedule:inquiry calendar pdm SMS SMS Student Phone TAs' Phones Personal Cloud Federation for TAs
- 110. teaching_assistants = [{"name":"Anne", "phone":"801362XXXX", "eci":"072a3730-2e9a-012f-d2da-00163e411455", "calendar":"http://www.google.com/calendar/..." }, {"name":"John", "phone":"801602XXXX", "eci":"fc435280-2b60-012f-cfeb-00163e411455", "calendar":"http://www.google.com/calendar/..." } ... ];
- 111. rule dispatch { select when schedule inquiry foreach teaching_assistants setting (ta) event:send(ta,"schedule","inquiry") with attrs = {"from" : event:attr("From"), "message": event:attr("Body"), "code": math:random(99); }; always { raise explicit event subscribers_notified on final } }
- 112. rule dispatch { select when schedule inquiry foreach teaching_assistants setting (ta) event:send(ta,"schedule","inquiry") with attrs = {"from" : event:attr("From"), "message": event:attr("Body"), "code": math:random(99); }; always { raise explicit event subscribers_notified on final } }
- 113. rule dispatch { select when schedule inquiry foreach teaching_assistants setting (ta) event:send(ta,"schedule","inquiry") with attrs = {"from" : event:attr("From"), "message": event:attr("Body"), "code": math:random(99); }; always { raise explicit event subscribers_notified on final } }
- 114. Data Other Stores Personal Data Contacts Service Configuration Notifications Management Authorization Calendars Service XDI Servers XDI Servers XDI Servers Subscription To Do & Service Reminders CloudOS Intentcasting Service XDI Client Notification Forever Service APIs Dashboard Rules Kynetx Engine Support Personal Cloud OS Mongo Libraries Services & Applications User Space Kernel Space
- 115. Kynetx Roadmap KBX Events Rules Engine 2007 2009 2011
- 116. Kynetx Roadmap Personal Event Networks KBX Events Rules Engine 2007 2009 2011 now
- 117. Kynetx Roadmap CloudOS Services Personal Event Networks KBX Events Rules Engine 2007 2009 2011 now next
- 118. Kynetx Roadmap Applications CloudOS Services Personal Event Networks KBX Events Rules Engine 2007 2009 2011 now next future
- 119.
- 120. What we need... •Partners to implement Evented APIs
- 121. What we need... •Partners to implement Evented APIs •Partners to help define services
- 122. What we need... •Partners to implement Evented APIs •Partners to help define services •Application developers
- 123. What we need... •Partners to implement Evented APIs •Partners to help define services •Application developers •Acceleration ($$$)
- 124. Kynetx is an OperatingSystem for your Personal Cloud
- 125. Personal Clouds changehow we…
- 126. Personal Clouds changehow we… relate to everything in our lives
- 127. Personal Clouds changehow we… relate to everything in our lives buy & sell products & services
- 128. Personal Clouds changehow we… relate to everything in our lives buy & sell products & services communicate with each other
- 129. Personal Cloud WhitePapers http://windley.com/liveweb
- 130. Personal Cloud Operating Systems ? Contact info: pjw@kynetx.com www.windley.com @windley
Editor's Notes
- #2 \n
- #3 \n
- #4 \n
- #5 \n
- #6 a personal event network is like an OS for your personal cloud. You can install apps to customize it for your purpose, it can store and manage your personal data, and it provides generalized services through APIs that any app can take advantage of.\n
- #7 When we talk about “personal clouds” these logos spring to mind. \nEach is trying to create a specific set of personal services for individuals\nRobert Scoble calls this the “game of games” and it’s huge\n
- #8 For this to happen, personal clouds need an OS. \n
- #9 \n
- #10 \n
- #11 \n
- #12 \n
- #13 Tell story about CD ROMs. 500 Channels\n
- #14 \n
- #15 \n
- #16 \n
- #17 \n
- #18 \n
- #19 \n
- #20 \n
- #21 “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
- #22 “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
- #23 “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
- #24 “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
- #25 “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
- #26 Alternate view from Brian Vellmere\n
- #27 \n
- #28 Our response to these trends and how to make the most of them is the personal cloud.\nLike the Web, personal clouds aren’t a specific technology, but a concept growing out of standards and methods of practice. \n
- #29 Transformational value. Why does this matter? \nCloud platforms are helping us do more with less. We have a vision of PENs impacting the most fundamental relationships in our lives. This future world is even better than anything we’ve imagined. \n
- #30 \n
- #31 \n
- #32 Everything is connected; producing streams of data. \nThey’re everywhere and always on. \nThey’re talking to their manufacturers, not to us.\n
- #33 \n
- #34 \n
- #35 \n
- #36 \n
- #37 \n
- #38 \n
- #39 \n
- #40 \n
- #41 \n
- #42 \n
- #43 \n
- #44 \n
- #45 \n
- #46 \n
- #47 \n
- #48 \n
- #49 \n
- #50 \n
- #51 \n
- #52 \n
- #53 \n
- #54 \n
- #55 \n
- #56 \n
- #57 \n
- #58 \n
- #59 Current state\nManaging connected devices as a manufacturere.\nMy Tivo recently updated its software…\nGE is building dishwashers that can reflash their firmware\n
- #60 next state\nConnected devices are great, but I want them in my network too. \nOne place to manage them. \nMy GE air conditioner and Toyota electric car negotiate when the car can charge\n
- #61 One answer might be APIs. But there’s a problem with relying on APIs to solve this problem. \n
- #62 OK, this may sound nice, but where are we today? How do we get to this world?\nWe live in a world of APIs that power apps. \nLet me show you what I’m thinking...\n
- #63 \n
- #64 Most modern web sites are like pools of data that is relatively static. An API is like a pump that we can use to get water out of the pool. \nThis is limited: bound to the data that’s there, the update schedule\nWorks today, but the trend is to real-time. \n
- #65 Challenge: doesn’t call you back.\nIt’s one-way. \n
- #66 Twitter as an example\nTalk later about how we make creating those queries easily. declarative, powerful\nReal-time benefits: \n
- #67 Events say something happened…\nComputers have used interrupts since the 1960’s. \nEvents allow for asynchronous interaction\nIt’s only natural that our APIs will be evented as well. \nSome APIs are already evented, we want more; built a standard\n
- #68 \n
- #69 \n
- #70 \n
- #71 Remember what email was like in 1990? Several large email providers dominated the landscape. If I wanted to send email to you, it would work as long as we both used the same system. \n
- #72 A protocol called SMTP provided any email systems with a way to interact with each other. Networks are built from ways of interacting. \n
- #73 For email, place surrendered to way. The result was a blossoming of opportunities for people and businesses. \n
- #74 Suppose I give you a task...\n
- #75 Our default, knee jerk reaction is to build a web site, but that is “place” thinking...not “way” thinking. \n
- #76 Website approach to online commerce places every interaction in vendor-made silo\nThese silos trap context, making it hard to link experiences. \n
- #77 How could we build an ecommerce network instead of just a collection of independent ecommerce sites?\n
- #78 For this to work, we need a personal cloud that acts for the customer and a vendor cloud that acts for the flower shop. They use an ecommerce protocol to interact. This is a way to buy flowers...or anything else...rather than a place. \n
- #79 For this to work, we need a personal cloud that acts for the customer and a vendor cloud that acts for the flower shop. They use an ecommerce protocol to interact. This is a way to buy flowers...or anything else...rather than a place. \n
- #80 This simple system can be made more flexible by creating networks that allow for discovery and trusted interaction.\n
- #81 This simple system can be made more flexible by creating networks that allow for discovery and trusted interaction.\n
- #82 Use by one leads to usage by others. \nBetter linking of applications...imagine customers ordering via their PEN. \nPEN creates protocol for market interactions\n
- #83 The reason to use protocols and networks is because they scale better than places. Recall the email example from the beginning of my talk. We can build networks of interaction for ecommerce that scale better and consequently provide better service for customers and enhanced revenue for merchants. \n
- #84 Demand chains\nCustomers have a lot of relevant retail data that they’ll share in a conversation\nBetter information leads to better markets.\nRFQs, power adapter\n
- #85 \n
- #86 To see how this works, imagine a guy named Tim who has a personal event network. \nTim’s personal event network has a number of apps installed. It’s also is listening on many event channels. These channels are carrying events about everything from Tim’s phone and appliances to merchants he frequents.\nTim has relationships with REI and a local flowershop. They both have separate channels into Tim’s personal event network. Consequently, Tim can\n\n
- #87 \n
- #88 \n
- #89 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #90 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #91 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #92 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #93 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #94 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #95 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #96 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #97 I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
- #98 \n
- #99 KRL is the static query to the dynamic stream of events...\n
- #100 We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
- #101 We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
- #102 Open source\n
- #103 \n
- #104 \n
- #105 \n
- #106 \n
- #107 Open source\nGlobally addressable data with semantics, fine-grained permissioning\ndata exchange\nOASIS TC\nFunded development\n
- #108 \n
- #109 \n
- #110 \n
- #111 \n
- #112 describe scenarion\n
- #113 \n
- #114 \n
- #115 \n
- #116 \n
- #117 \n
- #118 \n
- #119 \n
- #120 We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
- #121 We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
- #122 We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
- #123 I’ve been experimenting this all these ideas, building out systems based on events and personal event networks.\nHere’s what I’ve built and why\nBusiness model\nBottom row is open source\n
- #124 Rules Engine\nEvents\nKBX\nSky\nNotifications/reminders\n
- #125 Rules Engine\nEvents\nKBX\nSky\nNotifications/reminders\n
- #126 Rules Engine\nEvents\nKBX\nSky\nNotifications/reminders\n
- #127 We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
- #128 We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
- #129 We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
- #130 We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
- #131 a personal event network is like an OS for your personal cloud. You can install apps to customize it for your purpose, it can store and manage your personal data, and it provides generalized services through APIs that any app can take advantage of.\nCloud appliances vs general-purpose computing platforms???\n
- #132 \n
- #133 \n
- #134 \n
- #135 \n
- #136 \n
- #137 \n