<$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 11, 2005
Display-agnostic hypermedia 
Link

Unmil P. Karadkar Texas A&M University, College Station, TX
Richard Furuta Texas A&M University, College Station, TX
Selen Ustun Texas A&M University, College Station, TX
YoungJoo Park Texas A&M University, College Station, TX
Jin-Cheon Na Nanyang Technological University, Singapore
Vivek Gupta Texas A&M University, College Station, TX
Tolga Ciftci Texas A&M University, College Station, TX
Yungah Park Texas A&M University, College Station, TX

Conference on Hypertext and Hypermedia archive
Proceedings of the fifteenth ACM conference on Hypertext & hypermedia table of contents
Santa Cruz, CA, USA
SESSION: Novel interfaces table of contents
Pages: 58 - 67
Year of Publication: 2004
ISBN:1-58113-848-2

Abstract:
In the diversifying information environment, contemporary hypermedia authoring and filtering mechanisms cater to specific devices. Display-agnostic hypermedia can be flexibly and efficiently presented on a variety of information devices without any modification of their information content. We augment context-aware Trellis (caT) by introducing two mechanisms to support display-agnosticism: development of new browsers and architectural enhancements. We present browsers that reinterpret existing caT hypertext structures for a different presentation. The architectural enhancements, called MIDAS, flexibly deliver rich hypermedia presentations coherently to a set of diverse devices.

My Discussion:
Mainly a description of the MIDAS, a hypermedia system that is very different from the web we know today. MIDAS stores the hypermedia, best described here as linked multi-media presentations, such that the same presentation can contain the same content in different modalities. For example, a URI could abstractly point to a narrative that in the repository is available as both as a PDF, a spoken audio file, and a simple text-file, and by exchaing metadata about the content and the capability of the client and the context of the user, MIDAS can choose to present the narrative as audio, for example if the user is using a cellphone, or the PDF if the user is using a laptop. MIDAS servers also synchronize the accessing of the presentation URI with multiple simultaneous browsers and can coordinate what is being shown, so a user listening to the narrative on the cellphone could watch the associated pictures on a PDA or a large screen of a public terminal, and since MIDAS knows the user is already listening, will not use any of the real estate on the PDA for the text, but just show the pictures.
It sounds really advanced and useful, but reading the paper one gets the feeling that authoring media for a system in which the author has so little prior knowledge of how the narratives will be viewed, might make it very difficult to create a specific experience, something current web authors are very invested in. Very little is said about what state MIDAS is in, although the figures leave the impression that while the servers may be specced and built well, the client side browsers are still downright primitive. It has potential to allow users access to their media in many different ways, but the paper doesn't spend time actually discussing much of the experiences and feelings of the users, either as browers or authors.

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.

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