Mashups and Open Apis- Ideas that worked for us…

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    Mashups and Open Apis- Ideas that worked for us… - Presentation Transcript

    1. Open APIs and Mashups © PreventionWeb 2007 www.preventionweb.net Ideas that worked for us… Sujit Mohanty UNISDR Secretariat, Geneva
    2. What we wanted to achieve? © PreventionWeb 2007 www.preventionweb.net
      • To facilitate collaboration in the disaster reduction community.
      • To avoid duplication of efforts in content collection and dissemination.
      • To provide our users a way to generate and share their own content.
      • To share content with other partners.
      • To overlay data on partners data sources to have an integrated experience.
    3. What’s open APIs and mashups?
      • OpenAPI (Application Programming Interface)
        • Sets of technologies that enable websites to interact with each other by using SOAP,REST, Javascript or any other web technology.
      • Mashups
        • A mashup is a website or web application that combines data from more than one source into a single integrated experience. Content used in mashups is typically sourced from a third party via a public interface or API .
              • Source: Wikipedia
    4. Examples of open APIs allowing mashups Screenshot from : www.programmableweb.com
      • www.programmableweb.com is a site which tracks APIs and mashups.
    5. More on APIs and mashups
      • http://www.programmableweb.com
      • http://www.webmashup.com/
      • http://www.mashupcamp.com/
      • http://www.apifinder.com/
      • http://mashable.com/
      • Want to provide an API? Try
      • http://www.dapper.net/
      • http://www.kapowtech.com/
    6. So what did we do?
      • Using a middleware technology or a SOAP API was complex for us.
      • Used HTTP (GET and POST) and XML to provide web services to our partners.
    7. Examples from PreventionWeb
      • Web services for:
        • Academic programmes database
        • Guided shared links- (service for Information Platform for Disaster Reduction)
        • Shared events calendar
        • Contacts management
    8. Print as PDF with CADRI branding Call to action for adding content Print as PDF with NSET branding Call to action for adding content Partners website HTTP+ XML HTTP+ XML By machine tagging UNISDR regional websites P W A P I Academic programmes in disaster risk reduction PreventionWeb CADRI site NSET, Nepal site
    9. Principles
      • Distributed content
      • Distributed call to action
      • Distributed output (own branded)
      • Machine tagging in API
    10. IPDR(Information Platform for Disaster Reduction) Guided links to all partner site Printed version Template for entry P W A P I Based on concept diagram of Craig Duncan, ISDR Secretariat, Geneva Other partners site ADRC, Japan site PreventionWeb NSET, Nepal site All partners* get links in their own style * Currently 30
    11. Questions?

    + Sujit MohantySujit Mohanty, 9 months ago

    custom

    745 views, 1 favs, 0 embeds more stats

    This presentation is on application of web2.0 techn more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 745
      • 745 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 22
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories