<$BlogRSDUrl$>

Every Friday I pick a paper from the ACM Digital Library that is found by the search term +connected +2005 +"mobile device" +"user interface", and write a brief discussion of it. Why? Because it makes me actually read them.

virtual journal club: "Connected Mobile Devices UI"
Friday, February 04, 2005
A service architecture for mobile teamwork 
Link

Engin Kirda Technical University of Vienna, Argentinierstrasse 8/184-1, 1040 Vienna / Austria
Pascal Fenkam Technical University of Vienna, Argentinierstrasse 8/184-1, 1040 Vienna / Austria
Gerald Reif Technical University of Vienna, Argentinierstrasse 8/184-1, 1040 Vienna / Austria
Harald Gall Technical University of Vienna, Argentinierstrasse 8/184-1, 1040 Vienna / Austria

ACM International Conference Proceeding Series archive
Proceedings of the 14th international conference on Software engineering and knowledge engineering table of contents
Ischia, Italy SESSION: Computer-supported cooperative work table of contents
Pages: 513 - 518
Year of Publication: 2002
ISBN:1-58113-556-4

Abstract:
Mobile teamwork has become an emerging requirement in the daily business of large enterprises. Employees collaborate across locations and need support while they are on the move. Business documents (artifacts) and expertise need to be shared independent of the actual location or connectivity (e.g., access through a mobile phone, laptop, Personal Digital Assistant, etc.) of employees. Although many collaboration tools and systems exist, most do not deal with new requirements such as locating artifacts and experts through distributed searches, advanced information subscription and notification, and mobile information sharing and access. The MOTION service architecture that we have developed supports mobile teamwork by taking into account the different connectivity modes of users, provides access support for various devices such as laptop computers and mobile phones, and uses XML meta-data and the XML Query Language (XQL) for distributed searches and subscriptions. In this paper, we describe the architecture and the components of our generic MOTION service platform for building collaborative applications. The MOTION Teamwork Services Components are currently being evaluated in two industry case-studies.

My Discussion:
The system described is not a replication-based system like groove, but one where participants publish their work with metadata in their own or a constant respositories. Users can spawn XML queries that run over these repositories to find data, or subscribe to specific publishing events. What is interesting for the connected mobile space is how the developers explcitly acknowledge that working over a mobile device isn't a 'laptop-lite' event with always-on pipes, but actually includes SMS and having to run more capable proxies for the constrained devices, an acknowledgement probably stemming from the fact that they built the system. This paper is now 2 years old, and I really should follow up to see what their trial results were -- is having access to document repositories from a Nokia 3650 even useful? Is being able to tailor rules to be warned about certain things over SMS or WAP push or email useful? This paper does not say, it describes only a system, a complex but seemingly well-engineered one.

Comments: Post a Comment

This page is powered by Blogger. Isn't yours?