Extreme Markup Languages 2003: Proceedings

Proceedings Home Page

Can Topic Maps describe context for enterprise-wide applications?

Duane Degler [IPGems]

Lisa Battle [Lockheed Martin]
Abstract

Topic maps provide exciting opportunities not just to make information easier to find, but to increase the usability of software. In order to provide users with the information that applies to their particular situations, in forms that they can use, software must be aware of a user’s context (in a broad, multi-dimensional sense). Topic maps can serve as the language for linking information to software applications and for sharing information about context among applications. Using topic maps in the design of user-centered software applications for the U.S. Social Security Administration, we have encountered several interesting issues that are not necessarily found in the design of stand-alone information resources. In the future, there is an increasing potential role for topic maps in the design of flexible applications. The infrastructural investments required to achieve richly contextual applications can be made gradually, over the course of many small and successful projects, as the role and benefits of Topic Maps becomes increasingly visible.

Can Topic Maps describe context for enterprise-wide applications?

Introduction: our preoccupation with context
The user-centered approach to software design
What do we mean by context?
A potential new role for Topic Maps as the “common language” for context
Using Topic Maps to provide contextually relevant information
Case study: a government legal research application
The first stage: “I know what I’m looking for — get me to it!”
The second stage: “I don’t know what I need to know”
The third stage: “Just tell me whatever I absolutely must know”
The fourth stage: “I didn’t know I needed that”
Benefits of proactive information
Building and maintaining the Topic Map
Topic creation by end users
Can a map be both generic and situation-specific?
Using Topic Maps to create contextually relevant applications
Providing an API/Web service to information resources
Creating flexible, modular applications
Storing and maintaining business rules
Translating between business and technical language
Conclusion