Advertisement

The Interactive API (iAPI)

  • Florian Daniel
  • Andrea Furlan
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8295)

Abstract

The claim of this paper is that reuse on the Web – if sensibly facilitated – can be achieved in a much more intuitive and efficient fashion than today. The idea is to invert the current perspective on reuse by moving away from programmer-oriented artifacts, such as APIs, web services and data feeds, and focusing on user-oriented artifacts, i.e., graphical user interfaces (UIs). The paper defines a new kind of API, the interactive API (iAPI), which reconciles the intuitiveness of interactive UIs with the power of programmable APIs and enables (i) programmatic access to UIs and (ii) interactive, live programming. The paper discusses use cases and implementation options and lays the foundation for UI-oriented computing as a discipline.

Keywords

Service Composition Programmatic Access Implementation Option Graphical Control Browser Window 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. 1.
    Abdelnur, A., Hepper, S.: Java Portlet Specification, Version 1.0. Technical Report JSR 168, Sun Microsystems, Inc. (October 2003), http://download.oracle.com/otndocs/jcp/PORTLET_1.0-FR-SPEC-G-F/
  2. 2.
    Alonso, G., Casati, F., Kuno, H., Machiraju, V.: Web Services: Concepts, Architectures, and Applications. Springer (2003)Google Scholar
  3. 3.
    Dix, A., Finlay, J., Abowd, G., Beale, R.: Human-Computer Interaction, 3rd edn. Prentice Hall (2004)Google Scholar
  4. 4.
    Fielding, R.: Architectural Styles and the Design of Network-based Software Architectures. Ph.d. dissertation, University of California, Irvine (2007)Google Scholar
  5. 5.
    Jordan, D., Evdemon, J.: Web Services Business Process Execution Language Version 2.0. Oasis standard, OASIS (April 2007), http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
  6. 6.
    Li, P., Wohlstadter, E.: View-based maintenance of graphical user interfaces. In: AOSD, pp. 156–167 (2008)Google Scholar
  7. 7.
    Namoun, A., Nestler, T., Angeli, A.D.: Service Composition for Non-programmers: Prospects, Problems, and Design Recommendations. In: ECOWS, pp. 123–130 (2010)Google Scholar
  8. 8.
    Nottingham, M., Sayre, R.: The Atom Syndication Format (December 2005), http://www.ietf.org/rfc/rfc4287.txt
  9. 9.
    RSS Advisory Board. RSS 2.0 Specification (2009), http://www.rssboard.org/rss-specification
  10. 10.
    Web Application Working Group. Widgets Family of Specifications (May 2012)Google Scholar
  11. 11.
    Yu, J., Benatallah, B., Casati, F., Daniel, F.: Understanding Mashup Development. IEEE Internet Computing 12(5), 44–52 (2008)CrossRefGoogle Scholar
  12. 12.
    Yu, J., Benatallah, B., Saint-Paul, R., Casati, F., Daniel, F., Matera, M.: A Framework for Rapid Integration of Presentation Components. In: WWW, pp. 923–932. ACM Press (May 2007)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2013

Authors and Affiliations

  • Florian Daniel
    • 1
  • Andrea Furlan
    • 1
  1. 1.University of TrentoTrentoItaly

Personalised recommendations