Go back to the EiToolkit page.

EIToolkit Workshop (EIToolkit'05)

The Research Group Embedded Interaction organized a meeting for the EIToolkit in early December 2005. People from different backgrounds using a variety of technolgies and input and output methods came together and derived requirements and features for a common toolkit.

Results of the workshop will be presented here soon.

Please direct questions, comments and recommendations to PaulHolleis

Time and Place

Date: 07. - 09. December 2005 (Wednesday - Friday)

Time: Wed. 13:00 - 19:00, Thu 9:00 - 19:00, Fri 9:00 - 17:00

The workshop took place at the Ludwig-Maximilians-Universität München in Munich, Germany. See, e.g., http://www.hcilab.org/contact.htm for more information on how to get there.

LFE Medieninformatik
Room 107, 1st floor
Amalienstr. 17
80333 Munich


The meeting will start with an introduction to the lab. Once most of the participants have arrived, there will some some short talks on the current architecture and implementation of the toolkit as well as issues we already identified and other existing approaches and related work.

  • Wednesday 07.12:
    • 12:00: Welcome, "Registration" and Lunch smile
    • 14:00: Introduction to EI group and lab
    • 14:20: Current status and ideas
    • 14:45: Presentation of group Fluidum and instrumented room
    • 15:00: Related work and similar approaches
    • 15:30: Introduction to experiences of the participants
    • 16:30: Coffee Break
    • 17:00: Discussions and brainstorming on desired functionality
    • 18:15: End

  • Thursday 08.12:
    • 9:00: Summary of the results of the day before
    • 9:10: Resume discussion on functionality and issues
    • 9:30: Discussions on selected subjects, especially on requirements found by the group of Nicky Kern
    • 10:30: Further discussion and presentation of results
    • 11:00: Preliminary decisions on further steps for those who have to leave
    • 12:15: Lunch
    • 14:00: Reiteration on problems
    • 16:40: Coffee Break
    • 17:00: Documentation and discussion of issues found

  • Friday 09.12:
    • 9:00: Summary and presentation of the results of the day before
    • 9:10: Discussion on technologies and methods that need to be incorporated
    • 10:00: Detailed discussion on work related to information exchange and their protocols
    • 12:00: Lunch
    • 14:00: Further ideas for streaming etc.
    • 15:45: Coffee Break
    • 16:00: Plan further steps, distribute software
    • 17:00: End

Social Events

Although the whole workshop was a social event :-), we tried to have all enjoy their stay in Munich. We went to the famous christmas market and had dinner in two typical bavarian restaurants, including the famous Augustinerkeller.


The main goal of the workshop was to (further) develop the architecture of the EIToolkit. This included designing central components like stub managers (or deciding that they are not needed) as well as questions regarding the protocols that should be used.


  • Paul Holleis (Embedded Interaction, University of Munich)
  • Matthias Kranz (Embedded Interaction, University of Munich)
  • Albrecht Schmidt (Embedded Interaction, University of Munich)

  • Alexis Maldonado (Technical University of Munich)
  • Christian Decker (University of Karlsruhe)
  • Christian Metzger (Information Management, ETH Zurich)
  • David Molyneaux (University of Lancaster)
  • Martin Strohbach (University of Lancaster)
  • Michael Beetz (Technical University of Munich)
  • Michael Rohs (Deutsche Telekom Laboratories)
  • Nicky Kern (University of Darmstadt)
  • Philipp Scholl (University of Karlsruhe)
  • Radu Bogdan Rusu (Technical University of Munich)
  • Tam Huynh (University of Darmstadt)
  • Till Riedel (University of Karlsruhe)
  • Ulrich Steinhoff (University of Darmstadt)
  • Yoosoo Oh (GIST, U-VR Lab, Visiting Researcher in Munich)

Some Issues

This list is meant to be a set of thoughts that might be discussed in the meetings and afterwards. Please add any issues that come to your mind.

Software Design

  • should stubs be self-contained applications? does it make sense to start a stub without having an application? Could the application initiate the start of the stub? -> we can include a startup file (main.cpp) that can be used to start the stub, leaving the loose coupling between stub and rest of the system intact.


  • Querying for stubs / applications: return only local resources? Everything everywhere?

Security / Reliabilty

  • Encryption
  • Logging
  • Authentification


  • Sending a command, should there be an acknowlegement / confirmation?
  • Exception / Error handling system

-- PaulHolleis - 28 Sep 2005
Topic attachments
I Attachment Action Size Date Who Comment
clj4650pswin2kxp2003.exeexe clj4650pswin2kxp2003.exe manage 10851.6 K 07 Dec 2005 - 09:33 RainerFink Printer Driver: HP Color LaserJet 4650 dtn, Windows XP, PostScript, English
lj2300pswin2kxp2003.exeexe lj2300pswin2kxp2003.exe manage 10771.5 K 07 Dec 2005 - 09:34 RainerFink Printer Driver: HP LaserJet 2300 dn, Windows XP, PostScript, English
lj4200pswin2kxp.exeexe lj4200pswin2kxp.exe manage 10759.8 K 07 Dec 2005 - 09:31 RainerFink Printer Driver: HP LaserJet 4200 dtn, Windows XP, PostScript, English
o578en.exeexe o578en.exe manage 27016.0 K 07 Dec 2005 - 09:36 RainerFink Printer Driver: Canon iR2270, Windows XP, PostScript, English
updpswin2kxp2003_32-en.exeexe updpswin2kxp2003_32-en.exe manage 7559.9 K 07 Dec 2005 - 09:35 RainerFink Printer Driver: HP Universal Printer Driver, Windows XP, English
Topic revision: r19 - 03 Mar 2008, PaulHolleis
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Medieninformatik-Wiki? Send feedback