This is the intro deck I used to frame my standard talk on web hooks around mashups. After these slides, continue with <a href="http://www.slideshare.net/progrium/web-hooks-and-the-programmable-world-of-tomorrow-presentation">this slideshow</a>

1. Beyond Mashups
this talk is basically a talk i give about web hooks, but in the context of mashups.
the idea is you’re all familiar with mashup opportunity, made possible by APIs...
web hooks are like the other side of APIs that will open up a new kind of opportunity

2. Mashup
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

3. Datasource
Mashup
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

4. Datasource
Mashup
Presentation
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

5. Datasource
Magic
Mashup
Presentation
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

6. Datasource
Magic
Mashup
Presentation Widget
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

7. Datasource
Magic
Mashup
Presentation Widget
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

8. Datasource
Magic
Mashup
Presentation Widget
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

9. Datasource
Magic
Mashup
Presentation Widget
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

10. Datasource
Magic
Mashup
Presentation Widget
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

11. Datasource
Magic
Mashup
Presentation Widget?
this is my crude example of mashups. a datasource or two, perhaps a presentation tool,
some magic glue... and sometimes packaged up as a widget or embeddedable something.
housing maps as an example. it’s mostly about read-only or query based functionality.

12. Mashup
Web Service A Web Service B
but this model is interesting in that it’s like combining web services to make something new

13. Web Service C
Web Service A Web Service B
which is really yet another, now third web service.

14. Aggregation
Web Service C
Web Service A Web Service B
this is aggregation. and while it’s obviously valuable, there’s another idea waiting
to be appreciated...

15. Integration
Web Service A Web Service B
integration. just make my existing services *work together how i want*

16. Integration
Make my existing tools work together
to become more than the sum of the parts.
Web Service A Web Service B
integration. just make my existing services *work together how i want*

17. The Programmable Web is a misnomer.
i believe in the programmable web. i want it, we have a glimpse of it.
but we don’t have it. not really.

18. It should be called the Programmatic Web.
instead, API’s give us *programmatic* access to their services.
we cannot “program” them, change them or customize them,
or truly *compose* them like we’ve envisioned with the pipes metaphor

19. WEB HOOKS
and the
Programmable World of Tomorrow
Jeff Lindsay
enter web hooks.
please see other slides...