The Live Web #SCITDA11 Keynote

Editor's Notes

• #2: \n
• #3: Web is an amazing place\n\n
• #4: \n
• #5: Life events. \nbusiness.utah.gov\n
• #6: Life events, not agencies\nOne place, not multiple places\nAdd payment and personal information only once\nSecure and trustworthy environment\n“online” not “in line”\n
• #7: Life events, not agencies\nOne place, not multiple places\nAdd payment and personal information only once\nSecure and trustworthy environment\n“online” not “in line”\n
• #8: Life events, not agencies\nOne place, not multiple places\nAdd payment and personal information only once\nSecure and trustworthy environment\n“online” not “in line”\n
• #9: \n
• #10: Tightly coupled vs. loosely coupled \nNumber of connections and interactions is staggering\nWhy many home automation plays have failed to take hold\n
• #11: Adding a network changes anything\n
• #12: Do demo here!!!\n
• #13: \n
• #14: \n
• #15: book on wishlist or maybe you just looked at it. \n
• #16: book on wishlist or maybe you just looked at it. \n
• #17: Have your phone guide you to the empty parking slot nearest your desitnation\n
• #18: Food that notifies you when it’s about to go out of date\n
• #19: \n
• #20: I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
• #21: I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
• #22: I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
• #23: I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
• #24: I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
• #25: I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
• #26: \n
• #27: Very different than tightly coupled interactions\n
• #28: Very different than tightly coupled interactions\n
• #29: Very different than tightly coupled interactions\n
• #30: Very different than tightly coupled interactions\n
• #31: Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
• #32: Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
• #33: Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
• #34: Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
• #35: \n
• #36: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #37: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #38: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #39: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #40: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #41: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #42: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #43: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #44: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #45: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #46: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #47: On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
• #48: The most important feature for this discussion is that each Web site is a silo. The location metaphor works fine when what you want to do is confined to that silo. But what happens when you need information from multiple places to accomplish your task?\n
• #49: \n
• #50: \n
• #51: \n
• #52: Fortunately there’s a way to make it easier. \nThe best apps will not be mere clients for a single API. \n
• #53: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #54: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #55: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #56: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #57: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #58: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #59: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #60: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #61: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #62: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #63: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #64: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #65: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #66: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #67: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #68: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #69: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #70: In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
• #71: \n
• #72: \n
• #73: \n
• #74: when you follow someone on twitter, you are creating a static query against the river of tweets\nwe’ve create a rule language, KRL, to work in this new model. \nTell me when someone mentions my company on Twitter. \nTell me when someone checks into the same place I am.\nTell me when one of my Facebook friends posts an update on their blog.\nTell me when someone calls my customer service line after visiting the customer service page on my company’s Web site.\n \n
• #75: \n
• #76: A platform for building Live Web applications would have certain properties. \n
• #77: A platform for building Live Web applications would have certain properties. \n
• #78: A platform for building Live Web applications would have certain properties. \n
• #79: A platform for building Live Web applications would have certain properties. \n
• #80: A platform for building Live Web applications would have certain properties. \n
• #81: \n
• #82: \n
• #83: \n
• #84: \n
• #85: \n
• #86: \n
• #87: \n
• #88: \n
• #89: \n
• #90: 1.) Simpler schema for an event than a request (more standard)\n2.) Generators don’t know who’ll process an event\n3.) No need for specific processing instructions in the event\n4.) Adding and removing components requires less overall coordination\n
• #91: \n
• #92: Open source platform for processing events raised by endpoints and taking action based on results\n
• #93: \n
• #94: call out the abstract in this expression\n
• #95: \n
• #96: \n
• #97: \n
• #98: \n
• #99: \n
• #100: \n
• #101: \n
• #102: \n
• #103: \n
• #104: Send me email for access to the book. \n\n
• #105: \n
• #106: \n
• #107: Influencers\nDevelopers\nPartners\n\n