论文信息 - Why Experimental Interfaces Should Include an Application Programming Interface

Why Experimental Interfaces Should Include an Application Programming Interface

An Application Programming Interface (API) can serve as a mechanism for separating interface concerns on the one hand from data and processing on the other, allowing for easier implementation of alternative human-computer interfaces. The API can also be used as a sounding board for ideas about what an interface should and should not accomplish. Our discussion will take as its case study our recent work in designing experimental interfaces for the visual construction of Boolean queries, for a project we have previously called the Mandala Browser.

[1] Li-Te Cheng,et al. Sometimes you need to see through walls: a field study of application programming interfaces , 2004, CSCW.

[2] Jan H. Spyridakis,et al. API documentation and software community values: a survey of open-source API documentation , 2013, SIGDOC '13.

[3] Harald Reiterer,et al. The concept maps method as a tool to evaluate the usability of APIs , 2011, CHI.

[4] Joshua J. Bloch. How to design a good API and why it matters , 2006, OOPSLA '06.

[5] Hewijin Christine Jiau,et al. Facing up to the inequality of crowdsourced API documentation , 2012, SOEN.

[6] Umer Farooq,et al. API peer reviews: a method for evaluating usability of application programming interfaces , 2010, CSCW '10.

[7] Stéfan Sinclair,et al. Visual Interface Design for Digital Cultural Heritage: A Guide to Rich-Prospect Browsing , 2011 .

[8] E. Stroulia,et al. The Landscape of Service-Oriented Systems: A Research Perspective , 2007, International Workshop on Systems Development in SOA Environments (SDSOA'07: ICSE Workshops 2007).

[9] Sho-Huan Simon Tung,et al. Merging interactive, modular, and object-oriented programming , 1992 .

[10] V. Ganapathy,et al. Automatic discovery of API-level exploits , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..