Emerging Technologies for Semantic Work Environments: Techniques, Methods, and Applications
Jörg Rech Fraunhofer Institute for Experimental Software Engineering, Germany Björn Decker empolis GmbH–Part of Arvato: A Bertelsmann Company, Germany Eric Ras Fraunhofer Institute for Experimental Software Engineering, Germany
InformatIon scIence reference Hershey • New York
Acquisitions Editor: Development Editor: Senior Managing Editor: Managing Editor: Assistant Managing Editor: Copy Editor: Typesetter: Cover Design: Printed at:
Kristin Klinger Kristin Roth Jennifer Neidig Jamie Snavely Carole Coulson Jeannie Porter Michael Brehm Lisa Tosheff Yurchak Printing Inc.
Published in the United States of America by Information Science Reference (an imprint of IGI Global) 701 E. Chocolate Avenue, Suite 200 Hershey PA 17033 Tel: 717-533-8845 Fax: 717-533-8661 E-mail:
[email protected] Web site: http://www.igi-global.com and in the United Kingdom by Information Science Reference (an imprint of IGI Global) 3 Henrietta Street Covent Garden London WC2E 8LU Tel: 44 20 7240 0856 Fax: 44 20 7379 0609 Web site: http://www.eurospanbookstore.com Copyright © 2008 by IGI Global. All rights reserved. No part of this publication may be reproduced, stored or distributed in any form or by any means, electronic or mechanical, including photocopying, without written permission from the publisher. Product or company names used in this set are for identification purposes only. Inclusion of the names of the products or companies does not indicate a claim of ownership by IGI Global of the trademark or registered trademark. Library of Congress Cataloging-in-Publication Data Emerging technologies for semantic work environments : techniques, methods, and applications / Jorg Rech, Bjorn Decker and Eric Ras, editors. p. cm. Summary: "This book describes an overview of the emerging field of Semantic Work Environments by combining various research studies and underlining the similarities between different processes, issues and approaches in order to provide the reader with techniques, methods, and applications of the study"--Provided by publisher. ISBN-13: 978-1-59904-877-2 (hbk.) ISBN-13: 978-1-59904-878-9 (e-book) 1. Semantic Web. 2. Semantic networks (Information theory) 3. Information technology--Management. I. Rech, Jorg. II. Decker, Bjorn. III. Ras, Eric. TK5105.88815.E44 2008 658.4'038--dc22 2007042680 British Cataloguing in Publication Data A Cataloguing in Publication record for this book is available from the British Library. All work contributed to this book set is original material. The views expressed in this book are those of the authors, but not necessarily of the publisher. If a library purchased a print copy of this publication, please go to http://www.igi-global.com/agreement for information on activating the library's complimentary electronic access to this publication.
Table of Contents
Foreword ............................................................................................................................................ xiv Preface ................................................................................................................................................ xvi Acknowledgment ..............................................................................................................................xxiii
Section I Introduction Chapter I Enabling Social Semantic Collaboration: Bridging the Gap Between Web 2.0 and the Semantic Web ................................................................................................ 1 Sören Auer, University of Pennsylvania, USA Zachary G. Ives, University of Pennsylvania, USA Chapter II Communication Systems for Semantic Work Environments ................................................................ 16 Thomas Franz, University of Koblenz-Landau, Germany Sergej Sizov, University of Koblenz-Landau, Germany Chapter III Semantic Social Software: Semantically Enabled Social Software or Socially Enabled Semantic Web? ..................................................................................................... 33 Sebastian Schaffert, Salzburg Research Forschungsgesellschaft, Austria
Section II Semantic Work Environment Tools Chapter IV SWiM: A Semantic Wiki for Mathematical Knowledge Management ................................................. 47 Christoph Lange, Jacobs University Bremen, Germany Michael Kohlhase, Jacobs University Bremen, Germany
Chapter V CoolWikNews: More than Meet the Eye in the 21st Century Journalism ............................................................................................................................................. 69 Damaris Fuentes-Lorenzo, University Carlos III of Madrid, Spain Juan Miguel Gómez, University Carlos III of Madrid, Spain Ángel García Crespo, University Carlos III of Madrid, Spain Chapter VI Improved Experience Transfer by Semantic Work Support ................................................................. 84 Roar Fjellheim, Computas AS, Norway David Norheim, Computas AS, Norway Chapter VII A Semi-Automatic Semantic Annotation and Authoring Tool for a Library Help Desk Service ......................................................................................................... 100 Antti Vehviläinen, Helsinki University of Technology (TKK), Finland Eero Hyvönen, Helsinki University of Technology (TKK) and University of Helsinki, Finland Olli Alm, Helsinki University of Technology, Helsinki University of Technology (TKK), Finland Chapter VIII A Wiki on the Semantic Web .............................................................................................................. 115 Michel Buffa, Mainline, I3S Lab, France Guillaume Erétéo, Edelweiss, INRIA, France Fabien Gandon, Edelweiss, INRIA, France Chapter IX Personal Knowledge Management with Semantic Technologies ....................................................... 138 Max Völkel, Forschungszentrum Informatik (FZI) Karlsruhe, Germany Sebastian Schaffert, Salzburg Research Forschungsgesellschaft mbH, Austria Eyal Oren, Digital Enterprise Research Institute (DERI), Ireland Chapter X DeepaMehta: Another Computer is Possible ...................................................................................... 154 Jörg Richter, DeepaMehta Company, Germany Jurij Poelchau, fx-Institute, Germany
Section III Methods for Semantic Work Environments Chapter XI Added-Value: Getting People into Semantic Work Environments ..................................................... 181 Andrea Kohlhase, Jacobs University Bremen and DFKI Bremen, Germany Normen Müller, Jacobs University Bremen, Germany Chapter XII Enabling Learning on Demand in Semantic Work Environments: The Learning in Process Approach ..................................................................................................... 202 Andreas Schmidt, FZI Research Center for Information Technologies, Germany
Section IV Techniques for Semantic Work Environments Chapter XIII Automatic Acquisition of Semantics from Text for Semantic Work Environments ............................................................................................................................ 217 Maria Ruiz-Casado, Universidad Autonoma de Madrid, Spain Enrique Alfonseca, Universidad Autonoma de Madrid, Spain Pablo Castells, Universidad Autonoma de Madrid, Spain Chapter XIV Technologies for Semantic Project-Driven Work Environments ........................................................ 245 Bernhard Schandl, University of Vienna, Austria Ross King, Austrian Research Centers GmbH (ARC) Research Studios, Austria Niko Popitsch, Austrian Research Centers GmbH (ARC) Research Studios, Austria Brigitte Rauter, P.Solutions Informationstechnologie GmbH, Austria Martin Povazay, P.Solutions Informationstechnologie GmbH, Austria Chapter XV An Integrated Formal Approach to Semantic Work Environments Design ............................................................................................................................................... 262 Hai H. Wang, University of Southampton, UK Jin Song Dong, National University of Singapore, Singapore Jing Sun, University of Auckland, New Zealand Terry R. Payne, University of Southampton, UK Nicholas Gibbins, University of Southampton, UK Yuan Fang Li, National University of Singapore, Singapore Jeff Pan, University of Aberdeen, UK
Chapter XVI Lightweight Data Modeling in RDF ................................................................................................... 281 Axel Rauschmayer, University of Munich, Germany Malte Kiesel, DFKI, Germany
Compilation of References .............................................................................................................. 313 About the Contributors ................................................................................................................... 337 Index ................................................................................................................................................ 346
Detailed Table of Contents
Foreword ............................................................................................................................................ xiv Preface ................................................................................................................................................ xvi Acknowledgment ..............................................................................................................................xxiii
Section I Introduction This section will help the reader to learn about the most common technologies and to be able to classify these technologies. In addition, the reader will get a better understanding of why certain decisions about the usage of technologies have been made in the chapters of the subsequent sections. These chapters give an introduction to technologies that can be used to develop semantic work environments (SWE) and present several R&D projects in which different technologies and related tools have been developed. The authors compare these technologies using characteristics such as collaboration, communication, and so forth, and provide the reader with an overview of fundamental building blocks as well as development requirements for SWE development. Chapter I Enabling Social Semantic Collaboration: Bridging the Gap Between Web 2.0 and the Semantic Web ................................................................................................ 1 Sören Auer, University of Pennsylvania, USA Zachary G. Ives, University of Pennsylvania, USA Sören Auer and Zachary Ives introduce the interrelation between two trends that semantic work environments rely on: Web 2.0 and the Semantic Web. Both approaches aim at integrating distributed data and information to provide enhanced search, ranking, browsing, and navigation facilities for SWEs. They present several research projects to show how both fields can lead to synergies for developing knowledge bases for the Semantic Web.
Chapter II Communication Systems for Semantic Work Environments ................................................................ 16 Thomas Franz, University of Koblenz-Landau, Germany Sergej Sizov, University of Koblenz-Landau, Germany Thomas Franz and Sergej Sizov point out that communication is one of the main tasks of a knowledge worker, as it denotes the exchange of information and the transfer of knowledge, making it vital for any collaborative human work. The authors introduce different communication systems to indicate their different utilization and role in knowledge work. They present requirements on communication for SWEs and compare conventional communication tools and channels with these requirements. After presenting research work that contributes to the communication of knowledge work, they conclude with a visionary scenario about communication tools for future SWEs. Chapter III Semantic Social Software: Semantically Enabled Social Software or Socially Enabled Semantic Web? ..................................................................................................... 33 Sebastian Schaffert, Salzburg Research Forschungsgesellschaft, Austria Sebastian Schaffert continues the discussion of the synergies between Web 2.0/social web and the Semantic Web. He introduces two perspectives on how Semantic Social Software can be reached: One perspective is semantically enabled social software, that is, the usage of semantic metadata to enhance existing social software. The other perspective is a socially enabled Semantic Web, which means the usage of Social Software to create semantic metadata. Three examplary applications of semantic social software (i.e., Semantic Wikis, Semantic Weblogs, and e-portfolios) are provided by the author for deriving outstanding aspects of Semantic Social Software.
Section II Semantic Work Environment Tools This section provides seven chapters that are more related to concrete realizations of SWEs—tools developed to support work environments and personal activities using semantic technologies. These tools come from very different application domains such as oil drilling, journalism, and library help desk services, and motivate many application scenarios that exist for semantic work environments. The chapters further extend the overview of technologies already provided in Section I. Concrete architectures and platforms are presented for developing SWEs such as Semantic Wikis, Semantic Personal Knowledge Management systems, and Semantic Desktops. Several chapters also elaborate on the topics of authoring and annotating content, refer to inference technologies such as case-based reasoning, or present visualization approaches to support the tagging, linking, or presentation of content in SWEs.
Chapter IV SWiM: A Semantic Wiki for Mathematical Knowledge Management ................................................. 47 Christoph Lange, Jacobs University Bremen, Germany Michael Kohlhase, Jacobs University Bremen, Germany Christoph Lange and Michael Kohlhase present SWiM, a semantic Wiki for collaboratively building, editing, and browsing mathematical knowledge. In this Wiki, the regular Wiki markup is replaced by a markup format and ontology language for mathematical documents. SWiM represents a social semantic work environment, which facilitates the creation of a shared collection of mathematical knowledge. Chapter V CoolWikNews: More than Meet the Eye in the 21st Century Journalism ............................................................................................................................................. 69 Damaris Fuentes-Lorenzo, University Carlos III of Madrid, Spain Juan Miguel Gómez, University Carlos III of Madrid, Spain Ángel García Crespo, University Carlos III of Madrid, Spain Damaris Fuentes Lorenzo, Juan Miguel Gómez, and Ángel García Crespo describe a semantic work environment for the collaborative creation of news articles, thus building a basis for citizen journalism. Articles “within” this Wiki can be annotated using ontological metadata. This metadata is then used to reward users in terms of advanced browsing and searching the newspapers and newspaper archives, in particular finding similar articles. Faceted metadata and graphical visualizations help the user to find more accurate information and semantic related data when it is needed. The authors state that the Wiki architecture is domain-independent and can be used for other domains apart from news publishing. Chapter VI Improved Experience Transfer by Semantic Work Support ................................................................. 84 Roar Fjellheim, Computas AS, Norway David Norheim, Computas AS, Norway Roar Fjellheim and David Norheim describe the Active Knowledge Support for Integrated Operations (AKSIO) system that supports the experience transfer in operations of offshore oilfields. AKSIO is an example of a SWE that provides information in a timely and context-aware manner. Experience reports are processed and annotated by experts and linked to various resources and specialized knowledge networks. The authors demonstrate how Semantic Web technology is an effective enabler of improved knowledge management processes in corporate environments. Chapter VII A Semi-Automatic Semantic Annotation and Authoring Tool for a Library Help Desk Service ......................................................................................................... 100 Antti Vehviläinen, Helsinki University of Technology (TKK), Finland Eero Hyvönen, Helsinki University of Technology (TKK) and University of Helsinki, Finland Olli Alm, Helsinki University of Technology, Helsinki University of Technology (TKK), Finland
Antti Vehviläinen, Eero Hyvönen, and Olli Alm discuss how knowledge technologies can be utilized in creating help desk services on the Semantic Web. The authors focus on support for the semi-automatic annotation of natural language text for annotating question-answer pairs, and case-based reasoning techniques for finding similar questions. To provide answers matching with the content indexer’s and end-user’s information needs, methods for combining case-based reasoning with semantic search, linking, and authoring are proposed. The system itself is used as a help-desk application in Finnish libraries to answer questions asked by library users. Chapter VIII A Wiki on the Semantic Web .............................................................................................................. 115 Michel Buffa, Mainline, I3S Lab, France Guillaume Erétéo, Edelweiss, INRIA, France Fabien Gandon, Edelweiss, INRIA, France Michel Buffa, Guillaume Erétéo, and Fabian Gandon present a semantic Wiki called SweetWiki that addresses several social and usability problems of conventional Wikis by combining a WYSIWYG editor and semantic annotations. SweetWiki makes use of semantic web concepts and languages and demonstrates how the use of such paradigms can improve navigation, search, and usability by preserving the essence of a Wiki: simplicity and social dimension. In their chapter, they also provide an overview of several other semantic Wikis. Chapter IX Personal Knowledge Management with Semantic Technologies ....................................................... 138 Max Völkel, Forschungszentrum Informatik (FZI) Karlsruhe, Germany Sebastian Schaffert, Salzburg Research Forschungsgesellschaft mbH, Austria Eyal Oren, Digital Enterprise Research Institute (DERI), Ireland Max Völkel, Sebastian Schaffert, and Eyal Oren present how to use semantic technologies for improving one’s personal knowledge management. Requirements on personal knowledge management based on a literature survey are provided. Current nonsemantically as well as semantically-enhanced personal knowledge management tools were investigated and the reader is provided with an overview of existing tools. To overcome the drawbacks of the current systems, semantic Wikis are presented as the best implementation of the semantically-enhanced personal knowledge management vision—even if they do not perfectly fulfill all the stated requirements. Chapter X DeepaMehta: Another Computer is Possible ...................................................................................... 154 Jörg Richter, DeepaMehta Company, Germany Jurij Poelchau, fx-Institute, Germany Jörg Richter and Jurij Poelchau present the DeepaMehta platform as a semantic work environment. This platform replaces the traditional desktop by a semantic desktop. The authors explain the multilayered distributed architecture of DeepaMehta, which provides native support for topic maps to visualize the
underlying semantics of knowledge. Two exemplary applications of the DeepaMehta platform are presented that implement semantic work environments. The authors conclude their chapter with interesting future research directions and open questions that reflect future applications of SWEs.
Section III Methods for Semantic Work Environments Besides defining the requirements and choosing the right building blocks for developing an SWE, the success of such an environment still depends first of all on how the systems motivate people to participate and use the system, and second, on how information is structured and presented to the user. Hence, this section describes methods for better involving people in Semantic Work Environments and for enhancing so-called context-steered learning in these environments. Chapter XI Added-Value: Getting People into Semantic Work Environments ..................................................... 181 Andrea Kohlhase, Jacobs University Bremen and DFKI Bremen, Germany Normen Müller, Jacobs University Bremen, Germany Andrea Kohlhase and Normen Müller analyze the motivational aspect of why people are not using semantic work environments. They argue that the underlying motivational problem between vast semantic potential and extra personal investment can be analyzed in terms of the “Semantic Prisoner’s Dilemma.” Based on these considerations, they describe their approach of an added-value analysis as a design method for involving people in Semantic Work Environments. In addition, they provide an overview of other software design methods that can be used to develop SWEs and present two application examples of this analysis approach. Chapter XII Enabling Learning on Demand in Semantic Work Environments: The Learning in Process Approach ..................................................................................................... 202 Andreas Schmidt, FZI Research Center for Information Technologies, Germany Andreas Schmidt presents a method for building individual e-learning material that can be presented in SWEs. The cornerstone of this approach is the context-steered learning method, which uses the context of users and ontologically enriched learning material to build tailored e-learning material. Context-steered learning implements pedagogical guidance and thus goes beyond simple information delivery. It considers not only the current learning needs, but also the prerequisites for understanding the provided resources and a limited form of meaningful order (in the pedagogical sense). The author uses an architecture of loosely coupled services for implementing context-steered learning. This chapter is a contribution towards the challenge of presenting and structuring information so that it supports short-term problem solving as well as long-term competence development.
Section IV Techniques for Semantic Work Environments In order to realize Semantic Work Environments, information has to be collected, structured, and processed. This section describes specific techniques for supporting these activities, which might be helpful when building one’s own semantic-based tools. These techniques enhance available techniques and therefore provide better solutions for the challenges of extracting semantics, managing information from various distributed sources, and developing interfaces to quickly manage, annotate, and retrieve information. Chapter XIII Automatic Acquisition of Semantics from Text for Semantic Work Environments ............................................................................................................................ 217 Maria Ruiz-Casado, Universidad Autonoma de Madrid, Spain Enrique Alfonseca, Universidad Autonoma de Madrid, Spain Pablo Castells, Universidad Autonoma de Madrid, Spain Maria Ruiz-Casado, Enrique Alfonseca, and Pablo Castells provide an overview of techniques for semiautomatically extracting semantics from natural language text documents. These techniques can be used to support the semantic enrichment of plain information, since the manual tagging of huge amounts of contents is very costly. They describe how natural language processing works in general and state methods for tackling the problem of “Word Sense Disambiguation.” The authors provide a set of techniques for information and relationship extraction. This chapter gives a comprehensive overview of semantic acquisition techniques for SWEs, which reduce the cost of manually annotating preexisting information. Chapter XIV Technologies for Semantic Project-Driven Work Environments ........................................................ 245 Bernhard Schandl, University of Vienna, Austria Ross King, Austrian Research Centers GmbH (ARC) Research Studios, Austria Niko Popitsch, Austrian Research Centers GmbH (ARC) Research Studios, Austria Brigitte Rauter, P.Solutions Informationstechnologie GmbH, Austria Martin Povazay, P.Solutions Informationstechnologie GmbH, Austria Bernhard Schandl, Ross King, Niko Popitsch, Brigitte Rauter, and Martin Povazay state that capturing the semantics of documents and their interrelations supports finding, exploring, reusing, and exchanging digital documents. They believe that the process of capturing semantics must take place when the system users have maximum knowledge about a certain document (i.e., when the document is created or updated) and should interfere with a user’s normal workflow as little as possible. Therefore, they present METIS, a framework for the management of multimedia data and metadata from various distributed sources; Ylvi, a semantic Wiki platform with a high-level, collaborative user interface built on top of METIS for rapid knowledge exchange and management; and SemDAV, a Semantic-Web-based protocol that allows integrating personal information and sharing semantic information. SemDAV provides interfaces to quickly manage, annotate, and retrieve information.
Chapter XV An Integrated Formal Approach to Semantic Work Environments Design ............................................................................................................................................... 262 Hai H. Wang, University of Southampton, UK Jin Song Dong, National University of Singapore, Singapore Jing Sun, University of Auckland, New Zealand Terry R. Payne, University of Southampton, UK Nicholas Gibbins, University of Southampton, UK Yuan Fang Li, National University of Singapore, Singapore Jeff Pan, University of Aberdeen, UK The authors state that the services found in SWEs may have intricate data states, complex process behaviors, and concurrent interactions. They propose TCOZ (Timed Communicating Object-Z), a high-level design technique, as an effective way for modeling such complex SWE applications. Tools for mapping those models, for example, to the Unified Modeling Language (UML) or to several other formats, have been developed. In this chapter, the authors explain TCOZ, and use TCOZ for formally specifying the functionalities of an examplary application (a talk discovery system). They present tools for extracting an OWL web ontology used by software services as well as for extracting the semantic markup for software services from the TCOZ design model automatically. Chapter XVI Lightweight Data Modeling in RDF ................................................................................................... 281 Axel Rauschmayer, University of Munich, Germany Malte Kiesel, DFKI, Germany Axel Rauschmayer and Malte Kiesel state that the RDF standard is, in fact, suitable for lightweight data modeling, but it lacks clearly defined standards to completely support it. They present the Editing MetaModel (EMM), which provides standards and techniques for implementing RDF editing: It defines an RDF vocabulary for editing and clearly specifies the semantics of this vocabulary. The authors describe the EMM constructs and its three layers (i.e., schema, presentation, and editing). The schema defines the structure of the data, the presentation selects what data to display, and the editing layer uses projections to encode, visualize, and apply changes to RDF data. Particular focus is given to a formal description of the EMM and to the potential implementation of this model in the GUI of a semantic work environment. At the end of the chapter they provide a set of related technologies for modeling semantics for SWEs. They think that EMM is useful for developers of data-centric (as opposed to ontology-centric) editors and can serve as a contribution to the ongoing discussion about simpler versions of OWL.
Compilation of References .............................................................................................................. 313 About the Contributors ................................................................................................................... 337 Index ................................................................................................................................................ 346
xiv
Foreword
Since the dawn of the Semantic Web, we have been working on developing techniques that use the data, metadata, and links available on the World Wide Web (WWW) for inferring additional services. These services aim at supporting our work and lives with technologies such as the resource description framework (RDF) and, most recently, the Web ontology language (OWL). Several of these technologies enable or use semantic data and also enable further technologies that exploit the wealth of information on the WWW. This book, edited by Jörg Rech, Eric Ras, and Björn Decker, deals with another interesting and important problem, namely, integrating semantic technologies into work environments. It looks at ways of creating semantically richer applications that intelligently assist the user with additional information. A richer representation enables new services for people and enables further technologies that exploit this semantic information. Today, semantic technologies increasingly find their way into collaborative tools such as Wikis, Desktops, or Web-based platforms. In the context of corporate settings, these semantic-based collaborative applications represent enhanced tools that intelligently and autonomously support the knowledge worker with relevant information on time. Semantic work environments such as Semantic Wikis, Semantic Desktops, or Web-based semantic platforms are information systems that use semantic technologies to enhance the content in these systems for presentation, querying, reporting, or analysis purposes. Besides the information available on the WWW, these environments raise and exploit the more specific information available throughout company networks that is ripe to be integrated into new services. Furthermore, most employees of these companies like to share their knowledge and use these systems for documenting, storing, and disseminating their knowledge. To integrate the data into company networks, several systems have been developed that integrate semantic technologies—many of them are presented in this book. The first part of this book (sections one and two) is an interesting collection of chapters dealing with integrating semantic technologies and metadata into work environments. While the first three chapters investigate how semantic collaboration can be enabled and fostered, the other chapters describe real-world semantic work environments such as: • • • • •
SWiM: A Semantic Wiki for collaboratively building, editing, and browsing mathematical knowledge in order to support knowledge management for mathematicians. CoolWikNews: A Semantic Wiki devoted to news publishing in order to support knowledge management for journalists. AKSIO: An active socio-technical system for knowledge transfer between drilling projects, using documented experiences, best practices, and expert references. Opas: A semi-automatic annotation and authoring tool to support librarians via specialized help desk services. SweetWiki: A Semantic Wiki that integrates several semantic technologies to provide a Semantic Web application platform for everyone.
xv
• • • •
SemperWiki: A Semantic Wiki that is targeted to support personal knowledge management with semantic technologies. DeepaMehta: A platform designed to provide knowledge workers with additional information that supports their work, thoughts, and collaborations with colleagues. Ylvi: A Semantic Wiki that enables and supports the creation of semantic information during normal project work. OntoWiki: A Semantic Wiki aimed to support the social and semantic collaboration.
In order to enable and keep these semantic work environments alive, we need several technologies and methodologies. Standard data modeling formats and methods are necessary for promoting interoperability and for integrating users into these systems. This issue of using techniques and methods for semantic work environments is addressed in the second part (sections three and four) of this book. The six chapters address the following questions: • • • • •
How can we integrate people into semantic work environments and show them the added value these systems offer? How can we enable and foster learning during work activities and on demand in semantic work environments? How can we automatically acquire semantic information from previously existing sources for semantic work environments? How can we integrate the various existing technologies for semantic work environments to support project-driven work? How can we model the data, metadata, and relations used in semantic work environments?
In summary, the editors have selected a very interesting collection of chapters that present the current state of the art in semantic work environments. The primary objective of this book is to mobilize researchers and practitioners to develop and improve today’s work environments using semantic technologies. It raises the awareness in the research community for the great potential of SWE research. All in all, this book is a significant collection of contributions on the progress in semantic work environments and its use in various application domains. These contributions constitute a remarkable reference for researchers on new topics on the design and operation as well as on technical, managerial, behavioral, and organizational aspects of semantic work environments.
Prof. Dr. Klaus-Dieter Althoff Intelligent Information Systems University of Hildesheim, Germany September 2007
Klaus-Dieter Althoff is full professor at the University of Hildesheim and is directing a research group on intelligent information systems. He studied mathematics with a focus on expert systems at the University of Technology at Aachen. In 1992 he finished his doctoral dissertation on an architecture for knowledge-based technical diagnosis at the University of Kaiserslautern, where he also received the postdoctoral degree (Habilitation) with a thesis on the evaluation of case-based reasoning systems in 1997. He worked at the Fraunhofer Institute for Experimental Software Engineering as group leader and department head until he went to Hildesheim in April 2004. His main interests include techniques, methods and tools for developing, operating, evaluating, and maintaining knowledge-based systems, with a focus on case-based reasoning, agent technology, experience management, and machine learning.
xvi
Preface
In many companies, technical work environments integrate information systems aimed at supporting their long term organizational strategy and at providing efficient support to their core business processes. To support the knowledge worker by integrating these information systems is a complex task which requires the participation of various groups of people and technical systems. With the rise of semantic technologies, more and more information gets enriched with semantic metadata, which makes the information ready for harvesting. In the Web 2.0 (Murugesan, 2007) and Web 3.0 (Lassila & Hendler, 2007) movement, we experience this phenomenon through so-called “mashups” (Ankolekar, Krötzsch, Tran, & Vrandecic, 2007) of existing information sources such as search engines (e.g., Google Search), geographical map servers (e.g., Google Maps), collaborative encyclopedias (e.g., Wikipedia), or open picture repositories (e.g., Flickr). In order to map this phenomenon to the work environments in companies, we have to integrate the different information sources available in and near organizations. Semantic Work Environments (SWE) such as Semantic Wikis (Semantic Wikis, 2005; Völkel, Schaffert, Pasaru-Bontas, & Auer, 2006) or Semantic Desktops (Decker, Park, Quan, & Sauermann, 2005) are aimed at exploiting this wealth of information in order to intelligently assist our daily work. Ideally, they are built to collect data for deriving our current information needs in a specific situation and to provide processed and improved information that can be integrated into the task at hand. Furthermore, as the usage of this information is tightly integrated into our daily work, we do not only take part in the (re)use but also in the creation and sharing of information. This continuous flow of information, experience, and knowledge helps to keep us up-to-date in our area of expertise and enables us to integrate the experience of our colleagues into our own work. Hence, semantic work environments will also address the challenge of life-long learning because they provide easy and fast access to information that fits our current working situation. This means, on the one hand, that such systems help us to solve short-term problems, and on the other hand, that they enhance long-term competence development. Semantic Work Environments combine the strengths of Semantic Web technologies, workplace applications, and collaborative working—typically for a specific application domain such as research or journalism—and represent the “Semantic Web in the small.” Instead of making all content in the Internet machine-readable (i.e., “Semantic Web in the large”), the SWE approach tackles the problem on a smaller, more focused scale. Take Semantic Wikis as an example: Wikis are enhanced by the simple annotation of Wiki content with additional machine-readable metadata and tools that support authors during the writing of new or the changing of existing content (e.g., via self-explaining templates). This approach of building up the Semantic Web in the small is in line with current developments in the area of the Semantic Web. One prominent example is the definition of so called “microformats” (Ayers, 2006; Khare, 2006): Based on standard Web technology, they allow embedding small information chunks like contact information into Web sites.
xvii
We believe that semantic work environments are the first step towards achieving the vision of the Semantic Web, for several reasons: they are lightweight, goal-oriented, and more likely to use synergies. Semantic work environments are lightweight, since they support a specific problem and, therefore, require only relevant features for this task. They do not intend to solve a general, somewhat unfocused and fuzzy problem but have a certain application domain that imposes specific problem types to be solved. Therefore, requirements elicitation and implementation of the semantic work environments can be performed in a goal-oriented way and can be related to a set of working situations with specific tasks, technical work applications, and networks of people. Since they operate within a defined organizational boundary or community, reaching a consensus about the needed concepts and their meaning (e.g., by creating a consensus through an ontology) can be performed more easily compared to general Semantic Web applications. In addition, due to this focus, a quick return on investment is more likely. The focus of SWEs is also the basis for synergies that arise from embedding them tightly into the business processes and workflows within an organization. These business processes provide relevant information for classifying and organizing the information created and reused. This information can later be exploited by inference techniques to improve reuse by people operating in similar contexts. A second aspect of synergies is to overcome the dichotomy between the need for information and the often insufficient willingness to make information available for others. SWEs will play an important role for information storage, acquisition, and processing in specific application domains during knowledge work. In the future, they will enable the widespread use of automated inference mechanisms or software agents on top of the semantic information. Semantic enrichment of work environments will help participants in their daily work to avoid risks and project failures that are frequently encountered in traditional projects.
Challenges A commonly accepted fact is the ever-increasing amount of information we have to cope with during our daily work. While a century ago, most countries were based on manual-labor cultures, we are currently living in a world of knowledge workers. And the rise of computers and their integration into our daily work environments increases this flood of information even more. Or, to quote John Naisbitt: “We are drowning in information but starved for knowledge” (Naisbitt, 1984). Therefore, we need approaches to reduce the amount of information and to optimize access to important information and the way it is presented to the user—anywhere and anytime. Approaches such as Wikis are important; however, there is still much work to be done to integrate them into our daily working environments. Attempts to construct semantic work environments have to adequately deal with the challenges that exist in the new millennium. Such challenges can be classified into several categories: • • • •
Challenge 1: Enabling the collaboration of work communities for exchanging information and using semantic work environments. Challenge 2: Building semantic work environments to support social collaboration, information integration, and automated inference. Challenge 3: Starting semantic work environments and keeping them alive. Challenge 4: Adequately presenting information to a user so that it supports the two extremes of short-term problem solving and long-term competence development.
xviii
Challenge 8
Chapter III
Chapter IV Chapter V Chapter VI
Chapter VII
Chapter VIII
Chapter XIII
Chapter XIV
• •
Chapter XII
•
Chapter XI
•
Chapter IX Chapter X
Challenge 5
Challenge 4
Challenge 3
Challenge 7
Chapter II
Challenge 6
Chapter I
Challenge 2
Chapter
Challenge 1
Table 1. Chapters and approached challenges
Chapter XV
Chapter XVI
Challenge 5: Coping with the plethora of overlapping and similar Semantic Web-technologies, that is, how to select the right building blocks for the development of semantic work environments. Challenge 6: Coping with quick innovation cycles and the resulting time pressure that drives us away from classical search to context-sensitive and pro-active information offerings. Challenge 7: Obtaining the needed information in a timely manner. Challenge 8: Building architectures of such environments with different APIs, data structures, and business processes. In order to deal with the complexity of developing such tools, adequate methodologies, technologies, and ontologies are mandatory.
As in the case of Chapter X, most chapters in this book do not only approach one challenge, but tackle several of them.
solutions/BaCkground Today, members from multiple disciplines work on SWEs and collaborate to provide highly integrated services by integrating the ever increasing amount of information. Based on collaborative technologies such as Wikis and using semantic technologies such as OWL, collaborative semantic work environments
xix
can be created that are more efficient and effective than the sum of their parts and support the work of their users. However, this requires coping with different APIs, data structures, business and learning processes, as well as with the complexity of developing such tools, methodologies, technologies, and ontologies. Fortunately, SWEs do not need to be built from scratch. Modern information technologies as well as developments in knowledge management provide a substantial basis for developing SWEs. In particular, the vision of the Semantic Web (Berners-Lee, 1998) provides the basis for SWEs: Documents understandable by humans are augmented with machine-processable metadata. The Semantic Web provides standards such as the resource description framework (RDF) (Decker, Melnik et al., 2000; Decker, Mitra, & Melnik, 2000) or the Web ontology language (OWL) (Dean et al., 2002). Based on these standard languages, ontologies—that is, formal descriptions of concepts and their relations—allow inferring further facts and hypotheses. Examples of such ontologies are the document description ontology Dublin Core (McClelland, 2003) or upper-level ontologies like SUMO (Bouras, Gouvas, & Mentzas, 2007; Pease, 2003) or DOLCE (Oberle et al., 2007). These standards as well as the tools using these standards are the technical building blocks for semantic work environments. Besides the usage of such technologies, we have to think about how such systems provide information to the user. How should the information be structured? How should it be presented? What kind of navigation support should be offered? Information might be gathered from very different sources, different domains, and communities. The semantic annotation of information will help us to select relevant information and to put these information chunks in relation, thus giving a meaning to the information set. Solutions for making information more understandable, transferable to a new situation, and more learnable can be found in the domain of e-learning and knowledge management systems, (educational) adaptive hypermedia systems, instructional design literature, and so forth.
Book Content The objective of this book is to provide an overview of the field of semantic work environments by bringing together various research studies from different subfields and underlining the similarities between the different processes, issues, and approaches. The idea is also to show that many different application areas can benefit from the exploitation of already existing information sources. In order to present the solutions that address the challenge of creating semantic work environments by developing adequate methodologies, technologies, and ontologies, we structured the book into the four sections Introduction, Tools, Methods, and Techniques. The introduction section provides approaches that enable collaborative semantic work environments while the tools section gives an overview of currently implemented technologies with concrete results from field applications. The methods section provides insights into how to set up and run semantic work environments, and the techniques section describes base technologies to be used within semantic work environments. The introduction section starts with Chapter I, “Enabling Social Semantic Collaboration: Bridging the Gap between Web 2.0 and the Semantic Web” by Sören Auer and Zachary Ives. This chapter describes the interrelation between two trends that semantic work environments rely on in order to process existing and develop new knowledge: Web 2.0 as the base technology for human collaboration and the Semantic Web as the approach to add machine-processable descriptions to this knowledge. The technical realization is performed using the example of the tool OntoWiki. Chapter II, “Communication Systems for Semantic Work Environments,” by Thomas Franz and Sergej Sizov, points out how different means
xx
of communication are used within knowledge work. Common means of communications like e-mail or groupware are analyzed for “semantic gaps,” which are then refined into requirements for semantically enabled communication. Chapter III, “Semantic Social Software: Semantically Enabled Social Software or Socially Enabled Semantic Web?” by Sebastian Schaffert continues the discussion of the synergies between Web 2.0/social web and the Semantic Web. The author describes two ways of how semantic social software can be implemented: One possibility is semantically enabled social software, that is, Web 2.0 applications that are enriched with semantics. The other possibility is a Socially Enabled Semantic Web, which means involving communities in the build-up of ontologies. Three applications provide examples of semantic social software. The tools section provides an overview of current applications that can be a part of semantic work environments. This section comprises chapters four to ten. Chapter IV, “SWIM – A Semantic Wiki for Mathematical Knowledge Management,” by Christoph Lange and Michael Kohlhase, presents a semantic Wiki to share mathematical knowledge. In this Wiki, the regular Wiki markup is enhanced with additional mathematical markup, which integrates a mathematical ontology. Chapter V, “CoolWikNews: More than Meet the Eye in the XXI Century Journalism,” by Damaris Fuentes Lorenzo, Juan Miguel Gómez, and Ángel García Crespo, is about a semantic work environment for the collaborative creation of news articles, thus building a basis for citizen journalism. Articles in this Wiki can be annotated using ontological metadata. This metadata is then used to support navigation within articles, in particular for finding further relevant articles. Chapter VI, “Improved Experience Transfer by Semantic Work Support,” by Roar Fjellheim and David Norheim describes, the Active Knowledge Support for Integrated Operations (AKSIO) system. This system supports the experience management of oil drilling activities. This system supports collaborative knowledge creation and annotation by linking practitioners and experts. Chapter VII, “A Semi-Automatic Semantic Annotation and Authoring Tool for a Library Help Desk Service,” by Antti Vehviläinen, Eero Hyvönen, and Olli Alm, provides a help desk system that allows annotating natural language question-answer pairs with additional semantic information. To support this annotation, the system suggests potential annotations. Case-based reasoning is then used on this semantic information to retrieve the best fitting answers to a certain problem. The system itself is used in a help-desk application run by Finnish libraries to answer questions asked by library users. Chapter VIII, “A Wiki on the Semantic Web,” by Michel Buffa, Guillaume Erétéo, and Fabian Gandon, is about the SweetWiki system. This system combines a WYSIWYG editor and semantic annotations, creating a Wiki system with improved usability. The semantic annotation feature can use previously uploaded ontologies. In their article, they also provide an overview of several other semantic Wikis. Chapter IX, “Personal Knowledge Management with Semantic Technologies,” by Max Völkel, Sebastian Schaffert, and Eyal Oren, presents how to use semantic technologies to improve one’s personal knowledge management. Requirements on personal knowledge management based on a study are described. Current personal knowledge management tools are investigated concerning their drawbacks. To overcome these drawbacks, the usage of semantic Wikis for personal knowledge management is suggested. Chapter X, “DeepaMehta – Another Computer is Possible,” by Jörg Richter and Jurij Poelchau, presents the DeepaMehta platform, which can be used to build up semantic work environments. This platform provides native support for topics maps to visualize the underlying semantics of knowledge. Two examples of the application of the DeepaMehta platform show implementations of semantic work environments. Methods for Semantic Work Environments as the third section of this book presents approaches on how to build up and run semantic work environments. Chapter XI, “Added Value: Getting People into Semantic Work Environments,” by Andrea Kohlhase and Normen Müller, analyze the motivational aspect of why people are using semantic work environments based on the “prisoner’s dilemma.” Based on these considerations, they describe their approach of added-value analysis. Two application examples
xxi
of this analysis approach are presented. Chapter XII, “Enabling Learning on Demand in Semantic Work Environments: The Learning in Process Approach,” by Andreas Schmidt, presents a method for building individual learning material. The cornerstone of this approach is the Context-Steered Learning method, which uses the context of the user and ontologically enriched learning material to build tailored e-learning material. Base techniques for building Semantic Work Environments are presented in the final section. Chapter XIII, “Added Automatic Acquisition of Semantics from Text for Semantic Work Environments,” by Maria Ruiz-Casado, Enrique Alfonseca, and Pablo Castells, provides an overview of techniques for extracting semantics from text. These techniques can be used to support the semantic enrichment of previously non-annotated documents. Chapter XIV, “Technologies for Semantic Project-Driven Work Environments,” by Bernhard Schandl, Ross King, Niko Popitsch, Brigitte Rauter, and Martin Povazay, is about the METIS media data—an approach to support project management and execution by semantic work environments. Particular focus is placed on semantically enriched multimedia content. Based on METIS, the semantic Wiki Ylvi is used to build up organizational memories. Furthermore, the SemDAV Protocol is used for semantic data exchange. Chapter XV, “An Integrated Formal Approach to Semantic Work Environments Design,” by Hai H. Wang, Jin Song Dong, and Jing Sun, provides an ontology for defining Semantic Web services to build up flexible semantic work environments. An online talk discovery system is used as an example of their approach. Finally, Chapter XVI, “Lightweight Data Modeling in RDF,” by Axel Rauschmayer, and Malte Kiesel, presents the Editing Meta-Model (EMM), which supports editing within semantic work environments. Particular focus is given to a formal description of the Editing Meta-Model and to the potential implementation of this model in the GUI of a semantic work environment.
referenCes Ankolekar, A., Krötzsch, M., Tran, T., & Vrandecic, D. (2007). The two cultures: Mashing up Web 2.0 and the Semantic Web. Banff, Alberta, Canada: ACM Press. Ayers, D. (2006). The shortest path to the future Web. Internet Computing, IEEE, 10(6), 76-79. Berners-Lee, T. (1998). Semantic Web roadmap. Retrieved March 14, 2008, from http://www.w3.org/ DesignIssues/Semantic.html Bouras, A., Gouvas, P., & Mentzas, G. (2007). ENIO: An enterprise application integration ontology. Paper presented at the 18th International Conference on Database and Expert Systems Applications (DEXA ’07). Dean, M., Connolly, D., Harmelen, F. v., Hendler, J., Horrocks, I., McGuinness, D. L., et al. (2002). OWL Web ontology language 1.0 reference. Retrieved March 13, 2008, from http://www.w3.org/TR/ owl-ref/ Decker, S., Melnik, S., van Harmelen, F., Fensel, D., Klein, M., Broekstra, J., et al. (2000). The Semantic Web: The roles of XML and RDF. Internet Computing, IEEE, 4(5), 63-73. Decker, S., Mitra, P., & Melnik, S. (2000). Framework for the Semantic Web: An RDF tutorial. Internet Computing, IEEE, 4(6), 68-73.
xxii
Decker, S., Park, J., Quan, D., & Sauermann, L. (2005, November 6). The semantic desktop - next generation information management and collaboration infrastrucutre. Paper presented at the International Semantic Web Conference (ISWC 2005), Galway, Ireland. Khare, R. (2006). Microformats: The next (small) thing on the Semantic Web? Internet Computing, IEEE, 10(1), 68-75. Lassila, O., & Hendler, J. (2007). Embracing“Web 3.0.” IEEE Internet Computing, 11(3), 90-93. McClelland, M. (2003). Metadata standards for educational resources. Computer, 36(11), 107-109. Murugesan, S. (2007). Understanding Web 2.0. IT Professional, 9(4), 34-41. Naisbitt, J. (1984). Megatrends: Ten new directions transforming our lives. New York: Warner Books. Oberle, D., Ankolekar, A., Hitzler, P., Cimiano, P., Sintek, M., Kiesel, M., et al. (2007). DOLCE ergo SUMO: On foundational and domain models in the SmartWeb integrated ontology (SWIntO). Web Semantics, 5(3), 156-174. Pease, A. (2003). SUMO: A sharable knowledge resource with linguistic inter-operability. Paper presented at the Natural Language Processing and Knowledge Engineering, 2003. Proceedings. 2003 International Conference on. Semantic Wikis. (2005). Semantic Wiki Overview. Retrieved March 13, 2008, from http://c2.com/cgi/ wiki?SemanticWikiWikiWeb Völkel, M., Schaffert, S., Pasaru-Bontas, E., & Auer, S. (2006). Wiki-based knowledge engineering: Second workshop on Semantic Wikis. Odense, Denmark: ACM Press.
xxiii
Acknowledgment
Our vision for this book was to gather information about methods, techniques, and applications from the domain of semantic work environments, to share this information within the community, and to distribute this information across projects and organizational boundaries. During the course of realizing this vision, we received much support from people who spent a huge amount of effort on the creation and review process of the book. We would like to express our appreciation to all the projects and people involved in researching semantic work environments. We are especially grateful to the authors who provided us with deep insights into their projects and related results. Furthermore, we are also indebted to the publishing team at IGI Global for their continuing support throughout the whole publication process. Deep appreciation and gratitude is due to Jessica Thompson, Assistant Managing Development Editor at IGI Global, who supported us and kept the project on schedule. Most of the authors of chapters included in this book also served as reviewers for chapters written by other authors. Thanks go to all those who provided constructive and comprehensive reviews. Last but not least, thanks also go to the technical staff at Fraunhofer IESE and especially to Sonnhild Namingha for proofreading parts of the book. The Editors, Jörg Rech, Eric Ras, Björn Decker Kaiserslautern, Germany September 2007
Section I
Introduction
Chapter I
Enabling Social Semantic Collaboration:
Bridging the Gap Between Web 2.0 and the Semantic Web Sören Auer University of Pennsylvania, USA Zachary G. Ives University of Pennsylvania, USA
introduCtion The concepts Social Software and Web 2.0 were coined to characterize a variety of (sometimes minimalist) services on the Web, which rely on social interactions to determine additions, annotations, or corrections from a multitude of potentially minor user contributions. Nonprofit, collaboration-centered projects such as the free encyclopedia Wikipedia belong to this class of services, as well as commercial applications that enable users to publish, classify, rate, and review objects of a certain content type. Examples for this class of
content-centered Web 2.0 projects are del.iciou. us (for Web links), Digg.com (for news), Flickr (for images), and YouTube (for movies). Communication-centered services such as MySpace or XING enable individual communication and search for and within spatially distributed communities. So-called Web 2.0 mashups integrate and visualize the collected data and information in novel ways, unforeseen by the original content providers. The most prominent examples of mashups are based on Google Maps and overlay external content on a map. All these developments have a common approach of collecting metadata
Copyright © 2008, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
Enabling Social Semantic Collaboration
by making participation and contribution as easy and rewarding as possible. Even before Social Software and Web 2.0 applications emerged, prior attempts had been made to enable rapid assembly of data on the Web into more informative content: the most well-known such project is the Semantic Web, although researchers had been working on “information integration for the Web” for many years prior (Mediators,TSIMMIS,Ariadne), with very different methodologies but a similar end goal. The Semantic Web is conceived as an extension of the existing Web to enable machine reasoning and inference: a prerequisite to this is that “information is given well-defined meaning” (Berners-Lee, Hendler, & Lassila, 2001). This approach is based on a standardized description model, Resource Description Framework (RDF) (Lassila & Swick, 1999) and semantic layers on top for semantic nets and taxonomies (RDF-Schema) as well as ontologies, logic axioms, and rules (OWL and SWRL). However, the Semantic Web is not ubiquitous to this point, in part because of the high level of effort involved in annotating data and developing knowledge bases to support the Semantic Web. The Web 2.0 and Semantic Web efforts, which have largely gone on simultaneously, pose an interesting study in contrasting methods to achieve a similar goal. Both approaches aim at integrating dispersed data and information to provide enhanced search, raking, browsing, and navigation facilities for the Web. However, Web 2.0 mainly relies on aggregate human interpretation (the collaborative “ant” intelligence of community members) as the basis of its metadata creation, conflict resolution, ranking, and refinement; the Semantic Web relies on complex but sophisticated knowledge representation languages and machine inference (Table 1). A natural question to ask is whether the different approaches can be combined in a way that leads to synergies. We discuss in this chapter how the question is being answered in the affirmative by a number of promising research
Table 1. Similarities and differences between social software and the Semantic Web Social Software & Web 2.0
Semantic Web
Collaboration and integration focused Based on the Web Provide enhanced means for search and navigation End-user and business centred Community intelligence Post-encoding of semantics Opaque, homogeneous content Light-weight S&T
Technology centred Artificial intelligence Pre-encoding of semantics Complex, heterogeneous content Heavy-weight S&T
projects. The main goal of these projects is to support collaborative knowledge engineering in social networks, with high reward and little effort. After presenting fundamental communication and collaboration patterns of Social Software, we exhibit the tool OntoWiki for social, semantic collaboration. In subsequent sections we suggest strategies for employing Social Software and Web 2.0 methods to support the creation of knowledge bases for the Semantic Web. We give an overview on further and relater work and conclude with remarks concerning future challenges.
soCial software and weB 2.0 The concepts social software (Webb, 2004) and Web 2.0 (O’Reilly, 2005) were recently conceived to explain the phenomenon that computers and technology are becoming more and more important for human communication and collaboration. In particular the following aspects are important with respect to software enabling social collaboration: (1) usability, (2) community and participation, (3) economic aspects, (4) standardisation, and (5) reusability and convergence. In addition to that, a precise delimitation of the concept social software is due to heterogeneity of applications, applicants, and application domains complex. It was proposed by Shirky (2003) to define the concept of social software not just with respect
Enabling Social Semantic Collaboration
Table 2. Typical communication patterns for social software Pattern
Name
Partner
Point-to-point
1:1
E-mail, SMS/MMS
Bidirectional
1:1
IM, VoIP
Star-like
1:n
Web pages, Blogs, Podcasts
Net-like
n:m
Wikis, content communities
to characteristics of a certain software, but also with regard to communication patterns leading to the formation of a virtual community. Typical communication patterns of Social Software are depicted in Table 2. On the technological side, the popularity of social software is related to the development and use of the software development and communication paradigms AJAX (Asyncrounous JAvascript and XML), REST (Representational State Transfer), and JSON (Javascript Object Notation). These, in comparison to their counterparts Web services, RPC or remote desktop light-weight technologies enable completely new adaptive and interactive application architectures and services. Based on these technologies, a number of methods for user-interaction established, which encourage and simplify spontaneous contributions, help to organize a multiplicity of contributions, as well as to syndicate and mutually integrate the gained data. These include: •
Folksonomies: Content annotation by means of tags (i.e., self-describing attributes attached to content objects) enable the fuzzy but intuitive organization of comprehensive content bases (Golder et al., 2006). Tag clouds visualize tags to support navigation and filtering. Tags are colocated in a tag cloud when jointly used and emphasized differently to stress their usage frequency.
Direction
•
•
•
Example
Architecture of participation: Already the usage of an application creates an added value. For example, the added value can be generated by interactively evaluating usage statistics to determine popular content objects or by collecting ratings from users to classify content with respect to quality. Instant-gratification: Active users are rewarded with enhanced functionality and their reputation in the user community is visibly increased. This promotes contributions and helps to establish a collaboration culture. Mashups and feeds: The content collected in the system is syndicated for other services (e.g., RSS feeds, JSON exports, or public APIs). This allows seamless integration of different data end transforms the Web into a Service Oriented Architecture.
In the remainder of this chapter, we suggest approaches how these Web 2.0 and Social Software methods can be adopted to support semantic collaboration scenarios.
soCial semantiC work environments Recently, a number of strategies, approaches, and applications emerged aiming at employing elements of the Web 2.0 and Social Software for
Enabling Social Semantic Collaboration
semantic collaboration on the Web. Examples are the approaches to integrate semantics into wikis, to bring the semantic to the user’s desktops, or to weave social networks by means of semantic technologies such as FOAF. The application domain for semantic collaboration scenarios can be often characterized in the following way: •
• • • • •
A single, precise usage scenario of the envisioned knowledge bases is initially not known or (easily) definable. A possibly large number of involved actors is spatially separated. The collaboration is not a business in itself but a means to an end. Only a small amount of human and financial resources is available. Application of reasoning services is (initially) not mission critical. The collaboration environment is Web-centric.
ally and intuitively for end users in a generic but configurable way and interlinked to related digital resources. Users should be enabled to enhance the knowledge schema incrementally as well as to contribute instance data agreeing on it as easy as possible to provide more detailed descriptions and modelings. More specifically, the following components should be realized in SSWEs which follow the star-like communication pattern: •
•
•
• Some concrete examples for the growing number of in such a way characterized usage scenarios of Social Semantic Working Environments (SSWE) are summarized in Table 3. In order to organize the collaboration in SSWEs we collect in the remainder of this section some requirements for SSWE tool support. The main goal is to rapidly simplify the acquisition, presentation and syndication of semantically structured information (e.g., instance data) from and for end users. This can be achieved by regarding knowledge bases as “information maps.” Each node at the information map is represented visu-
•
• •
Intuitive display and editing of instance data should be provided in generic ways, yet enabling means for domains specific extensions. Semantic views allow the generation of different views and aggregations of the knowledge base. Versioning and evolution provides the opportunity to track, review, and selectively roll-back any changes made. Semantic search facilitates keyword searches on all information, search results can be filtered and sorted (using semantic relations). Community support enables discussions about small information chunks. Users are encouraged to vote about distinct facts or prospective changes. Online statistics interactively measure the popularity of content and activity of users. Semantic syndication supports the distribution of information and their integration into other services and applications.
Table 3. Example SSWE application scenarios
Aim of Semantic Collaboration
Example Domain
Example application
Creation of shared / common terminologies
Biomedicine
Open Biomedical Ontologies (OBO)
Integration of dispersed information sources
Virtual organizations
Web sites of research networks, or social and charitable organizations
Content creation within online-communities
Science & Technology
Conference, publication knowledge bases
Enabling Social Semantic Collaboration
In the next sections we propose strategies on how to put these requirements into effect in real systems and provide some examples of a prototypical implementation of an SSWE called OntoWiki.
visual representation of semantiC Content The intuitive visual representation of highly structured and interlinked content is a major challenge on the Semantic Web. The possibilities for adopting strategies from Social Software here are due to the more heterogeneous and complex content on the Semantic Web limited. However, a commonly seen strategy in Social Software such as Wikis and Blogs is to visually represent content bases to users in the shape of “information maps.” Each node at the information map, that is, Blog or Wiki article, is represented as a Web accessible page and interlinked to related nodes. Wiki or Blog article titles are used to create intuitive and recognizable Web addresses to ease navigation in the information map. A similar strategy can be applied for the generic visual representation of Semantic Web knowledge bases—a Web page can be rendered for each knowledge base object compiling all information available about the object and interlinking it with related content.
different views on instance data In addition to regarding knowledge bases on the Semantic Web as interlinked “information maps,” the intuitive visual representation can be facilitated by providing different views on instance data. Such views can be either domain specific or generic. Domain specific views can be seen in analogy to Web 2.0 Mashups and will have to be implemented specifically for a certain application scenario. Generic views, on the other hand, provide visual representations of instance data according to certain property types. We give some examples.
List Views List views present a selection of several instances in a combined view. The selection of instances to display can be either based on class membership (i.e., according to an rdf:type property) or based on the result of a selection by a facet or full-text search. List views can be made additionally configurable by enabling users to toggle the display of commonly used properties. Furthermore, each list element representing an individual instance should be linked to an individual view of that instance containing all related information.
Individual Views Individual views combine all the information related to a certain node in the knowledge base, that is, all properties and their values attached to a particular instance. Property values pointing to other individuals are (according to the information map metaphor) rendered as HTML links to the corresponding individual view. Alternatively, to get information about the referenced individual without having to load the complete individual view users can be enabled to expand a short summary (loaded per AJAX) right where the reference is shown.
Map View One building block of the Web 2.0 is the availability of public APIs, callable from embedded Javascripts thus enabling the integration of different data. Several APIs are, for example, available for embedding maps. Hence, if instance data in a knowledge base contains property values representing geographical information (i.e., addresses or longitudes/latitudes) map views can provide information about the geographical location of the selected data (see Figure 1). Depending on the extensibility of the API the integration can be realized bidirectional in a way that objects displayed in the map can be expanded and instance details
Enabling Social Semantic Collaboration
Figure 1. Map view (left) and calendar view (right) of instance data about scientific conferences in OntoWiki
are dynamically fetched from the knowledge base and displayed directly within the map view.
Calendar View Instances having property values with the associated datatype xsd:date can be displayed in a calendar view (see Figure 1). As for the map view the selection of instances displayed in the calendar view can be the result of a full-text search or facet-based filtering. Each item displayed can be linked to the individual view of the corresponding instance. To be able to integrate the calendar data with other Web services or desktop applications, a link can be offered to export calendar items in iCal format.
inline editing The smallest possible information chunks (i.e., RDF statements) presented on the user interface of the Semantic Web application are editable for users. For example, all information originating from statements and presented on the user interface can be equipped with small edit and add buttons (see Figure 2). On activation of the buttons, a suitable editing widget can be loaded into the currently displayed page and the corresponding statement object can be edited or a similar content added. This strategy can be seen analogous to the WYSIWYG (What You See Is What You Get) for text editing, since information can be edited in the same environment as it is presented to users.
CollaBorative authoring
view editing
Since Social Software and Web 2.0 applications are mainly focussed on a specific content type, content authoring functionality is mostly realized in an application specific way. A common element, however, is tagging functionality for individually annotating content objects. To enable users to author information within a Semantic Web application in a generic, application independent way, we see two complementary edit strategies:
Common combinations of information are editable in one single step. This requires the generation of comprehensive editing forms based on the view to be edited. The same technique as for generating the view can be applied for generating a suitable form, if the display of property values is replaced with appropriate widgets for editing these values. Examples for editable views are forms to add or edit (a) all information related to a specific instance or (b) values of a specific property across
Enabling Social Semantic Collaboration
Table 4. Editing widgets for the construction of edit forms Semantic widgets
Datatype widgets
Statements: allow editing of subject, predicate, and object.
Text editing: include restricted configurations for e-mail, numbers, and so forth.
Nodes: enable editing of either literals or resources.
WYSIWIG HTML editor: edits HTML fragments.
Resources: search and select for/from existing resources.
Dates: selects dates from a calendar.
Literals: literal data in conjunction with datatype/ language identifier.
File widget: uploading of files to the Semantic Web application
several instances. The latter simplifies the addition of information after a set of instances was initially created. Both editing strategies are founded on the idea that users edit content exactly at the same place where it is displayed. This facilitates incremental additions as well as ease-of-use and promotes user contributions in constructing a knowledge base.
editing widgets The implementation of both strategies can be grounded on a library of editing widgets thus simplifying extensions for new data-types and domain-specific enhancements. Such widgets
can be implemented in a server side programming language; they generate HTML fragments together with appropriate CSS (Cascading Style Sheet) definitions and optionally JavaScript code. They may be customized for usage in specific contexts. In Table 4, we propose some semantic and datatype specific widget types.
Concept Identification and Reuse Knowledge bases become increasingly advantageous, if once defined concepts (e.g., classes, properties, or instances) are as much reused and interlinked as possible. This especially eases the task of rearranging, extracting, and aggregating knowledge. To become part of the daily routine
Figure 2. OntoWiki instance display with statement edit buttons (left). Statement editor with interactive search for predefined individuals based on AJAX technology (right)
Enabling Social Semantic Collaboration
also for inexperienced and rare users, already defined concepts should be suggested to the user whenever he is requested to contribute new information. In a Web-based environment and for highly scalable knowledge bases conventional Web technologies were the major obstacles here, since they do not support large data sets to be handled at the client (browser) side. The Web 2.0 technologies AJAX and JSON help to overcome this limitation by enabling to interactively propose already defined concepts while the user types in new information to be added to the knowledge base (see Figure 2).
soCial CollaBoration aspeCts A major aim of SSWEs is to foster and employ social interactions for the development of knowledge bases. This eases the structured exchange of meta-information about the knowledge base drastically and promotes collaboration scenarios where face-to-face communication is hard. Making means of social interactions as easy as possible furthermore contributes in creating an “architecture of participation” that allows users to add value to the system as they use it. In the following, we elaborate on some examples how social interactions can be specifically supported by SSWEs
Change tracking All changes applied to a knowledge base should be tracked. An SSWE should enable the review of changes on different levels of detail. These are for example the RDF statement level, the taxonomy/class hierarchy level, the logic/ontology level or the domain level. The review of changes should be able to be restricted to a specific context or perspective on the knowledge base, such as changes on a specific instance, changes on instances of a certain class, or changes made by
a distinct user or user group. In addition to present such change sets on the Web, users should be able subscribe to get information about the most recent changes on objects of their interest by email or RSS/Atom feeds. This again promotes the participation of users.
Commenting Ideally an SSWE allows adding of comments to all information in the knowledge base. Commenting (and other tasks in general) can be promoted by reducing the number of clicks and the wait time in between as much as possible. This enables community driven discussions, for example about the validity of certain statements. Technically, this can be implemented on the basis of RDF reifications, which allow making statements about statements. Small icons attached to an object of a statement within the user interface can indicate that such reifications exist. See Figure 3. Positioning the mouse pointer on such an icon will immediately show up a tool tip with the most recent annotations; clicking on the icon will display them all.
rating As many Social Software applications SSWEs should allow users to rate instances according to a certain scale. Content specific ratings could for example be implemented by means of special annotation properties which allow the creation of rating categories and scales with respect to a
Figure 3. Comments attached to statements.
Enabling Social Semantic Collaboration
certain class. Instances of the class can then be rated according to these categories, thus allowing for example the rating of instances of a class publication according to categories originality, quality, and presentation.
Popularity All accesses to the knowledge base can be logged, thus allowing to arrange views on the content based on popularity. As with ratings or user activity, the popularity of content can be measured with respect to a certain knowledge base or fragment of it (e.g., popularity with respect to class membership) and with respect to a certain time period (e.g., last hour, day, week, month, etc.). This enables users to add value to the system as they use it.
Activity/Provenance The system keeps record of what was contributed by whom. This includes contributions to the ontology schema, additions of instance data or ratings, and commenting. This information can be used to honour active users in the context of the overall system, a specific knowledge base or a fragment of it (e.g., instance additions to some class). This way, it contributes to instantly gratify users for their efforts and helps building a community related to certain semantic content.
semantiC searCh To enable users of SSWEs to efficiently search for information in the knowledge base, the semantic structuring and representation of content should be employed to enhance the retrieval of information. We present two complementary strategies to achieve this goal.
facet-Based Browsing Taxonomic structures give users exactly one way to access information. Furthermore, the development of appropriate taxonomic structures (whether, e.g., class or SKOS keyword hierarchies) requires significant initial efforts. As a pay-asyou-go strategy, facet-based browsing allows to reduce the efforts for a priori knowledge structuring, while still offering efficient means to retrieve information. Thereby, facet-based browsing methods can provide similar functionality for semantically rich knowledge bases as tagging systems and tag clouds for Social Software applications. Facet-based browsing was first implemented for RDF data by the Longwell Browser.1 To enable users to select objects according to certain facets, all property values (facets) of a set of selected instances are analyzed. If for a certain property the instances have only a limited set of values, those values are offered to restrict the instance selection further. Hence, this way of navigation through data will never lead to empty results. The analyzing of property values though can be very resource demanding and time consuming. To still enable fast response times it can be beneficial to cache the results of of a property value analysis and to selective invalidate cache objects on updates of respective property values.
Semantically Enhanced Full-Text search OntoWiki provides a full-text search for one or multiple keywords occurring in literal property values. Since there can be several property values of a single individual containing the search string the results should be grouped by instances and ordered by frequency of occurrence of the search string. Search results may be filtered to contain only individuals which are instances of a distinct class or which are described by the literal only in conjunction with a distinct property (see Figure 4).
Enabling Social Semantic Collaboration
Figure 4. User interface for the semantic enhanced search in OntoWiki. After searching for “York” it is suggested to refine the search to instances with one of the properties swrc:address, swrc: booktitle or swrc:name
A semantic search has significant advantages compared to conventional full-text searches. By detecting classes and properties, contain matching instances, the semantic search delivers important feedback to the user how the search may be successfully refined.
data integration for sswes In this section, we give a short overview over approaches from the Data Integration realm, which can build a basis for the implementation of SSWEs. Since the early days of the Web, one of the most compelling visions has been to develop new systems that exploit the wealth of available information to answer new questions—highlevel, semantic queries—that are not directly answerable using a single document or data item. The Semantic Web represents the most widely promoted, modern version of this vision, but actually, as Tim Berners-Lee himself observes in Berners-Lee (2003), the Semantic Web is a particular methodology for attempting to achieve data integration—a topic studied previously in
0
the AI agents community (Arens, Chee, Hsu, & Knoblock, 1993; Friedman & Weld, 1997) and the data integration field (Chawathe et al., 1994; Levy, Rajaraman, & Ordille, 1996). Data integration is an incredibly challenging problem: data is both physically encoded and logically represented in many different ways, and “meaning” or “semantics” is highly dependent on a frame of reference. Over time, many of the physical encoding issues have been largely addressed through standardization; likewise for basic protocols for fetching data. Today, most data sources provide access in one of a handful of physical formats: a serialization hidden underneath JDBC drivers, HTML, comma-separated values, RDF, or XML. Data is often fetched using HTTP, perhaps layered over with Web Service protocols, as we see with many services from Amazon, Google, and so on. This leaves the hardest problems in the areas of semantics: obtaining semantic annotations for data items; determining a unified output representation for the data when it is combined; and converting the data from source to output. Each of these areas was originally addressed by asking the content creator or service builder to encode everything; but in recent years there has
Enabling Social Semantic Collaboration
been a trend towards incorporating Web 2.0-like ideas with a human in the loop.
semantic annotation Early work on information integration was divided into two classes of approaches: integration of databases focuses on settings where the data was already stored in relational tables or in objects, which had a considerable amount of metadata describing semantics; integration of Web sources focused on developing wrapper induction strategies (Kushmerick, Weld, & Doorenbos, 1997) for learning how to extract (and hence annotate) certain data items from Web pages. The Semantic Web has adopted a strategy that greatly resembles that of database integration: data items are annotated with a very rich set of metadata, including class relationships that are based on Knowledge Representation formalisms. In certain settings, however, we are beginning to see the emergence of Web 2.0-like ideas, such as collaborative tagging and instant gratification, in this space. The Mangrove project (Halevy, Etzioni, Doan, & Ives, 2003) focused on encouraging Web contributors to semantically annotate their pages (using a small set of predefined tags) by providing useful “out of the box” services that exploited these tags, such as organizational event calendars. To a significant extent, today’s tag-based Web sites follow a similar model, although to the best of our knowledge there has not yet been a focus on integrating tag-based services with query services that go beyond basic keyword querying.
Developing a Unified Output representation Most approaches to integrating data are instances of the so-called mediator architecture (Wiederhold, 1992): they build an “umbrella” layer and representation over disparate data sources. A challenge lies in developing the necessary unified schema or ontology to represent the combined
knowledge. In some cases, this is fairly straightforward as concepts align closely, but in other cases this can be a major endeavor. In recent years, there has been a focus on “lightweight” integration into commonly understood data representations: overlaid maps, timelines, itemized lists, simple visualizations of one or two attributes. Such target representations are limited in the questions they can answer, but for the right questions, their integrated views are very useful. The most common example of this approach is the plethora of map mashups available over Google Maps. However, recent research projects like SIMILE (Huynh et al., 2005) exploit very similar ideas using Semantic Web technologies. A complementary approach is to allow collaborative authoring of the target knowledgebase. One prime example of this is GoogleBase, which has an extensible set of item types and attributes, but which suggests a starting schema for most common categories of items. This establishes some regularity across all items of a related type. The Open Directory Project (dmoz.org) adopts a slightly different strategy, with a single Web site classification taxonomy that can be edited by any contributor.
Converting the data Probably the most challenging aspect of data integration is the process of actually combining the data. As described previously, some of the lower levels of this process have been largely alleviated, due to common data encodings and Web Service or HTTP interfaces. This leaves most of the emphasis on combining, restructuring, and translating attributes and classes from the source representation to the target. Traditional data integration achieves this using declarative query languages. The Semantic Web approach relies on expressing equivalences or subsumption relationships between classes in different knowledge bases; this works for many situations but cannot perform, for instance, mathematical
Enabling Social Semantic Collaboration
transformations such as unit conversion. For both of these cases, a variety of tools have been built to perform semi-automated schema matching (Aumueller, 2005; Doan, Domingos, & Halevy, 2001; Gal, Modica, & Jamil, 2004; Jian, Hu, Cheng, & Qu, 2005; Madhavan, Bernstein, & Rahm, 2001; McGuinness, Rikes, Rice, & Wilder, 2000; Noy & Musen, 2000); unfortunately, this is a very challenging problem, and hence such tools are somewhat prone to mistakes. Web 2.0 generally relies on mashups built using AJAX—Asynchronous Javascript And XML—which express the transformations using custom procedural code over XML data. Most mashups are highly effective, in part because they focus on simple, lightweight conversions with well-understood data. They are developed grass-roots-style, by third party programmers who wanted functionality not available elsewhere. The MOBS system (McCann et. al, 05) takes the schema matching approach and infuses it with community-based ideas, to great effect. MOBS relies on a large community of users to correct and refine schema mappings between sources, and it focuses on providing reward mechanisms for these users.
related work In addition to the references given in the preceding sections, we would like to exhibit here some work with regard to extending Social Software with semantic enhancements in the light of the earlier mentioned social communication patterns, that is, point-to-point, bidirectional, star-like, and net-like. Supplementary to these categories, local approaches which can be subsumed under the Semantic Desktop concept play a crucial role for integrated support of SSWEs. The project SemperWiki (Oren, 2005), for example, created a simple Wiki, combined with an RDF triple store for the desktop, which can function as a local basis
for content to be exchanged and distributed in a social, semantic collaboration network. Another example is semantically enhanced file systems such as SemDAV (Schandl, 2006) and TagFS (Bloehdorn et. al, 2006). The latter extends the file system metaphor with tags, while SemDAV’s aim is a deeper integration of Semantic Web technologies. Social Software founded on the point-to-point or bidirectional communication patterns is enhanced for example in McDowell et al. (2004) which provides multiple semantic enhancements for the traditional e-mail service. Franz and Staab (2005) show how semantic enhancements can be integrated into instant messaging. The group of star-like semantic social software is dominated by technologies which enrich textual information in news feeds and traditional Web pages with machine-interpretable semantics (e.g., for RSS (Hammersley, 2003) and ATOM (Nottingham & Sayre, 2005) or GRDDL (HazaëlMassieux & Connolly, 2005), RDFa (Adida & Birbeck, 2006) and Microformats (Khare & Celik, 2006) for Web pages). The by far largest group are net-like approaches, which can be categorized into (a) semantic enhancements for decentralized technologies like Wikis, Blogs, and P2P networks (e.g., Haase et al., 2004; Kager et al., 2004; Souzis, 2005), (b) Ontologies for the description of content in social networks (e.g., FOAF (Brickley & Miller, 2004) and SIOC (Breslin et al., 2006)), and (c) centralized services for specialized collaboration communities (e.g., flickr.com, del.icio.us and last.fm).
future researCh direCtions As we mentioned earlier, a pivotal Social Software concept is the collaborative tagging of content leading to folksonomies (i.e., taxonomies created by folks) (Golder et al., 2006). A folksonomy here is a system of weighted keywords emerged from a multiplicity of individually chosen keyword at-
Enabling Social Semantic Collaboration
tachments (i.e., tags) to content objects. Applied to the sphere of the Semantic Web the challenge is to employ human “swarm intelligence” in the spirit of tagging to create not just comprehensive but also consistent knowledge bases. Consistent here is meant less from a logical point of view than from the perspective of achieving an agreement in the user community. When knowledge bases are collaboratively developed by loosely-coupled communities a way to improve the consistency is the development of methodologies for moderation and decision processes within SSWEs. A field of future research are possible indicators for the degree of consistency. A different approach of tackling the consistency problem represents policies and access control mechanisms for accessing, editing, and annotating content. Often knowledge bases start as simple semantic networks, become increasingly rich thus resulting in taxonomies and class hierarchies and are finally enriched with logical axioms and definitions. Due to the variety of the possible expressivity to be considered, the formulation of policy models and access control strategies turns out to be difficult. In addition, policies should be adequate for a spectrum of knowledge bases with a varying degree of semantic richness. Another challenge, lying less in the scientific than the software engineering field, is to increase the flexibility and robustness of storage backends, libraries, and frameworks for the development of Semantic Web applications. In addition, standards for semantic widgets and user interface elements for SSWEs can support user acceptance and interoperability. Last but not least, economic aspects play a crucial role to make SSWEs a success. Due to the fact that semantic collaboration is in many cases not a direct business in itself, specific business models are needed which are focussed on services and products supporting the generation and curation of semantic content by communities.
referenCes Adida, B., & Birbeck, M. (2006). RDFa Primer 1.0 (Working Draft). World Wide Web Consortium (W3C). Arens, Y., Chee, C., Hsu, C.-N., & Knoblock, C. (1993). Retrieving and integrating data from multiple information sources. International Journal on Intelligent and Cooperative Information Systems, 2(2), 127-158. Auer, S. (2005, May 30). Powl – a Web based platform for collaborative Semantic Web development. In Scripting for the Semantic Web, CEUR Workshop Proceedings, CEUR-WS (pp. 135). Auer, S., & Herre, H. (2006). A versioning and evolution framework for RDF knowledge bases. In Proceedings of Ershov Memorial Conference. Aumüller, D. (2005a). SHAWN: Structure helps a wiki navigate. In Proceedings of the BTW-Workshop WebDB Meets IR. Aumüller, D. (2005b). Semantic authoring and retrieval within a wiki (WikSAR). In Demo Session at the Second European Semantic Web Conference (ESWC2005). Retrieved March 2, 2008, from http://wiksar.sf.net Aumueller, D., Do, H. H., Massmann, S., & Rahm, E. (2005). Schema and ontology matching with COMA++. In SIGMOD Conference (pp. 906-908). Bächle, M. (2006). Social Software. Informatik Spektrum, 29(2), 121-124. Berners-Lee, T. (2003, May 20-24). Keynote address: Fitting it all together. In 12th World Wide Web Conference, Budapest, Hungary. Berners-Lee, T., Hendler, J., & Lassila, O. (2001, August). Mein computer versteht mich. Spektrum derWissenschaft, 8, 42-49.
Enabling Social Semantic Collaboration
Bizer, C., Lee, R., & Pietriga, E. (2005, November). Fresnel – a browser-independent presentation vocabulary for RDF. In End User Semantic Web Interaction Workshop at ISWC 2005. Bloehdorn, S., Görlitz, O., Schenk, S., & Völkel, M. (2006). TagFS - tag semantics for hierarchical file systems. Brickley, D., & Miller, L. (2004). FOAF vocabulary specification FOAF Project. Chawathe, S. S., Garcia-Molina, H., Hammer, J., Ireland, K., Papakonstantinou, Y., Ullman, J. D. et al. (1994). The TSIMMIS project: Integration of heterogeneous information sources. IPSJ, 7-18. Dietzold, S., & Auer, S. (2006, June). Access control on RDFTriple stores from a semanticwiki perspective. In Scripting for the Semantic Web, CEUR Workshop Proceedings (pp. 183). ISSN 1613-0073. Doan, A., Domingos, P., & Halevy, A. (2001). Reconciling schemas of disparate data sources: A machine-learning approach. In SIGMOD Conference (pp. 509-520).
Halevy, A., Etzioni, O., Doan, A., & Ives, Z. (2003). Jayant Madhavan, Luke McDowell, Igor Tatarinov: Crossing the structure chasm. CIDR.. Hammersley, B. (2003). Content syndication with RSS. O’Reilly Associates. Hazaël-Massieux, D., & Connolly, D. (2005). Gleaning resource descriptions from dialects of languages (GRDDL). In World Wide Web Consortium (W3C). Jian, N., Hu, W., Cheng, G., & Qu, Y. (2005). FalconAO: Aligning ontologies with falcon. In Integrating Ontologies. Khare, R., & Çelik, T. (2006). Microformats: A pragmatic path to the Semantic Web. WWW ‘06. ACM Press (pp. 865-866). Kushmerick, N., Weld, D., & Doorenbos, R. (1997). Wrapper induction for information extraction. IJCAI, 1, 729-737. Lassila, O., & Swick, R. R. (1999, February 22). Resource description framework (RDF) model and syntax specification. In W3C Recommendation, WorldWideWeb Consortium (W3C).
Franz, T., & Staab, S. (2005). SAM: Semantics aware instant messaging for the networked semantic desktop. In Semantic Desktop Workshop at the ISWC2005, Galway, Ireland.
Levy, A., Rajaraman, A., & Ordille, J. (1996). Querying heterogeneous information sources using source descriptions. VLDB, 251-262.
Friedman, M., & Weld, D. (1997). Efficiently executing information-gathering plans. IJCAI, 1, 785-791.
Madhavan, J., Bernstein, P., & Rahm, E. (2001). Generic schema matching with cupid. VLDB, 49-58.
Gal, A., Modica, G., & Jamil, H. (2004). OntoBuilder: Fully automatic extraction and consolidation of ontologies from Web sources. ICDE, 853. Haase, P., Broekstra, J., Ehrig, M., Menken, M., Mika, P., Olko, M. et al. (2004). Bibster – a semantics-based bibliographic peer-to-peer system. In The Semantic Web – ISWC 2004 (pp. 122-136). Springer. LNI 3298.
McGuinness, D., Fikes, R., Rice, J., & Wilder, S. (2000). The chimaera ontology environment. AAAI/IAAI, 1123-1124. Nottingham, M., & Sayre, R. (2005). The atom syndication format. The Internet Engineering Task Force (IETF). Noy, N., & Musen, A. (2000). PROMPT: Algorithm and tool for automated ontology merging and alignment. AAAI/IAAI, 450-455.
Enabling Social Semantic Collaboration
Oren, E. (2005). SemperWiki: A semantic personal wiki. Semantic Desktop Workshop at the ISWC 2005, Galway, Ireland.
Leuf, B., & Cunningham, W. (2001). The wiki way. Amsterdam: Addison-Wesley Longman.
Schandl, B. (2006). SemDAV: A file exchange protocol for the semantic desktop. CEUR-WS, 202.
McCann, R., Kramnik, A., Shen, W., Varadarajan, V., Sobulo, O., & Doan, A. (2005). Integrating data from disparate sources: A mass collaboration approach. ICDE, 487-488.
additional reading
McDowell, L., Etzioni, O., & Halevy, A. (2004). Semantic e-mail: Theory and applications. Journal of Web Semantics, 2, 153-183.
Breslin, J., Decker, S., Harth, A., & Bojars, U. (2006). SIOC: An approach to connect Web-based communities. The International Journal of WebBased Communities, 2, 133-142. Golder, S., & Huberman, B. H. (2006). Usage patterns of collaborative tagging systems. Journal of Information Science, 32(2), 198-208. Karger, D., & Quan, D. (2004). What would it mean to blog on the Semantic Web? In The Semantic Web - ISWC2004 (pp. 214-228). Springer. LNCS 3298. Kroetzsch, M., Vrandecic, D., & Völkel, M. (2005). Wikipedia and the Semantic Web - the missing links. Wikimania, Frankfurt, Germany.
O’Reilly, T. (2005). What Is Web 2.0 - design patterns and business models for the next generation of software. Retrieved March 2, 2008, from http://www.oreillynet.com/pub/a/oreilly/ tim/news/2005/09/30/what-is-web-20.html Shirky, C. (2003, April). A group is its own worst enemy. In Rede zur ETech Conference. Retrieved March 2, 2008, from http://www.shirky.com/writings/group_enemy.html Souzis, A. (2005). Building a semantic wiki. IEEE Intelligent Systems, 20(5), 87-91.
endnote 1
http://simile.mit.edu/longwell/
Chapter II
Communication Systems for Semantic Work Environments Thomas Franz University of Koblenz-Landau, Germany Sergej Sizov University of Koblenz-Landau, Germany
introduCtion The paradigm of a flexible environment that supports the user in producing, organizing, and browsing the knowledge originates in the early 1940s, a long time before the first personal computers and new communication tools like the Internet became available. The conceptual design of Vannevar Bush’s memex (Bush, 1945) (an acronym for Memory Extender) is probably the most cited (e.g., Gemmell, Bell, Leuder, Drucker, & Wong, 2002) and criticized (e.g., Buckland,
1992) representative of such early conceptual work. In his article, Bush described the integrated work environment that was electronically linked to a repository of microfilms and able to display stored contents and automatically follow references from one document to another. A number of visionary ideas from this early conceptual work can be recognized in state-of-the-art information systems (cross-references between documents, browsing, keyword-based annotation of documents using the personal “codebook,” automatic generation of associative trails for content summarization, etc.).
Copyright © 2008, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
Communication Systems for Semantic Work Environments
Today we have entered the knowledge age where economic power or wealth is based on ownership of knowledge, Haag, Cummings, and McCubbrey (2002) and the ability to utilize knowledge for the improvement of services or products. Knowledge workers outnumber any other kind of worker already in highly developed economic systems. Their work is characterized by complex human-centric or personal work processes (Kogan & Muller, 2006) describing information intensive and complex tasks comprising of the creation, retrieval, digestion, filtering, and sharing of (large amounts of) knowledge. We understand a Semantic Work Environment (SWE) as an environment implemented by information technology (IT) that supports such complex knowledge work by exploiting the semantics of information. Accordingly, an SWE is based on methods and tools that allow the extraction, representation, and utilization of the semantics of information in order to provide enhanced IT support for the knowledge worker. To a certain extent, the memex can be considered as a microfilm-based precursor to SWEs. Communication is one of the tasks of the knowledge worker as it denotes the exchange of information and transfer of knowledge so that it is vital for any collaborative human work, for example, for coordinating work, reporting on work progress, or discussing solutions and problems. Efficient communication infrastructure is probably one of the key differences of modern SWEs in contrast to isolated memex-style solutions from the past. As an example, we may consider the common scenario of publishing research results. Basically, the preparation steps for a new scientific publication has not changed much since memex. Both Vannevar Bush and (roughly 70 years later) authors of this chapter had to exchange ideas for the new proposals with colleagues, discuss the proposed solution, sketch the outline of the publication, make responsibility assignments for content delivery, request reviews, and iteratively improve
the proposal, collaborate with publishers and other author groups, and finally make the contribution public. In the following sections, we will use this sample scenario for the comparison and illustration of various communication mechanisms. Internet and the World Wide Web (WWW) provide an infrastructure on top of which a variety of communication channels have been established such as e-mail, chat, Web logs (blogs), wikis, and instant messaging. We refer to such a communication channel as the communication protocol and the infrastructure on which a protocol is implemented. For the human utilization of a communication channel, communication clients or tools are employed. We refer to the combination of both as communication system in the following. Communication systems—predominantly those enabling asynchronous textual communication (e.g., e-mail)—are widespread today and have complemented former ways of communicating (e.g., mail). Obvious advantages of such systems are the rate at which messages are delivered between communication partners and the costs for the delivery. These advantages foster distributed work and virtual communities that consist of collaborators that are located across the planet. However, not only collaborators that are physically or timely separated employ IT systems for communicating, colleagues located on the same floor working for the same departmental group use them as well. As we show, communication systems also take part in different personal information management strategies rather than being just used for communicating. Noticing the importance of communication for knowledge work, this chapter deals with the role of communication systems with respect to knowledge work. At first, we introduce different communication systems to indicate their different utilization and role within knowledge work. Next, we develop requirements of communication systems for SWEs by a discussion of how SWEs support the knowledge worker and confront conventional communication tools and channels
Communication Systems for Semantic Work Environments
with these requirements. We then point to several research works that contribute to enhanced communication systems that support knowledge work better. We accommodate such research and give an outlook by a visionary description of the scenario introduced before and end the chapter with a conclusion.
CommuniCation systems In this section, we give an overview of currently available computer-based communication systems and point out their utilization for work. For the comparison of the different communication systems, we consider the following aspects: •
•
•
Symmetry of exchange: This category denotes the directionality of communication. Asymmetric means that there are the roles of an addresser and addressee where the latter cannot communicate back or only in a limited way, for example, one can reply to a Web log by (1) posting a comment that is, however, less visible and prominent on the Web page, (2) by writing one’s own Web log that refers (links) to the initial Web log, or (3) by contacting the blog author using another communication channel. Synchrony: Synchrony relates to the time that passes until a message is perceived by the addressee. Asynchronous communication is characterized by longer delays between utterances or messages while in synchronous and real-time communication, messages are immediately perceived by the addressee, for example, in Internet telephony, words of a sentence are perceived even before the sentence is closed. Communication media: Different media types such as text, image, audio, and video are supported by different communication channels.
While the communication channel defines communication properties such as synchronism or media support, communication tools build upon channels to provide means to convey information via a communication channel but also means to deal with communicated information. We pay attention particularly to the latter as information management features and data models of communication tools are relevant for the analysis of their role within knowledge work as to be supported by SWEs.
electronic mail Electronic mail (e-mail) enables asynchronous, primarily textual communication and is a well analyzed communication system: e-mail is not only employed as a pure communication means but also for time and task management (Mackay, 1998). E-mail overload (Whittaker & Sidner, 1996) summarizes the difficulties in organizing increasingly many e-mails and various kinds of e-mails such as private, work-related, spam, and important ones. It has further been examined how different working backgrounds of people influence the utilization of e-mail, observing that there are significant differences between user groups (Danis, Kellogg, Lau, Dredze, Stylos, & Kushmerick, 2005), for example, in the way different workers structure and classify their e-mails. As a commonly acknowledged communication means, e-mail became a source of knowledge and takes part in the creation of new knowledge making it an important knowledge management tool (Lichtenstein, 2004). In our previously introduced sample scenario, e-mail communication would have a wide range of possible issues: thematically focused discussions, tracking of document evolution, content sharing, and delivery. As e-mails are also used for coordination of tasks or work, they even inherit process knowledge.
Communication Systems for Semantic Work Environments
Mailing Lists and News Groups Mailing lists share the infrastructure of e-mail and allow group communication via e-mails addressed to a mailing list. A mailing list server allows for further administrative functions such as membership control. Furthermore, mailing lists can be moderated by users, that is, some human acts as a filter for posted messages and decides on the delivery of postings. News groups are based on a different technical infrastructure than mailing lists and have less administrative features. However, they closely resemble mailing lists as they also enable group communication by postings to particular news groups that are organized by a topic hierarchy. In our sample scenario, mailing lists and news groups could be used for sharing of contents (e.g., a new update of the paper draft becomes available) and multicast notifications of user groups (all authors are notified about the new submission deadline). In unmoderated cases, both mailing lists and news groups are open to flaming, that is, the posting of violent or rude message content (Kim & Raja, 1991; Mabry, 1998). A benefit of such openness is that it enables lurking, that is, a passive, read-only participation in conversations, for example, to be aware about current topics and issues addressed by a particular group (Nonnecke & Preece, 2000).
instant messaging Instant messaging (IM) enables near-synchronous, textual communication where users see messages nearly immediately after they have been submitted by communication partners. Next to information exchange that is often characterized by informal communication in IM, it is also used for coordinative tasks such as preparing media switches, for example, initiating a phone call or face-to-face meeting (Nardi, Whittaker, & Bradner, 2000). In work environments, IM
is primarily used for work related and complex conversation (Isaacs, Walendowski, Whittaker, Schiano, & Kamm, 2002). For instance, in our sample scenario, instant messaging could be used by two authors for collaborative online writing of the publication and discussion of its scientific issues. Two main types of instant messaging users have been identified in Isaacs et al. (2002): heavy users who employ IM for work and work related conversation and light users who, rather, use IM for coordinating and whose conversations are shorter and less complex.
Chat Systems Chat systems such as Internet relay chat (IRC) are closely related to IM concerning synchrony and exchange symmetry. While both IM as well as chat systems allow one-to-one conversation as well as group conversation, chat systems are focused on group conversation (e.g., prereview meeting of authors and editors of a scientific journal). Similarly to IM, studies about the utilization of a chat system indicate that in working environments, they are primarily used for work related conversation (69%) and for awareness of presence (Handel & Herbsleb, 2002). In contrast to IM clients, chat clients are usually not as intrusive, for example, they do not attract user attention on any new message as IM clients usually do it. Following a chat conversation, however, may become difficult since related posts (e.g., question-answer) may be disrupted by interleaving messages (Herring, 1999).
web logs Web logs (blogs) are frequently updated Web pages that contain chronologically ordered sections written by authors of a Web log. Thus, they present an asynchronous and asymmetric communication system. The content and purpose of blogs varies significantly from personal diary-like entries to
Communication Systems for Semantic Work Environments
Figure 1. Types of blogs Personal Quadrant I Online Diaries
Quadrant II Support Group
Individual
Community
Quadrant III
Quadrant IV
Enhanced Column
Collaborative Content Creation Topical
column-like ones. In Krishnamurthy (2002), that diversity is illustrated by four quadrants of blog types (Figure 1). One distinction is made along the content of blogs ranging from blogs dealing with primarily personal issues and those that deal with topics of general interest, for example, politics. Another axis distinguishes between the multiplicity of authors within a blog ranging from individually maintained blogs to community blogs that contain entries from many different authors. Most blogs are individualistic and self-expressive rather than being interactive and dedicated to general topics (Herring, Scheidt, Wright, & Bonus, 2005). Obviously, Web logs are an efficient means for Web publishing enabling one to many communication. As pointed out in Efimova and de Moor (2005), however, many-to-many conversations can be established by interlinked Web logs that reference each other and have been written by different authors. Beyond the borders of personal information management, blogs are used by many software development portals, research projects, and product vendors for “newsticker”-like publishing and sharing of announcements, new product releases,
0
or major events. In this sense, they can be also considered as a special case of thematically focused notification mechanism.
wikis Wikis are linked Web pages (wiki pages) that are provided by a wiki system that offers user management, a Web-based editor for wiki pages, and versioning of pages. In contrast to Web logs, wiki pages are commonly edited by multiple users. Thus wikis also allow collaborators to communicate by editing a wiki page, that is, by either reading the changes and additions of others or making changes oneself. Due to the simplicity of use and content creation, problem-oriented wikis are the state-of-the-art means for capturing and sharing of knowledge in thematically focused communities and complex work environments. From the background of our application example, wikis are widely used in practice for collaborative work on scientific publications (including discussion tracks on research issues, collecting technical knowledge like questions of formatting, and format conversions, etc.). Due to that collaborative nature, wikis are regarded as a powerful knowledge management tool (Wagner, 2004).
Communication Systems for Semantic Work Environments
Audio and Video Based Communication Systems Internet telephony applications enable synchronous, symmetric audio communication over the Internet based on voice over IP (VoIP) protocols. Trust building occurs faster in communications over rich communication media such as audio and video conferencing than compared to other media (Bos, Olson, Gergle, Olson, & Wright, 2002), for example, text-based chat. Besides one-to-one communication, conference modes that enable many-to-many communication are also possible and provide a further means to support group collaboration that can lower group dependability (Kane & Luz, 2006). Internet phone calls and phone conferences can be recorded and such recordings are sometimes published (e.g., the track of a joint phone conference between authors and publishers of the scientific journal). Such publication is often called audio blogging
attributing to the symmetry of content exchange that is one-to-many similar to regular Web logs. Therefore, audio blogging also resembles Internet radio as another audio-based one-to-many communication channel. Next to audio communication, there exists also audio-visual communication where communication partners can see and listen to each other. Prior studies have shown that video conferencing does not increase the quality of work compared to the use of phone and e-mail based communication. For the negotiation of meaning, however, video conferencing is assumed to be beneficial for particular user groups, for example, non-native speakers benefit from it (Veinott, Olson, Olson, & Fu, 1999). Recently, video blogging became popular by Web sites like YouTube1 that allow users to upload videos to a server to share them with others. Like audio blogging, video blogging allows to use commonly synchronous video conferencing in an asynchronous manner.
Table 1. Comparison of communication channels E-mail Mailing Lists and News Groups Instant Messaging Chat Systems Web log Internet Telephony Audio Blogging Video Conferencing Video Blogging Internet Radio Wiki
Symmetry of Exchange
Synchrony
Media
Symmetric
Asynchronous
Text Image (video, audio)
Symmetric
Asynchronous
Text Image (video, audio)
Symmetric
Synchronous
Text (Image, video, audio)
Symmetric
Synchronous
Text (Image, video, audio)
Asymmetric
Asynchronous
Text, Image, video, audio
Symmetric
Synchronous
Audio (Text, Image, Video)
Asymmetric
Asynchronous
Audio, Text, Image,
Symmetric
Synchronous
Video, Audio
Asymmetric
Asynchronous
Video, Audio, Image, Text
Asymmetric
Asynchronous
Audio
Asynchronous
Text, Image (video, audio)
Symmetric
Communication Systems for Semantic Work Environments
Discussion The previous sections indicate the varying suitability of channels for different tasks such as work coordination and conversation about work, but also for tasks not directly related to information communication such as preparation of media change and the perception of presence and awareness. Moreover, the relation between communicated information and work strategies has been indicated, for example, identifying that e-mails are often used as to-do items and that the e-mail inbox is often employed for task and to-do tracking. In Table 1, we summarize the analysis given in this section. The media column lists the media types supported by a channel ordered by their frequency of use in the channel. Media that can be transported via a channel but which is not supported by conventional communication tools, that is, media that is not directly presented by a communication client, is put in brackets.
towards semantiC work environments In this section we briefly introduce the notion of personal work processes and complex tasks as they are to be supported by SWEs. We then develop requirements for communication tools based on those notions and confront current tools with such requirements.
personal work processes and implications for swes Personal knowledge work is characterized by personal work processes which describe complex, information intensive work. At the end of the successful execution of a personal work process stands the achievement of a task. We refer to such a task as a complex task as it commonly comprises several subtasks, for example, information search,
filtering, selection, and combination of information, reservation of resources, communication, creation, and conveyance of information. SWEs are dedicated to support the knowledge worker and thus the personal processes that describe their complex tasks. In the following, we elaborate on the implications for communication systems that follow from the requirements on SWEs. An example of a common complex task is the publication of research results such as introduced in the beginning of this chapter. In the context of research publication particular contextual views are adopted, for example, people are seen as producers of research papers which have a lifecycle and are developed and manipulated collectively. In another example of a complex task—the planning of a conference—people are seen as meeting participants, and research papers are associated to time slots and organized into conference sessions. The example indicates that the same information is used for different purposes and has different roles depending on the working context, that is, the context constituted by a complex tasks. Accordingly, communication systems of SWEs should enable such cross-contextual utilization of information, meaning that communicated information should be available just as any other information. Users should be able to associate it to other information, reuse it, and exploit it for different tasks, not only in the context of communication. Flexible information classification schemes need to be supported by SWEs that allow knowledge workers to retrieve and to file information with respect to their working context. Moreover, classification issues such as pointed out by e-mail overload (Whittaker & Sidner, 1996) call for enhanced support and guidance in the classification of communicated information, for example, automatic e-mail classification. Such classifications cannot be limited to a particular application but need to be reusable and available across applications as knowledge workers need to organize information that they receive from different sources or have created themselves.
Communication Systems for Semantic Work Environments
Different communication channels support different media differently and are advantageous for particular communication related tasks. SWEs should allow the knowledge worker to focus on what to communicate to whom in the most effective way. The choice of the channel should be the result of what is communicated and to whom it shall be communicated. Accordingly, a cross-channel communication environment is required that allows for conversations that utilize multiple channels. The complexity of personal work processes and the number of such processes that knowledge workers deal with in parallel demand guidance in the conduction of such processes. The knowledge worker needs to know what has been done within the different processes, which steps are pending, and what are the associated timelines. Accordingly, communication systems need to support personal work processes, for example, by the integration with tools that allow a user to manage and track them. Any information about process steps needs to be available for later review and reuse, for example, to review the basis of a decision made in the past. Communication tools need to make communicated information persistent for both retrieval and archiving purposes. Moreover, previous exchanges may also provide contextual information about conversations that span large time intervals of several weeks or months. The single knowledge worker will certainly collaborate in teams with multiple coworkers. Accordingly, the implications outlined in the prior paragraphs need to be fulfilled with respect to collaborative work in a networked environment.
Current Shortcomings Conventional communication tools and channels do not fulfill many of the requirements pointed out before. Many tools support a single communication channel only and prevent more effective, cross
channel conversations, for example, the answering of an e-mail by a quick follow up explanation using chat or instant messaging. If such cross channel conversations cannot be tracked with communication tools, conversational threads are cut which complicates later recall of conversations. Recently, tools became available that integrate some communication channels: for instance, a merge of instant messaging and Internet telephony tools can be noticed as many instant messengers support telephony today while phone tools often support instant messaging (e.g., Skype). There are also tools that integrate instant messaging and e-mail, for example, Google mail and talk as well as the Skype-plugin for the Thunderbird mail client. Today’s communication tools focus on the communication task, that is, they are tailored for information exchange. Thus they are not well suited for all the tasks and processes related to management work that knowledge for which workers might like to employ them. As they also do not provide the communicated information in a standardized format that allows further utilization; they ignore the known role of communicated information for work processes, time and task management. Limited information reuse denotes a further shortcoming caused by the missing interoperability of communication clients and other work tools. Communicated information is often not easy to reuse without the loss of context, for example, saving an e-mail attachment to the file system results in the loss of the relation to the e-mail. Analog to the previous example, copying parts of a message into the clipboard provided by a computer desktop and then pasting it into another application also cuts the relation between the copied text and its origin. Such information, however, can be used for information browsing and information search, for example, to present a user with the origin of some piece of text or with the e-mail that was associated with the attachment that has been saved to the file system for editing.
Communication Systems for Semantic Work Environments
Many communication tools lack means to classify communicated information. Most e-mail clients allow a user to organize e-mails into folder hierarchies. These, however, allow the user to classify e-mails only with respect to one criteria. Back in our example, the lead author of a paper may classify e-mails by the person who sent them. To keep track of e-mails related to the production of the research paper the lead author may want to classify e-mails beyond the sender by their topic. Such multiclassification, however, that allows the user to summarize information to suit different tasks is only weakly supported by current communication clients. Some clients allow the user to flag e-mails with tags such as to-do but they lack efficient retrieval support based on such tags or prevent the user from associating multiple such tags with a single e-mail. Moreover, classification schemes reside within the application and cannot easily be shared outside, for example, to classify information dealt with in further applications. Still, many communication tools omit automatic storage of communicated information and thus also miss support for the retrieval and archiving of prior work. Such features are clearly valuable for the knowledge worker who needs to
track what has been done as part of which complex task, for example, the author of a research paper wants to recall the conversation where coauthors decided on the inclusion or deletion of a particular paragraph. Table 2 summarizes the discussion of this section by listing current communication channels and tools with respect to the work relevant properties mentioned here.
researCh enhanCing work support of CommuniCation systems The analysis of the previous section has developed shortcomings of current communication systems and stated requirements for enhanced work support. This section gives brief pointers to research contributing to overcoming shortcomings of current communication systems. It starts with a section pointing at research towards enhanced management of communication data. The next section deals with research contributing to enhanced support for personal processes and
Table 2. Comparison of communication tools and channels User-Defined Classification
Retrieval
Reuse and Referencing
E-mail, Mailing Lists, News Groups
Folder Hierarchies, Query Folders
Search, Folder Browsing, Ordering by Property
Forward, Inline Reply, File System Export, Clipboard, To Do (MS Outlook™)
Instant Messaging
Often predefined Classification by Sender or Time
Search, Ordering by Property
File System Export, Clipboard
Chat Systems Weblogs
[1] Browser Bookmarking, Web log Tagging (e.g. Technorati)
[2] Web Search, Bookmark and Tag-based Browsing
File System Export URL Referencing, File System Export, Clipboard
Internet Telephony
[1]
[2]
File System Export
Video Conferencing
[1]
[2]
File System Export, Clipboard
Audio and Video Blogging
Tagging (e.g. YouTube)
Browsing by Tag/User/Date/ Genre, Text Search
URL Referencing
Wiki
Arbitrary classification, e.g. by setup of link page
Wiki Search, Web Search, Browsing
URL Referencing, File System Export, Clipboard
[1] Classification only possible outside client, e.g. through file system export [2] Commonly no built-in retrieval support. Retrieval possible through file system search and browsing
Communication Systems for Semantic Work Environments
is followed by a section that indicates different research tools for communication that enable the creation of semantic metadata. We then point out different vocabularies to represent such metadata, present research about trust based communication, and overview work on peer-to-peer technology towards communication support.
Management of Communicated information Cole and Stumme have been working on a Conceptual E-Mail Manager (CEM) (Cole & Stumme, 2000). CEM addresses the issue of e-mail classification we pointed out. The main difference in comparison to common e-mail management relies in a multihierarchy storage in contrast to today’s commonly used tree structuring. Each e-mail is seen in a formal context that assigns a set of catchwords to each e-mail. Additionally, a hierarchy for the set of catchwords exists that is used to order the information. Conceptual scales are provided as a mechanism to group related information so that different views of messages can be created. Their implementation is able to visualize concept lattices (Cole, Ecklund, & Stumme, 2000) for any chosen scale. An example of a further research prototype that also addresses the issue of e-mail overload is ContactMap (Whittaker et al., 2004). In contrast to CEM, ContactMap is an approach to simplify classification and retrieval of messages by a different user interface design. ContactMap provides a user interface to contact data where each contact is presented by an image. Such contact images are presented in a two dimensional area and can be grouped, marked, and arranged within this area. As a result, awareness of groups and contacts is increased and access to messages via contacts is simplified through the additional visual cues provided by the system. The Small World Instant Messenger (SWIM) developed by Zhang and Van Alstyne (2004) describes an approach to integrate interpersonal
aspects in communication systems. SWIM is based on previous work by Watt, Walther, and Nowak (2002) dealing with searchability of social networks on the one hand as well as work by Isaacs et al. (2002) presenting an empirical study of over 21,000 IM conversations by 437 users. SWIM builds a user profile based on the user’s homepage and/or bookmarks to conduct information search on social networks. We pointed out that some communication systems lack persistency support for communicated messages. The communication system developed by Watts, Dodds, and Newman (2002) is an approach to develop asynchronous communication for video as communication medium thus also achieving persistency for video mediated communication. Their system aims at the combination of the advantages of multi modal face-to-face like communication with the advantages of asynchronous communication. The system allows communication via video messages that are made persistent for later retrieval and viewing by an addressee that can also answer asynchronously by further video messages.
Process Support The issue of reuse of communicated information for time and task management is treated by Taskmaster (Bellotti, Decheneaut, Howard, & Smith, 2003), a research tool that provides a solution for aligning e-mail as a communication means and its exploitation for task management. Belotti et al. (2003) developed Taskmaster as an application that is based on so called thrasks. A thrask summarizes a task and its associated e-mails and attachments. The developed application represents e-mails within the context of its related task and lets users directly view and order tasks together with their associated e-mails and attachments. Khoussainov and Kushmerick (2005) also address time and task management issues with respect to e-mail management, however, by a very different approach compared to Taskmaster.
Communication Systems for Semantic Work Environments
Khoussainov and Kushmerick (2005) present how machine learning techniques are applied to automatically classify e-mails by tasks. They also worked on a formalization of e-mail activities and the application of machine learning to identify the structure of such activities (Kushmerick & Lau, 2005). McDowell, Etzioni, and Halevy (2004b, 2004a) focus on Semantic E-mail Processes (SEP) to provide a solution to the challenge of missing process support in current e-mail tools. They present a template-based approach to define SEPs which allow the user to specify more or less complex tasks such as event planning with much less lines of code/data than implementing the process in a programming language. Once such process is defined in that it can be executed semi-automatically, for example, answers to a meeting invitation are interpreted automatically recognizing rejections and positive replies that are then used to execute further actions. QuickML (Masui & Takabayashi, 2003) is an example of enhanced process support and group communication. QuickML allows the user to build mailing lists in an ad-hoc fashion by providing a service that allows a user to initiate and maintain a mailing list simply by sending e-mails to the service. QuickML limits administrative overhead and thus fosters group collaboration through e-mail. The Loops system (Erickson et al., 2006) is a chat system for group collaboration providing—next to a chat communication channel—several enhancements such as a so-called social proxy which is a visual user interface that provides presence information about people. Unlike conventional chat systems, chat messages are persistent in Loops so that previous conversations can be tracked and asynchronous communication is possible. Loops also allow for multichannel communication by including a bulletin board that resembles one-to-many communication and allows the user to make certain information more
prominent than would be possible by persistent chat messages. The Buddyspace (Vogiazou, Eisenstadt, Dzbor, & Komzak, 2005) instant messenger is a research prototype that offers enhanced awareness and presence features, for example, the representation of a buddy list as a map that shows the location and presence status of buddies. Furthermore, Buddyspace allows for more sophisticated presence information allowing to distinguish between different presence information for different groups of buddies, for example, a user can set the status online for the group of coworkers, while simultaneously appearing as not available for another group.
Creating Semantic Communication metadata Information reuse and retrieval for information communicated by Web logs is improved by semantic blogging, as dealt with in Möller, Bojars, and Breslin (2006). Semantic blogging denotes an enhancement of conventional blogging that allows the user to integrate semantic meta data about things mentioned in a blog entry, for example, information about a person or an event. Such semantic meta data can be automatically extracted by appropriate blog readers so that the contained information can be immediately reused by the reader that would usually be required to manually enter given event information into his calendar, or some person’s contact information into his address book. Similar to semantic blogs, semantic wikis (Fischer, Gantner, Rendle, Stritt, & SchmidtThieme, 2006; Oren, Breslin, & Decker, 2006; Völkel, Krötzsch, Vrandecic, Haller, & Studer, 2006; Wagner, 2004) augment standard wiki text with semantic meta data. While wikis are a tool for collective information publishing the underlying main concept of interlinked content in the form of wiki pages makes wikis also a tool
Communication Systems for Semantic Work Environments
for various PIM tasks. Exploitations of semantic wikis are similar to those of semantic blogs, allowing tighter integration with desktop applications such as address books or calendars. Beyond that, semantic metadata in wikis also improves data management features allowing for sophisticated search functionalities and dynamic generation of aggregation pages that need to be edited manually and are static in conventional wikis. For instant messaging communicating, two different approaches are given by the semantics aware messenger (SAM) (Franz & Staab, 2005) and the instant messaging server Nabu (Osterfeld, Kiesel, & Schwarz, 2005). While SAM intercepts conversations at the instant messaging client to store semantic metadata about the conversations, Nabu extracts similar semantic metadata on the server side. Both approaches generate semantic metadata to enable enhanced management and reuse of communication data. Approaches like sTex2 and OntoOffice3 stand for similar solutions dedicated to supporting metadata creation in the context of text processing. The tools provided by the associated research projects enable to add semantic metadata to Latex documents and Microsoft Office documents at the time of their creation.
Representing Communication Next to the development of methods and tools presented above, there is also research on different vocabularies to semantically represent metadata relevant in communication. The Friend-of-afriend4 vocabulary is one such vocabulary defining classes and properties to represent persons, their contact details, affiliations, and social relationships. Further examples of similar vocabularies that allow the user to represent persons and their contact details are the vCard ontology5 and the W3C PIM ontology.6 SIOC (Breslin, Harth, Bojars, & Decker, 2005) provides a vocabulary and tools concentrating on representing public communication via mailing
lists or blogs and its relation to communities and topics. Among others, SIOC includes an ontology for representing data produced by conversations via different communication modes such as blogs, forums, and mailing lists. The framework for cross-context semantic information management (X-COSIM) (Franz, Staab, & Arndt, 2007) includes the X-COSIM reference ontology (X-COSIMO) to align information expressed with different domain ontologies such as described before. Based on a context-independent and formally consistent representation of information in X-COSIMO, information can be reused across desktop applications to support personal processes as described.
Security and Trust Communication channels offer an efficient means for certain types of communication. They raise, however, also new issues concerning trust and security. Decisions about whether someone should be allowed to access some information are partly based on how much we trust a particular person, or even how much we trust a particular person given a specific context. Dependent on the expertise of a person on a particular field, we may trust a person with respect to that field while distrusting the same person about other fields, for example, we might trust a computer scientist when she talks about programming languages but distrust her when it comes to cooking advices. Golbeck and Hendler (2005) developed algorithms for inferring trust relationships between individuals that are not directly connected in a social network. They also provide an extension for the Foaf vocabulary to represent trust values between persons and have developed an e-mail client called TrustMail, which adds trust ratings to e-mails for sorting and filtering them based on such ratings.
Communication Systems for Semantic Work Environments
peer-to-peer The research on decentralized, self-organizing infrastructures has been motivated by increasing popularity of peer-to-peer (P2P) frameworks and applications. Recent P2P information systems usually build on top of structured overlay networks like Chord (Stoica, Morris, Karger, Kaashoek, & Balakrishnan, 2001), CAN (Ratnasamy, Francis, Handley, Karp, & Schenker, 2001), Pastry (Rowstron & Druschel, 2001), or P-Grid (Aberer, Punceva, Hauswirth, & Schmidt, 2002) and provide scalable mechanisms for knowledge sharing and information dissemination. Almost all of the mentioned systems maintain distributed indexes that are based on various forms of distributed hash tables (DHTs) and support mapping from keys associated with managed objects (e.g., files, words, concepts, topics of interest) to corresponding network locations (e.g., peers subscribed for a topic of interest, or nodes that contain matching files). In particular, this infrastructure has been adopted for reliable publish/subscribe (e.g., Rowstron, Kermarrec, Castro, & Druschel, 2001) and multicast (e.g., El-Ansary, Alima, Brand, & Haridi, 2003; Merz & Gorunova, 2005) communication in self-organizing, decentralized environments.
CommuniCation support in future swes Communication tools of future SWEs consolidate multiple research works by exploiting machine interpretable semantics of communicated information to serve several work-supporting features. We exemplify them based on a visionary version of the research publication scenario we used throughout the chapter. Let John be a scientist that prepares a publication together with his colleague Mary. First, John creates the rough draft of the paper structure.
The annotated paper outline is used by his SWE to derive a new major task “publication” and a number of corresponding “subsection” subtasks. The work environment creates a new semantic wiki for collecting publication-specific details and resources. In the next step, the environment uses John’s semantic e-mail archive and earlier task descriptions in order to generate suggestions for co-authors that work on the same topic and collaborated with John in scientific writing in the past. The proposed recommendations are ordered by estimated relevance and presented to John in the task management section. John assigns writing of the evaluation section to Bob and asks Mary to be the internal reviewer of the proposal. The environment automatically notifies Mary and Bob about new responsibilities using annotated e-mail that also contains further details and references specified by John. When communication clients of Bob and Mary receive the notification, they automatically insert new tasks into their personal to-do tracker. Furthermore, SWE generates the thematically focused work environment for Bob and automatically includes related publications, formatting guidelines and templates, locally stored relevant research results, and the calendar with deadlines into this view. Bob uses this information in order to fulfill the task. During writing, he adds further resources (charts, figures, text) to the personal work environment. These resources are seamlessly shared between partners through associated semantic wiki. Once finished, Bob marks the task completed. The notification is automatically sent to others. The next day, Bob and Mary use cross-channel group communication tools (chat, phone, and shared whiteboard) to discuss the evaluation section. The captured records are automatically summarized, annotated by significant keywords and phrases, and persistently added to the semantic wiki of the paper draft for later references. John exploits the track of conversations based on person, topic, or task to retrieve messages relevant for his work.
Communication Systems for Semantic Work Environments
In the next days, John, Mary, and Bob add a number of further corrections and improvements to the evaluation section. After each update, detailed provenance information is generated and persistently stored. This allows John to keep track of authorship and reasons for all changes made. After submission of the publication, the similar work environment is used by conference organizers, reviewers, and authors in order to exchange notifications, request further explanations and clarifications during the review process, give reasons for further improvements, and finally to prepare the camera-ready release of the accepted publication. Our sample scenario indicates that a significant requirement for SWEs is that tools are interoperable, that is, that information created and processed by one tool (or person) needs to be available for further processing and reuse with potentially different applications and user groups. For this reason, the corresponding communication systems denote an important building block of future SWEs.
diversity of research disciplines that contribute to enhancements of communication systems show that diverse aspects need to be considered in the design of better communication tools. The discussion also revealed that supporting knowledge work means to take a cross tool perspective as information reuse and work dependent conceptual views into information occurring frequently, for example, when some information is regarded as a message in a communication context and as a task in a process management context. Research related to the social semantic desktop (Decker, 2006) takes a cross tool perspective and summarizes research towards enhanced support for personal knowledge work.
aCknowledgment This work was funded by the X-Media project (www.x-media-project.org) sponsored by the European Commission as part of the Information Society Technologies (IST) programme under EC grant number IST-FP6-026978.
ConClusion referenCes In this chapter, we presented a view into communication systems with respect to work environments, in particular SWEs. We have indicated that sole information transfer denotes only one of the many utilizations of IT-based communication systems. Notably, communication systems play an important role in work processes. Conventional communication systems lack sufficient support for such utilizations and we discussed what the requirements for improved communication systems are and what shortcomings conventional systems have. We gave examples of ongoing research from different research disciplines ranging from machine learning to user interface design and semantic Web research that all work towards an improvement of communication systems. The
Aberer, K., Punceva, M., Hauswirth, M., & Schmidt, R. (2002). Improving data access in P2P systems. IEEE Internet Computing, 6(1), 5-67. Bellotti, V., Ducheneaut, N., Howard, M., & Smith, I. (2003). Taking e-mail to task: The design and evaluation of a task management centered e-mail tool. In CHI (pp. 345-352). Bos, N., Olson, J. S., Gergle, D., Olson, G. M., & Wright, Z. (2002). Effects of four computermediated communications channels on trust development. In CHI (pp. 135-140). Breslin, J. G., Harth, A., Bojars, U., & Decker, S. (2005). Towards semantically-interlinked online communities. In ESWC (pp. 500-514).
Communication Systems for Semantic Work Environments
Buckland, M. K. (1992). Emmanuel Goldberg, electronic document retrieval, and Vannevar Bush’s memex. JASIS, 43(4), 284-294. Bush, V. (1945). As we may think. The Atlantic Monthly, 176(1), 101-108. Cole, R. J., Eklund, P. W., & Stumme, G. (2000). CEM-visualisation and discovery in e-mail. In Principles of Data Mining and Knowledge Discovery (pp. 367-374). Cole, R., & Stumme, G. (2000). CEM - a conceptual e-mail manager. In Iccs (pp. 438-452). Danis, C., Kellogg, W. A., Lau, T., Dredze, M., Stylos, J., & Kushmerick, N. (2005). Managers’ e-mail: Beyond tasks and to-dos. In CHI ’05: CHI ’05 Extended Abstracts On Human Factors in Computing Systems, New York, NY (pp. 13241327). ACM Press. Decker, S. (2006). The social semantic desktop: Next generation collaboration infrastructure [Special issue: APE2006 academic publishing in Europe: The role of information in science and society]. Information Services and Use, 26(2), 139-144. Efimova, L., & de Moor, A. (2005). Beyond personal Webpublishing: An exploratory study of conversational blogging practices. In HICSS, (p. 107a). El-Ansary, S., Alima, L., Brand, P., & Haridi, S. (2003). Efficient broadcast in structured peer-topeer networks. In 2nd International Workshop on Peer-to-Peer Systems (IPTPS), Berkeley, CA (pp. 304-314). Erickson, T., Kellogg, W. A., Laff, M., Sussman, J. B., Wolf, T. V., Halverson, C. A. et al. (2006). A persistent chat space for work groups: The design, evaluation and deployment of loops. In Conference on Designing Interactive Systems (pp. 331-340).
0
Fischer, J., Gantner, Z., Rendle, S., Stritt, M., & Schmidt-Thieme, L. (2006). Ideas and improvements for semantic wikis. In ESWC (pp. 650-663). Franz, T., Staab, S., & Arndt, R. (2007). The XCOSIM Integration Framework for a seamless semantic desktop. In Proceedings of the Fourth International ACM Conference on Knowledge Capture (K-CAP 2007) (pp. 143-150). Franz, T., & Staab, S. (2005). SAM: Semantics aware instant messaging for the networked semantic desktop. In Proceedings of the 1st Workshop On The Semantic Desktop. 4th International Semantic Web Conference (pp. 167-181). Galway, Ireland. Gemmell, J., Bell, G., Lueder, R., Drucker, S. M., & Wong, C. (2002). Mylifebits: Fulfilling the memex vision. In ACM Multimedia (pp. 235-238). Golbeck, J., & Hendler, J. (2005). Inferring trust relationships in Web-based social networks. ACM Transactions on Internet Technology. Haag, S., Cummings, M., & McCubbrey, D. J. (2002). Management information systems for the information age (3rd ed.). Irwin McGraw-Hill. Handel, M., & Herbsleb, J. D. (2002). What is chat doing in the workplace? In CSCW (pp. 1-10). Herring, S. C. (1999). Interactional coherence in cmc. In HICSS ’99: Proceedings of the ThirtySecond Annual Hawaii International Conference on System Sciences, Washington, DC (Vol. 2, pp. 2022). IEEE Computer Society. Herring, S. C., Scheidt, L. A., Wright, E., & Bonus, S. (2005, February 1). Weblogs as a bridging genre. Information Technology & People, 18(30), 142-171. Isaacs, E., Walendowski, A., Whittaker, S., Schiano, D. J., & Kamm, C. A. (2002). The character, functions, and styles of instant messaging in the workplace. In CSCW (pp. 11-20).
Communication Systems for Semantic Work Environments
Kane, B., & Luz, S. (2006). Multidisciplinary medical team meetings: An analysis of collaborative working with special attention to timing and teleconferencing. Computer Supported Cooperative Work (CSCW), V15(5), 501-535. Khoussainov, R., & Kushmerick, N. (2005). Email task management: An iterative relational learning approach. In Second Conference on E-mail and Anti-Spam, CEAS. Kim, M.-S., & Raja, N. S. (1991). Verbal aggression and self-disclosure on computer bulletin boards. Annual Meeting of the International Communication Association. Kogan, S. L., & Muller, M. J. (2006). Ethnographic study of collaborative knowledge work. IBM Systems Journal, 45(4), 759. Krishnamurthy, S. (2002). The multidimensionality of blog conversations: The virtual enactment of September 11. In Internet Research 3.0, Maastricht, The Netherlands. Kushmerick, N., & Lau, T. (2005). Automated e-mail activity management: An unsupervised learning approach. In IUI ’05: Proceedings of the 10th International Conference On Intelligent User Interfaces, New York, NY (pp. 67-74). ACM Press. Lichtenstein, S. (2004). Knowledge development and creation in e-mail. In HICSS. Mabry, E. A. (1998). Frames and flames: The structure of argumentative messages on the net (pp. 13-26). Mackay, W. E. (1988). More than just a communication system: Diversity in the use of electronic mail. In CSCW (pp. 344-3535). Masui, T., & Takabayashi, S. (2003). Instant group communication with quickml. In GROUP (pp. 268-273).
McDowell, L., Etzioni, O., & Halevy, A. Y. (2004a). Semantic e-mail: Theory and applications. J. Web Sem., 2(2), 153-183. McDowell, L., Etzioni, O., Halevy, A. Y., & Levy, H. M. (2004b). Semantic e-mail. In Www (pp. 244-254). Merz, P., & Gorunova, K. (2005). Reliable multicast and its probabilistic model for job submission in peer-to-peer grids. In 6th International Conference on Web Information Systems Engineering (WISE), New York (pp. 504-511). Möller, K., Bojars, U., & Breslin, J. G. (2006). Using semantics to enhance the blogging experience. In ESWC (pp. 679-696). Nardi, B. A., Whittaker, S., & Bradner, E. (2000). Interaction and outeraction: Instant messaging in action. In Conference on Computer Supported Cooperative Work (CSCW) (pp. 79-88). Nonnecke, B., & Preece, J. (2000). Persistence and lurkers in discussion lists: A pilot study. In HICSS ’00: Proceedings of the 33rd Hawaii International Conference on System Sciences, Washington, DC (Vol. 3, p. 3031). IEEE Computer Society. Oren, E., Breslin, J. G., & Decker, S. (2006). How semantics make better wikis. In WWW (pp. 1071-1072). Osterfeld, F., Kiesel, M., & Schwarz, S. (2005). Nabu - a semantic archive for XMPP instant messaging. In S. Decker, J. Park, D. Quan & L. Sauermann (Eds.), Proceedings of the 1st Workshop On The Semantic Desktop. 4th International Semantic Web Conference (pp. 159-166). Galway, Ireland. Ratnasamy, S., Francis, P., Handley, M., Karp, R., & Schenker, S. (2001). A scalable content-addressable network. In ACM SIGCOMM Conference, San Diego, CA (pp. 161-172). Rowstron, A., & Druschel, P. (2001). Pastry: Scalable, decentralized object location and routing for
Communication Systems for Semantic Work Environments
large-scale peer-to-peer systems. In IFIP/ACM International Conference on Distributed Systems Platforms, Heidelberg, Germany (pp. 329-350). Rowstron, A., Kermarrec, A., Castro, M., & Druschel, P. (2001). SCRIBE: The design of a large-scale event notification infrastructure. In Proceedings of the 3rd International Workshop on Networked Group Communication, London, UK (pp. 30-43). Stoica, I., Morris, R., Karger, D., Kaashoek, M., & Balakrishnan, H. (2001). Chord: A scalable peerto-peer lookup service for internet applications. In ACM SIGKOMM Conference, San Diego, CA (pp. 149-160). Veinott, E. S., Olson, J., Olson, G. M., & Fu, X. (1999). Video helps remote work: Speakers who need to negotiate common ground benefit from seeing each other. In CHI ’99: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, New York, NY (pp. 302309). ACM Press. Vogiazou, Y., Eisenstadt, M., Dzbor, M., & Komzak, J. (2005). From Buddyspace to CitiTag: Large-scale symbolic presence for community building and spontaneous play. In ACM Symposium on Applied Computing (SAC) (pp. 1600-1606). Völkel, M., Krötzsch, M., Vrandecic, D., Haller, H., & Studer, R. (2006). Semantic wikipedia. In WWW (pp. 585-594).
Wagner, C. (2004). Wiki: A technology for conversational knowledge management and group collaboration. Communications of the Association for Information Systems, 13, 265-289. Watts, D. J., Dodds, P. S., & Newman, M. E. (2002). Identity and search in social networks. Science Magazine, 296, 1302-1305. Watt, J., Walther, J., & Nowak, K. (2002). Asynchronous videoconferencing: A hybrid communication prototype. hicss, 01, 13. Whittaker, S., Jones, Q., Nardi, B. A., Creech, M., Terveen, L. G., Isaacs, E. et al. (2004). Contactmap: Organizing communication in a social desktop. ACM Trans. Comput.-Hum. Interact., 11(4), 445-471. Whittaker, S., & Sidner, C. L. (1996). E-mail overload: Exploring personal information management of e-mail. In CHI (pp. 276-283). Zhang, J., & Van Alstyne, M. W. (2004). SWIM: Fostering social network based information search. In CHI Extended Abstracts (pp. 1568).
endnotes 1 2
3 4 5 6
http://youtube.com/ http://kwarc.eecs.iu-bremen.de/projects/ stex/index.html http://www.ontoprise.de/ http://www.foaf-project.org/ http://www.w3.org/2006/vcard/ns http://www.w3.org/2000/10/swap/pim/contact
Chapter III
Semantic Social Software:
Semantically Enabled Social Software or Socially Enabled Semantic Web? Sebastian Schaffert Salzburg Research Forschungsgesellschaft, Austria
introduCtion
social software
Recently, the combination of Social Software with Semantic Web technology has been gaining significant attention in the Semantic Web community. This is exemplified by the surprisingly high number of submissions and attendees of the 1st Workshop on Semantic Wikis (Völkel & Schaffert, 2006) that took place at the European Semantic Web Conference 2006 (ESWC06) last year, as well as the ESWC06 best poster award for the Semantic Wikipedia (Völkel, Krötzsch, Vrandecic, Haller & Studer, 2006). This chapter describes what I believe makes Social Software attractive for the Semantic Web community, and what makes the Semantic Web attractive for the Social Software community. It also derives challenges for the Semantic Web community to address that seem relevant to us based on our experience with Social Software and the Semantic Web. In the remainder of this introduction, I briefly introduce Social Software, the Semantic Web, and the combination of both, which I call Semantic Social Software.
According to Wikipedia, Social Software is software that “enables people to rendezvous, connect or collaborate through computer-mediated communication and to form online communities.”1 Although this definition in principle also includes technologies that have already existed for a long time (like e-mail or Usenet), the term Social Software usually only comprises more recent developments like wikis, Weblogs, instant messaging (e.g., AIM, ICQ), social bookmarking (e.g., del.icio.us), media sharing (e.g., Flickr, YouTube), and social networking systems (e.g., MySpace, OpenBC). Today, huge amounts of content are available in Social Software systems. The free Web encyclopedia Wikipedia now hosts over 4 million entries of partly astonishing quality. The social networking site MySpace is one of the most popular Web sites overall (ranked number 4 by Alexa, following closely after Google, Yahoo, and MSN). According to the Web log index Technorati,2 there are currently about 40 million blogs with a
Copyright © 2008, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
Semantic Social Software
doubling time of about 6 months and around 1.2 million blog posts every day. What makes Social Software interesting is not only the huge amount of content but that it considerably changes the way content is created and consumed, maybe even more so than the Web did some 15 years ago: where the traditional process of publishing content was expensive and time consuming, Social Software allows virtually everyone to publish on a mouse click. To speak in market terms, with Social Software, consumers become prosumers. Because of these radical changes in content production, I consider Social Software a disruptive technology.
on information to a Web focused on relations between things. According to W3C founder and chair Tim Berners-Lee, the Semantic Web will be the next big thing. The current Semantic Web approach may be briefly described as enriching the existing Web with meta-data and (meta-)data processing so as to provide Web-based systems with advanced (socalled intelligent) capabilities, in particular with context-awareness and decision support. What distinguishes the Semantic Web from previous AI approaches is that it assumes a distributed but strongly connected web of small pieces of formal knowledge rather than big, centralised knowledge bases.
semantic web semantic social software The vision of the Semantic Web is to move from “dumb” content that is suitable for presentation only to “smart” content that may be processed by machines and used in different settings. It is also to move from application-centric systems to data-centric systems, and from a Web focused
Figure 1. Nova Spivack's “Metaweb”
Semantic Social Software is the combination of Social Software with Semantic Web technologies. Its basic ideas are on the one hand to improve usage of Social Software by adding metadata and on the other hand to improve the process of
Semantic Social Software
creating Semantic Web metadata by using Social Software. These two different perspectives are discussed extensively in the next sections. The combination of Social Software and Semantic Web technologies seems to fit well. This may be due to the remarkable similarities between Social Software—which is about small but strongly connected pieces of content from different sources with differing opinions—and the Semantic Web, which is about small but strongly connected pieces of formal knowledge from different sources, with different levels of precision and trustworthiness, maybe even inconsistencies. The difference is in this sense only in the level of abstraction: where Social Software mostly deals with social connections and human readable content, the Semantic Web mostly deals with formal connections and formal content. In a way, the step from traditional AI to the Semantic Web is thus very similar to the step from traditional content production to Social Software. This perspective is also in line with a number of recent predictions for the future of the Web: for example, technology evangelist Nova Spivack outlines in his 2004 articles3,4 what he calls “The Metaweb” (Figure 1). The Metaweb is essentially about using social connections to form information connections and vice versa. As can be seen in Figure 1, Nova Spivack is convinced that “The Metaweb is emerging from the convergence of the Web, Social Software and the Semantic Web,” connecting human and machine intelligence and moving from “just a bunch of interacting parts” to “a new higher-order whole.” This chapter continues as follows: the following section describes two different perspectives one can take on Semantic Social Software, namely the “Semantically Enabled Social Software” perspective (meaning the usage of semantic metadata to enhance existing social software) and the “Socially Enabled Semantic Web” perspective (meaning the usage of Social Software to create semantic metadata). Then, I describe
three different kinds of Social Software whose combination with Semantic Web technology appears promising: Semantic Wikis, Semantic Weblogs, and e-portfolios. Out of these three applications, I derive salient aspects of Semantic Social Software in the following section. I then present the mentioned major challenges for the Semantic Web community, and conclude with an overview of the related work and perspectives.
“semantiCally enaBled soCial software” or “soCially enaBled semantiC weB”? Semantic Social Software is traditionally approached from two directions. The first, which I call “Semantically Enabled Social Software,” makes use of Semantic Web technology to enhance existing Social Software. The second, which I call “Socially Enabled Semantic Web” makes use of the structures (e.g., links between pieces of content or between people) in Social Software to form Semantic Web data. In the following, I describe these two approaches and show that they are really just two sides of the same story, because the difference is primarily in the use of applications and not in the applications themselves.
Semantically Enabled social software As has been outlined in the introduction, massive amounts of digital content are nowadays available in Social Software systems. Although content in Social Software systems is highly connected via hyperlinks and/or social networks, finding relevant content is becoming increasingly difficult, because the existing structure is used merely for presentation purposes. With diverging applications it is furthermore often hard to exchange content between different systems.
Semantic Social Software
“Semantically Enabled Social Software” tries to overcome these issues by applying Semantic Web technology to Social Software. The existing informal or semiformal structures like hyperlinks are augmented by machine-readable formal descriptions (“metadata”) that make explicit the actual meaning behind a connection. Such metadata allows for more sophisticated services, like improved search and navigation (e.g., queries on the structure, context visualisation, derived knowledge), personalised presentation of content (e.g., based on personal preferences), and improved interoperability between systems (e.g., to integrate several applications in a company process, or to support smart agents). For example, a hyperlink from an article in Alice’s Web log to an article in Bob’s Web log could be annotated with “agrees with” or “disagrees with.” Articles in a Web log could furthermore be associated with certain topics like “EU constitution” (as a subtopic of “EU politics”). This would give readers the opportunity to search not only for articles relevant to a certain topic but also to find supporting or diverging opinions on this topic. This approach is, among others, followed by the Semantic Wikipedia project (Völkel et al., 2006), which aims to enhance the existing Wikipedia by semantic annotations to facilitate search and navigation, and by the semiBlog project (Möller, Bojars & Breslin, 2006), which aims to simplify search, connectivity, browsing, and management of a Web log by using semantic annotations.
Socially Enabled semantic web The “Socially Enabled Semantic Web” sees Semantic Social Software as a tool that simplifies and thus improves the creation of metadata on the Semantic Web, in the same manner as Social Software simplified and improved the creation of data on the normal Web. This approach is founded in the observation that creating formal, machine-readable content on the Semantic Web is hard, which is arguably still one of the most
significant barriers to the wide-spread adoption of the Semantic Web. The reason for this is primarily that creating formal metadata currently requires significant expertise in the modelled domain (e.g., biology), as well as the use and intricacies of the used formal languages (e.g., RDF and OWL). The latter issue could be significantly mitigated by appropriate tools, but existing tools are insufficient in the sense that they are much too complicated to use for non-technical users. As a consequence, formalised content on the Semantic Web is still rare and limited to some selected domains. Semantic Social Software has the potential to overcome some of these problems. It supports the creation of metadata in a number of ways. First, it builds upon existing structures, where connections reflect real-world relationships that are “natural” to the people using the software. Second, it supports the collaboration of people with different backgrounds and expertise, allowing, for example, a biologist and a computer engineer to work on the same knowledge model, augmenting each other. And third, Semantic Social Software provides instant gratification: every bit of formal knowledge contributed by a user is immediately usable. For instance, a common ontology engineering process supported by a Semantic Wiki (as a special kind of Semantic Social Software) could be to start with a collection of normal Wiki pages (as, e.g., found on Wikipedia) that make up the domain to be modeled and then augment the existing hyperlink structure between Wiki pages with machine readable annotations. The first task (writing informal Wiki content) could be easily achieved by a biologist, the second task (formalising the hyperlink structure) by a knowledge engineer. Both could contribute their expertise and collaborate on the creation of the knowledge model. This approach is, for example, followed by Peter Mika (2005) in his work about complementing ontologies with social networks and by our own work on collaborative knowledge engineering
Semantic Social Software
with the Semantic Wiki IkeWiki (Schaffert, 2006; Schaffert, Gruber, & Westenthaler, 2005).
Two Sides of the Same Story Although the two perspectives described above have originally developed separately and with different application scenarios in mind, the actual software used in both perspectives shares many properties, even to the extent of being actually the same tool used in different settings. This is best exemplified by the history of our own Semantic Wiki system IkeWiki (Schaffert, 2006; Schaffert, Westenthaler, & Gruber, 2006; Schaffert et al., 2005), originally developed to support non-technical domain experts in the process of formalising their knowledge (i.e., “Socially Enabled Semantic Web”), it is now primarily used in a number of settings focussed on enhancing the functionality of Social Software (i.e., “Semantically Enabled Social Software”), like our own group’s knowledge base or the conference wiki of the Social Skills durch Social Software conference. Similar developments can be seen in other projects. I therefore argue that, although the two research directions have different goals, they are actually only two sides of the same story, namely “Semantic Social Software.” This joint perspective allows us to investigate Semantic Social Software as a kind of software that is—based on its properties—helpful in many different settings, rather than looking at it merely as a tool designed for a single purpose. This chapter investigates different applications of Semantic Social Software and discusses them under both, the “Semantically Enabled Social Software” and the “Socially Enabled Semantic Web” perspective.
three appliCations of semantiC soCial software Social Software is very diverse and there exist numerous different applications. In this chapter,
I introduce three applications where a combination with Semantic Web technology is or might be fruitful: semantic Wikis and semantic Web logs as existing applications, and e-portfolios as an emerging application. The convergence of the two different approaches to Semantic Social Software can be seen in all three applications.
semantic wikis: Community-Authored Knowledge models A wiki is essentially a collection of Web sites connected via hyperlinks. Many different wiki systems exist, but they commonly have a straightforward interface for editing content with a simplified syntax that makes it very easy to set hyperlinks to other pages within the wiki. Therefore, content in a wiki is usually strongly connected via hyperlinks. Furthermore, editing of content in wiki systems is Web-based and access is often unrestricted or at least hardly restricted. Most wiki systems also provide a rollback mechanism for reverting back to previous versions in case of accidental or undesired changes. Wikis are used in many areas, like encyclopedia systems (e.g., Wikipedia), as personal or group knowledge management tools, as collaboration tools, or in collaborative learning environments. The main idea of a Semantic Wiki is to annotate the inherent hyperlink structure of a Wiki with symbols that describe the meaning of a link in a machine readable fashion. A link from Mozart to Salzburg could, for example, be annotated with lived in or born in. Such an annotation can then be used, for example, enhanced presentation by displaying contextual information, enhanced navigation by giving easy access to relevant related information, and enhanced “semantic” search that allows to query the context in addition to the content. Semantic Wikis are also excellent tools for collaborative creation of knowledge models. Based on (existing or emerging) natural language
Semantic Social Software
Figure 2. Semantic annotation in IkeWiki
descriptions of concepts and individuals, formal knowledge models can be created successively. Natural language descriptions can be created primarily by domain experts (e.g., biologists) and then formalised in collaboration with knowledge engineers. For advanced knowledge engineering tasks, Semantic Wikis offer the possibility to export the knowledge model as RDF or OWL, which can then be loaded into more sophisticated and complicated tools like the OWL ontology editor Protegé.5 Semantic Wikis exist in many different flavours (e.g., Semantic MediaWiki, SemWiki, IkeWiki, SemperWiki, PlatypusWiki). Some systems are still primarily focused on the page content and see annotations as optional “added value”; they follow more the “Semantically Enabled Social Software” approach (e.g., Semantic MediaWiki). For others, the semantic annotations are in the foreground and sometimes even more important than the actual content; they follow the “Socially
Enabled Semantic Web” approach (e.g., IkeWiki and PlatypusWiki). Figure 2 shows how the page about the Bilberry is presented in IkeWiki, the Semantic Wiki developed at Salzburg Research. It includes several kinds of semantic metadata: (1) Type information is shown below the page title, (2) Links to (semantically) related pages are displayed in a separate “references box” on the right hand side, and finally, (3) shows interactive typing of links using AJAX technology, making it simple for users to add metadata to existing structures.
semantic web logs: Formalising Discourse A web log or blog is a personal, web-based journal very similar to a digital diary that everyone can read. It is usually organised as a list of short articles ordered by publication date. A very significant difference to a wiki is that content can usually only
Semantic Social Software
be authored by the owner of the weblog. Visitors, however, are usually allowed to leave comments about articles that are shown separately. Also, the software used by weblogs is often aware of other Weblogs linking to one of the articles and show this information in a so-called trackback section as part of the article. Furthermore, weblogs can integrate listings of other weblogs in their navigation (the so-called blogroll). In this way, Weblogs often become part of a strongly networked community, the so-called blogosphere. Karger and Quan (2004) summarise this “essence of blogging” under three key concepts: •
• •
Publishing information in small, discrete notes, as opposed to large, carefully organised Web sites Decentralised, per-user publication Exposing machine-readable listings
A semantic Web log uses semantic Web technology for improved searching and navigation in the blogosphere. Firstly, Web log posts can be associated with formal metadata describing their content, thus improving exchange, search, and retrieval of content. Secondly, the cross-linking between weblog posts in different Weblogs can be used for representing the discourse about a certain subject. In Möller, Bojars, and Breslin (2006), the first kind of metadata use is called
Figure 3. Structural relations in the blogosphere
content metadata, while the second kind is called structure metadata. Figure 3 (Möller et al., 2006) shows some of the possible structural relations between Weblogs. A particularly interesting property of Semantic Weblogs is the formal representation of discourse about different opinions on a certain topic and the corresponding social networks. This gives readers the possibility to search and navigate not only by topic but also to follow a discussion across different weblogs and to search specifically for certain opinions and connections between Weblogs. A salient aspect of discourse representation is the representation of second/higher order metadata (or “metadata about metadata”): where normal blog posts may state opinions about the content of other posts, Semantic Weblogs may make formal statements about the formal content of other Semantic Weblogs, requiring more expressive representation formalisms. This could, for example, also be used to form “networks of trust” concerning formal metadata, touching one of the core remaining open issues of the Semantic Web.
e-portfolios: Collecting learning artefacts The E-Portfolio Method (Barrett, 2005) is an educational method for supporting life-long learning. The basic idea is to collect all kinds of (digital) artifacts that document a personal learning process in a digital portfolio. Such artifacts may be as coarse as certificates or as fine-grained as every-day documentation of one’s learning progress like in a diary, including all relevant material, for example, test results, articles, presentations, group works, house work, contributions to an online discussion, self-written Wikipedia articles, and so forth. In other contexts, e-portfolios are for this reason also called Lifelog or Lifeblog. The goal of this collection is to be able to reflect about one’s own learning progress, to be able to extract parts of one’s personal portfolio
Semantic Social Software
for external presentation, to design a personal development plan (PDP), to validate and assess the learning outcomes against this plan, and to share learning artefacts with others. Artefacts in such a digital portfolio are strongly connected, both within the personal portfolio and with artefacts in the portfolios of other learners. Obviously, the e-portfolio method requires software support. An early e-portfolio system is Elgg (Tosh & Werdmuller, 2004).6 In Elgg, users can sign up and create their own digital portfolio where they can describe their personal skills and interests, publish articles in their personal Web log, collect links to other websites, and upload files that they consider relevant, particularly newsfeeds from other’s portfolios and weblogs. This profile can then, similar to social networking services, be used to find other people with similar interests, or to find communities with interesting topics. In this sense, e-portfolio systems can be seen as next generation social software. Other existing e-portfolio systems, like OSP7 or Blackboard’s e-portfolio tool, put more emphasis on the integration into learning and course management systems, but the social networking aspect is always existent to a certain degree. To the best of my knowledge, a Semantic e-portfolio does not yet exist (beyond the social tagging used by Elgg). However, as we argue in Hilzensauer, Hornung-Prähauser, and Schaffert (2006), such software could significantly benefit from Semantic Web technology. First, the collection of artifacts from different systems (like Weblogs, Wikis, online journals) requires interoperability to a degree that is not yet existent. Where current e-portfolio systems can only include raw file content or content created in the systems themselves, a Semantic e-portfolio could go much beyond that and integrate content from different sources and different systems, encoded in different media formats. Second, semantic metadata about the artifacts in a digital portfolio could be utilised to more easily create custom-tailored presentations out of the personal portfolio, for
0
example, for documenting one’s learning process for the purpose of evaluation or for creating a tailored resume for the application to a specific job. Third, semantically annotated artifacts could more easily—semi-automatically—be matched against one’s personal development plan, allowing for a better reflection by the learner. And fourth, semantic annotations allow for easier navigation and retrieval through an inevitably huge collection of “life artifacts.” E-pprtfolios also provide an interesting and challenging application for Semantic Web technologies. As the e-portfolio aims to represent a learner’s learning process and thus his skills and knowledge, the semantic metadata in an e-portfolio could mirror the learner’s knowledge and interactions with the environment. Such data, if used with the necessary care for privacy, can be useful in many application areas, ranging from automatic creation of personal timetables and development plans over finding relevant jobs in an online job database to assembling a team with complementary skill sets for a certain task in a company.
salient aspeCts of semantiC soCial software Semantic Social Software has a number of properties that make it interesting as a research topic besides the two major “sides” described above. In the following, I give an incomplete overview over what I consider salient aspects of Semantic Social Software.
testbed for semantic web Technology Semantic Social Software is software that can be developed quickly and easily, and can build upon existing applications and principles. Augmenting the existing social and hyperlink structures with formal annotations is rather intuitive and a natural
Semantic Social Software
extension of existing applications. At the same time, Semantic Social Software shows many of the promises and also of the problems of the big “Semantic Web Vision.” Examples are the improved searching and navigation, personalisation and content adaptation, interoperability, open world assumption, coupling of data and metadata, evolving knowledge models, inconsistencies in real-world data (as many authors work on the knowledge model), ontology alignment (as content from different sources is integrated), and so forth. Some of these aspects are further elaborated below. I therefore argue that Semantic Social Software can be an ideal test bed for Semantic Web technology. If problems with the technology arise in Semantic Social Software, they will likely also arise on the large Semantic Web. If technology works properly in Semantic Social Software, there is also a high chance that it works on the large Semantic Web.
Coupling of Data and Metadata An aspect that is often overseen in Semantic Web research is that metadata rarely stands for itself. Instead, metadata is in most cases only relevant with respect to the data it describes. Combined consideration of data and metadata therefore leads to more realistic settings and “connects human and machine intelligence.” In Semantic Social Software, the combination of data and metadata is quite natural, as existing Social Software with existing content is merely augmented (and not replaced) by metadata. Combined access to metadata and data in Semantic Social Software could, for example, mean enhanced search and navigation or context-dependent presentation of human-readable data. A combination of data and metadata requires consideration of query and reasoning languages that are capable of processing both, data and metadata. An example for such a language is Xcerpt (Schaffert, 2004), a rule-based query
language suitable for any kind of semi-structured data, including RDF and HTML. A further issue that often becomes apparent in Semantic Social Software is the so-called URI crisis, that is, the question whether a URI used in the metadata refers to a Web page (Wiki page, Web log entry) or to the content described in that page (e.g., “elephant”). Another interesting aspect of coupling data and metadata is the semi-automatic extraction of metadata from the actual data using, for example, natural language processing techniques. For example, a page in a Semantic Wiki could be annotated automatically based on the content of the page. As automatic metadata extraction is currently not perfectly reliable, it would make sense to mark such annotations as “automatic” and give users the opportunity to revise them if needed.
emerging and evolving knowledge models A very interesting property of Semantic Social Software is that knowledge models do not appear in discrete “releases,” but slowly and dynamically evolve over time. A knowledge model in, for example, a Semantic Wiki may begin with a small set of annotations for a single page to a full-fledged ontology. Also, some parts of the knowledge model will usually be more formalised than others, reflecting areas with more imminent needs or higher community interest. Such evolving knowledge models raise a number of interesting questions that are also relevant for the Semantic Web as a whole (which inevitably will also be an evolving knowledge model). Primarily, evolving systems will be full of inaccuracies and even inconsistencies, demanding for more tolerant formal languages than those that are proposed today. Also, trust, versioning, and merging/aligning are issues that will need to be addressed appropriately.
Semantic Social Software
Self-Organising Communities around Emerging Topics In many Social Software systems, communities organise themselves around certain emerging topics that are relevant at some point in time. In Semantic Social Software, such emerging topics are likely to also be more precisely formalised than others, and could be identified automatically by applying appropriate reasoning. Such information could be used to provide readers with information about “what is relevant,” similar to “recent changes” listings in current systems.
Challenges for the semantiC weB Community In our works with and considerations about different kinds of Semantic Social Software, there have been a number of frequently arising challenges that should be taken into consideration by the Semantic Web community if the Semantic Web is supposed to be adopted by a wide community. I present some of these challenges in the following.
“Keep it Simple, Stupid!” Ultimately, Semantic Web Technology will only “take off” if it is simple enough to use, that is, the additional effort is in average significantly less than the actual benefit. Systems that require users to learn complicated formal languages imposing (for “outsiders”) arbitrary-looking restrictions will very likely fail. Often, as Jim Hendler said,8 “a little semantics goes a long way.” In addition, we need tools that hide most of the complexity of the language from the user, for example, domain-specific interfaces for creating knowledge and visual interfaces for composing queries. Semantic Social Software goes into this direction, but fails when the underlying languages become too expressive (e.g., number restrictions).
don’t forget the data in metadata As has been lined out above, metadata is “data about data,” and only rarely useful on its own. Considering data and metadata separately therefore only makes little sense. Instead, it is necessary to develop formalisms, query languages, and reasoning languages that can handle both data and metadata. Steps into this direction have been made (e.g., in Xcerpt), but they are not in the “mainstream” and there is still a long way to go.
Be Tolerant About Inconsistencies The world is full of inaccuracies and inconsistencies, particularly if different people with different viewpoints work on the same knowledge model—as is the case in Semantic Social Software, and as will be the case in the Semantic Web. Yet, the Semantic Web, like many or most of its predecessors in AI, builds upon Classical Logic, which is by the “ex falsum quodlibet” rule intolerant to inconsistencies. What the Semantic Web as a web of inconsistencies, errors, and inaccuracies needs are formalisms that do not break and can work around problematic parts of the knowledge model (e.g., Schaffert et al., 2005). Various such formalisms have been proposed in the pre-Semantic Web era, for example, paraconsistent logics or fuzzy logics.
there is no “one size fits all” Different applications require different representation formalisms. Whereas languages like OWL are good for representing conceptual hierarchies, they are incredibly bad in representing presentational structures (HTML and CSS do it just fine). What the Semantic Web needs is a flexible and extensible set of formal languages, including formalisms for temporal knowledge, location, rules, situations, and events, and so forth. Even
Semantic Social Software
higher-order languages will be useful in many applications, despite their known undecidability.
Reasoning Needs to be Efficient Many applications work in close interaction with human users. In such situations, it is unacceptable to have complex reasoning systems that take several minutes even for small data sets. It is necessary to improve the performance of existing systems, and to allow developers more fine-grained control over the expressivity and correctness of the reasoner. Often, it is more important to get an almost correct answer within a few milliseconds than to wait for a completely correct answer after several minutes.
Reasoning Needs Truth Maintanance A significant issue with reasoning systems is that their reasoning is not tracable for users. As a consequence, users often get the feeling of being patronised by the system when the system makes a decision based on reasoning. For Semantic Web applications, it would thus be desirable to allow the user to see all justifications for a decision. A typical example is when the system infers the type for some resource (e.g., a Wiki page) based on the type of a relation to another resource and the user does not agree with this inference, but cannot remove the type directly. In such situations, users should have the option to interfere and modify some of the justifications as needed.
metadata needs versioning In evolving knowledge models, it is important and interesting to keep track of the modifications done not only in the data but also in the metadata. For this purpose, it is necessary to define what makes up a “unit” or “transaction,” as a single modification in the application most likely has effects at many different places in a knowledge model.
related work Many people within the Semantic Web community are investigating Semantic Social Software. Most noteworthy is the Semantic Wiki movement that has gained a lot of attention, culminating in last year’s 1st Semantic Wiki Workshop (Vökel & Schaffert, 2006) colocated with the 3rd European Semantic Web Conference (ESWC06). Other researchers have also worked in the field. An interesting work is the article “Ontologies Are Us” by Peter Mika (2005), which discusses the relation between social networks and Semantic Web relationships. Other related works have been mentioned throughout this chapter, most notably various Semantic Social Software systems, and Nova Spivack’s “Metaweb.” Related to the Semantic Web challenges I present in the last section is Frank van Harmelen’s invited talk entitled Where does it Break? or: Why the Semantic Web is not just “Research as Usual” at ESWC06, where he presents similar challenges for the Semantic Web community.
ConClusion and perspeCtives Semantic Social Software as the combination of Social Software and Semantic Web technologies has great potential, for Social Software developers as well as for Semantic Web researchers. In this chapter, I presented the two different perspectives on Semantic Social Software and gave three example applications. From our experience with developing and working with Semantic Social Software, I derived challenging research issues for the Semantic Web. These research issues need—in my opinion—to be investigated for making Semantic Web technology successful. In future work, our group will develop a common framework for implementing Semantic Social Software (and other kinds of semantic software), called the “knowledge-based content management system.” The aim of this system is to
Semantic Social Software
provide a robust foundation for storing, accessing, and processing content as well as metadata. The system will possibly, and hopefully, solve and implement some of the issues mentioned in the previous section. The combination of Semantic Web technology and Social Software has also been chosen as the next research focus of Salzburg NewMediaLab, Austria’s industrial competence centre for research on digital content.
aCknowledgment This work has been partly funded by Salzburg NewMediaLab, a competence centre in the Kind action line funded by the Austrian Federal Ministry of Economics and Labor (BMWA) and the state of Salzburg.
referenCes Barrett, H.C. (2005). Researching electronic portfolios and learner engagement (Tech. Rep., The REFLECT Initiative). Hilzensauer, W., Hornung-Prähauser, V., & Schaffert, S. (2006, September). Requirements for a personal development planning in e-portfolios supported by Semantic Web technology. In 6th International Conference on Knowledge Management (I-KNOW06), Graz, Austria. Karger, D.R., & Quan, D (2004). What would it mean to blog on the Semantic Web. In Proceedings of the 3rd International Semantic Web Conference (ISWC04), Hiroshima, Japan. Springer-Verlag. Krötzsch, M., Vrandecic, D., & Völkel, M. (2005). Wikipedia and the Semantic Web – the missing links. In Proceedings of the WikiMania2005. Mika, P. (2005, November). Ontologies are us: A unified model of social networks and semantics. In Proceedings of the 4th International Semantic
Web Conference (ISWC 2005), Galway, Ireland (LNCS 3729). Springer-Verlag. Möller, K., Bojars, U., & Breslin, J.G. (2006, June). Using semantics to enhance the blogging experience. In Proceedings of the 3rd European Semantic Web Conference (ESWC06), Budva, Montenegro (LNCS 4011). Springer-Verlag. Oren, E. (2005). SemperWiki: A semantic personal Wiki. In 1st Workshop on The Semantic Desktop, colocated with ISWC05, Galway, Ireland. Schaffert, S. (2004, October). Xcerpt: A rule-based query and transformation language for the Web. Ph.D. Thesis, University of Munich. Schaffert, S. (2006, June). IkeWiki: A semantic wiki for collaborative knowledge management. In 1st International Workshop on Semantic Technologies in Collaborative Applications (STICA’06), Manchester, UK. Schaffert, S., Bry, F., Besnard, P., Decker, H., Decker, S., Enguix, C. et al. (2005, November). Paraconsistent reasoning for the Semantic Web (Position paper). In Workshop on Uncertainty Reasoning for the Semantic Web (URSW05) at ISWC05, Galway, Ireland. Schaffert, S., Gruber, A., & Westenthaler, R. (2005, November). A semantic wiki for collaborative knowledge formation. In Semantics 2005, Vienna, Austria. Trauner Verlag. Schaffert, S., Westenthaler, R., & Gruber, A. (2006, June). IkeWiki: A user-friendly semantic wiki. In Proceedings of the 3rd European Semantic Web Conference (ESWC06) – Demonstrations Track, Budva, Montenegro. Tazzoli, R., Castagna, P., & Campanini, S.E. (2004). Towards a semantic wiki WikiWeb. In 3rd International Semantic Web Conference (ISWC2004), Hiroshima, Japan. Tosh, D., & Werdmuller, B. (2004). Creation of a learning landscape: Weblogging and social
Semantic Social Software
networking in the context of e-portfolios (Tech. Rep.). University of Edinburgh.
endnotes 1
Völkel, M., Krötzsch, M., Vrandecic, D., Haller, H., & Studer, R. (2006). Semantic wikipedia. In Proceedings of the 3rd European Semantic Web Conference (ESWC06) – Poster Track, Budva, Montenegro. Völkel, M., & Oren, E. (2006). Personal knowledge management with wemantic wikis. Völkel, M., & Schaffert, S. (2006). In 1st Workshop “From Wiki to Semantics” (SemWiki’06) – Colocated with ESWC’06, Budva, Montenegro.
2 3
4
5 6 7 8
http://en.wikipedia.org/w/index.php?title=Social_software\ &oldid=82649096 http://www.technorati.com http://novaspivack.typepad.com/nova_spivacks_weblog/2004/03/from_applicatio. html http://novaspivack.typepad.com/nova_spivacks_weblog/2004/04/new_version_of_ .html http://protege.stanford.edu/ http://www.elgg.org http://www.osportfolio.org/ as conference chair in the opening speech of the 2003 International Semantic Web Conference; Sanibel Island, Florida, USA, October 2003
Section II
Semantic Work Environment Tools
Chapter IV
SWiM:
A Semantic Wiki for Mathematical Knowledge Management Christoph Lange Jacobs University, Germany Michael Kohlhase Jacobs University, Germany
aBstraCt In this chapter, we present the SWiM system, a prototype semantic wiki for collaboratively building, editing, and browsing mathematical knowledge. SWiM is based on the semantic wiki IkeWiki, but replaces the wiki text with OMDOc, a markup format and ontology language for mathematical documents as the underlying knowledge representation format. Our long-term objective is to evolve SWiM into an integrated platform for ontology-based added-value services. As a social semantic work environment, it will facilitate the creation of a shared, public collection of mathematical knowledge (e.g., for education) and serve scientists as a tool for collaborative development of new theories. We discuss the architecture of the SWiM system focusing on its conceptual base, the OMDOc system ontology. In contrast to other semantic wikis, SWiM uses the system ontology to operationalize the fragments and relations of the underlying representation format, not only the domain ontology, that is, the relations between the represented objects themselves. We will present the prototype implementation of the SWiM system and propose its further evolution into a service platform for science and technology.
Copyright © 2008, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
SWiM
introduCtion The Internet plays an ever-increasing role in our everyday life, and science is no exception. The way we do (conceive, develop, communicate about, and publish) scientific or mathematical knowledge will change considerably in the next 10 years. In particular, most of the activities will be supported by scientific services, that is, software systems connected by a commonly accepted distribution architecture. It is a crucial but obvious insight that true cooperation of such services is only feasible if they have access to a joint corpus of joint knowledge. A central prerequisite for this is a technology that is capable to create, maintain, and deploy content-oriented (a.k.a. “semantic”) libraries of science on the Web that make the structure of scientific knowledge explicit, so that it can serve as a context for the objects of science. As mathematics is a discipline, which has always been especially aware of the syntax/semantics distinction and has treated its theories as first-class objects, we will pursue this ambitious goal for mathematical knowledge first and extend the methods and technologies to the (natural) sciences and engineering later. If we extend Tim Berners-Lee’s vision of a “Semantic Web” as a Web of data for applications to mathematics, many services come to mind: cutting and pasting mathematical text from a search engine into a computer algebra system, automated checking or explanation of proofs published on the Web, if they are sufficiently detailed and structured, semantic search or data mining for mathematical concepts (“Are there any objects with the group property out there?”), classification (given a concrete mathematical structure, is there a general theory for it?), and many more. All of these services can currently only be performed by humans, limiting the accessibility and thus the potential value of the information. On the other hand, the content-oriented mathematical libraries can only be generated by
humans, as has been proved by the successful PlanetMath project (Krowne, 2003; “PlanetMath,” 2007), which features free, collaboratively created entries on more than 10,000 mathematical concepts. PlanetMath, however, is not completely machine-understandable. There is a fixed set of metadata associated with each article, including its type (definition, theorem, etc.), parent topic, Mathematics Subject Classification, synonyms, and keywords, but the content itself is written in LaTeX and can only be searched in full-text mode.
semantiC mathematiCal knowledge markup with omdoc We make use of the structural/semantic markup approaches using formats such as OpenMaTh (Buswell, Caprotti, Carlisle, Dewar, Gaetano, & Kohlhase, 2004), Content MaThML (Carlisle, Ion, Miner, & Poppelier, 2003), and OMDOc (Open Mathematical Documents (Kohlhase, 2006)), the latter of which embeds and extends the former ones. These formats, constituting the state of the art for representing mathematical knowledge, are now used in a large set of projects in automated theorem proving (Müller, 2006a), e-learning (Melis et al., 2006), e-publishing, semantic search (Kohlhase & Şucan, 2006), and in formal digital libraries. OMDOc builds on OpenMaTh or Content MaThML for mathematical formulae and extends this by an infrastructure for context and domain models from “formal methods.” In contrast to those, a structural/semantic approach does not require the full formalization of mathematical knowledge, but only the explicit markup of important structural properties. For instance, a statement will already be considered as “true” if there is a proof object that has certain structural properties, not only if there is a formally verifiable proof for it. This allows OMDOc to be used, for example, as a development/migration format,
SWiM
which offers “structural” services while the content is still “false.” Since the structural properties are logic-independent, a commitment to a particular logical system can be avoided without losing the automatic knowledge management, which is missing for semantically unannotated documents. Work on OMDOc and SWiM shows that many added-value services in knowledge management do not need tedious formalization, but can be based on the structural/semantic level. OMDOc assumes a three-layered structure model for semantic representation formalisms: •
•
•
Object Level: represents objects such as complex numbers, differential equations, finite groups, and so forth. Semantic representation formats specify the logical structure of objects rather than their presentation. This avoids ambiguities, which would otherwise arise from domain specific representations. Statement Level: sciences (natural/social/ technological) are concerned with modeling our environment, more precisely with statements about the objects in it. We can distinguish different types of statements: model assumptions, their consequences, hypotheses, and measurement results. All of them state relationships between scientific objects and have to be verified or falsified in theories or experiments. Moreover, all these statements have a conventionalized structure, such as Exercise, Definition, Theorem, Proof, and a standardized set of relations among each other, both of which are part of the system ontology. For instance, a model is fully determined by its assumptions (also called axioms); all consequences are deductively derived from them (via theorems and proofs), and therefore their experimental falsification uncovers false assumptions of the model. Theory/Context Level: Representations always depend on the ontological context;
even the meaning of a single symbol—for example, the glyph h as the height of a triangle or Planck’s quantum of action—is determined by its context, and, depending on the current assumptions, a statement can be true or false. Therefore the sciences (with mathematics leading the way) have formed the habit to fix and describe the situation of a statement. OMDOc makes this structure explicit. In mathematical logic, a theory is the deductive closure of a set of axioms, that is, the (in general infinite) set of logical consequences of the model assumptions. Even though this fully explains the phenomenon context in theory, important aspects like the re-use of theories, knowledge inheritance, and the management of theory changes are disregarded completely. Therefore, formalisms with context level use elaborate inheritance structures for theories, for example, in form of ontologies in the Semantic Web or in form of “algebraic specifications” in program verification. An important trait of the three-layer language architecture is the inherent dependency loop between the object and theory levels mediated by the statement level: the objects obtain their meaning from the theories their functional components are at home in, and the theories are constituted by special statements, and, in particular, the objects that are contained in them. Making these structures explicit enables the mechanization and automation of knowledge management and the unambiguous, flexible communication of mathematical objects and knowledge that is needed for meaningful interoperability of software systems in science. In fact, we have experimented with extending this three-level architecture pioneered by the OMDOc format beyond mathematics. For physics, we only had to introduce three new statement-level constructs: observables, systems, and experiments (Hilf, Kohlhase, & Stamerjohanns, 2006), for chemistry and computer science only
SWiM
one at the statement level each, and one each at the object level (molecules and code fragments). In particular, the OMDOc theory level did not change at all; it seems to constitute a description of what is sometimes called “the scientific method.” Therefore, we are confident that the conceptual core of the SWiM system presented here can be extended to cover all STEM (Science, Technology, Engineering, and Mathematics) disciplines.
Cross-fertilization of mathematiCal knowledge management and semantiC wiki Even though the work reported here was initially motivated by solving the semantic prisoner’s dilemma in mathematical knowledge management (MKM) described later, we contend that the new application area MKM can also contribute to the development of semantic wikis in particular and semantic work environments in general.
semantic wikis: state of the art and Future Trends A semantic wiki is a wiki with an “underlying model of the knowledge described in its pages” (Wikimedia Foundation, 2006b). The concept of a semantic wiki is not definitive as of 2007, for semantic wikis did not emerge until late 2004. For an overview, see Lange (2007, section 1.4). Common semantic wikis, most of which are still research prototypes, combine the wiki principle with Semantic Web technologies. Most of them utilize formal languages like RDF (Lassila & Swick, 1999) or OWL (McGuinness & Harmelen, 2004) for annotating pages and links with semantic information. SweetWiki (see chapter VIII), for example, features a wiki system ontology with classes like “page” or “user” and lets users tag pages with concepts from several OWL domain ontologies. Other well-known semantic wikis
0
include Semantic MediaWiki (Krötzsch, 2008; Völkel, Krötzsch, Vrandečić, Haller, & Studer, 2006), an attempt to integrate the Wikipedia into the Semantic Web, and IkeWiki (Schaffert, 2006), which is intended as a social tool for knowledge engineering. The first well-known semantic wikis are Platypus (Tazzoli, Castagna, & Campanini, 2004) and WikSAR (Aumüller & Auer, 2005), but they are not under active development any more. In many semantic wikis, including SWiM, IkeWiki and Semantic MediaWiki, one page describes one real-world concept. The page itself and its links to other pages are typed using terms from ontologies. Importing and exporting RDF from and to the semantic Web is possible in most semantic wikis, and the knowledge base can be queried. Some semantic wikis employ a reasoning engine to infer additional knowledge from the explicit annotations that users made. Recent trends in wikis in general include: •
•
•
•
Improved user experience through WYSIWYG editing—as, for example, in SweetWiki and IkeWiki (see chapter III), Integration with other social software like Weblogs—SnipSnap (“SnipSnap,” 2007) is an example of a wiki with blogging functionality and some semantic features (“Labels”), A standardized Web Service interface and data exchange format for automated clients and distributed systems (Völkel et al., 2006), as well as Better spam and vandalism protection (especially on large, public wiki sites like Wikipedia).
Another important aspect is bringing semantic wikis to nonscientists. The by far most successful software in this regard is Semantic MediaWiki, which, despite its intention, is not yet used by Wikipedia (mainly for performance and scalability reasons), but by numerous other sites (Semantic
SWiM
Wiki Interest Group, 2007b). The trends mentioned for general wikis also prevail in the area of semantic wikis, with the addition of: •
•
•
Incorporation of multimedia (metadata/ ontologies/database management systems) (Nixon & Simperl, 2006; Popitsch, Schandl, Amiri, Leitich, & Jochum, 2006) Visualization of the RDF graph of the knowledge inside the wiki (Eronen & Röning, 2006), incorporation of visual mapping techniques (Haller, Kugel, & Völkel, 2006) Formalizing the knowledge in a semantic wiki more stringently—from ad-hoc database queries to DL reasoning (Vrandečić & Krötzsch, 2006; Krötzsch, Vrandečić, Page, et al., 2007).
Most semantic wikis serve general purposes; as of January 2007, there is only one more semantic wiki dedicated to MKM besides SWiM: se(ma)2wi (Zinn, 2006) is an installation of Semantic MediaWiki. OMDOc content from the ActiveMath learning environment (Melis et al., 2006) has been automatically converted to MediaWiki’s syntax via XSL transformations and imported to the wiki. The pages are categorized by their OMDOc statement types (e.g., definition) and annotated with learning metadata from ActiveMath. All other semantic information from OMDOc is lost in the conversion: The formulae are given in presentational-only LaTeX, and the links between wiki pages that represent mathematical statements, for example a link from a theorem to its proof, are not typed, as they are in SWiM.
ers to contribute, wiki-like openness to anybody does not suffice. Unlike the text formats used by common semantic wikis, the OMDOc format makes the fine-grained semantic structure implicit in the text explicit in the markup, making it tedious to author by hand. Moreover, only after a substantial initial investment (writing, annotating, and linking) on the author’s part, the community can benefit from the added-value services supported by the format—for example, the creation of customized textbooks with ActiveMath. If the author and beneficiary of such services were different persons, though, only few persons would be willing to contribute to a knowledge base. This “semantic prisoner’s dilemma” (see chapter XI) can be overcome when the authors themselves are rewarded for their contributions by being offered special added-value services, which improve immediately the more annotations and cross-references the users contribute. In semantic wikis, there are even core services that instantly gratify users for their contribution to the knowledge graph: Dynamic navigation links visualizing part of the semantic annotations in the current context directly depend on the page contents editable by the user and thus instantly open up new views on related topics to the user (Aumüller, 2005, section 3.2). In terms of chapter III, SWiM is both semantically enhanced social software and a socially
Figure 1. The Semantic Web authoring challenge
Benefits of a Semantic wiki for mkm SWiM is intended to encourage collaboration: Nonmathematicians can jointly create a “Wikipedia of mathematics” by compiling the knowledge available so far, while scientists can collaboratively develop new theories. However, to encourage us-
SWiM
enabled semantic Web application: first, it enhances a wiki by ontology-based added-value services and uses a semantic markup format, and second, its added-value services lead to a better connection between contributions of different users (consider, for example, linking assistance by auto-completion).
an alternative semantic web Most semantic work environments are based on ideas and techniques from Berners-Lee’s Semantic Web. The Semantic Web uses RDF triples to describe resources and the background knowledge in ontologies to draw inferences about their content. While, however, in most areas of the semantic Web, resources (anything with an URI, for example fragments of XML documents) and statements about them (the ABox, “assertional box”) are separated from their context (a vocabulary and background knowledge encoded in an ontology, called TBox, “terminological box”), the content resp. context markup language OMDOc can express both of them, using the above-mentioned three levels of formalization: all OMDOc statements must be made in proper context. The context is provided by theories and, syntactically, indicated by a certain content markup. Consider the statements “all differentiable functions are continuous” (background knowledge) and “the derivative of the sine function, evaluated at 0, is 1” (assertion about resources): both can be expressed as OMDOc statements. This turns collections of OMDOc documents into referentially closed systems (all the knowledge referred to, that is, both ABox and TBox, can be expressed in the system itself), which in turn allows ontological bootstrapping: the ontologies needed to draw inferences can be built up as we build up the data. Note that only part of the mathematical knowledge embedded in mathematical documents can be exploited for ontological reasoning, as it cannot faithfully be expressed in first-order logic (much
less so in DL or RDF without reification). For the sake of this argument we will use the term Web ontology language synonymously with “description logics” (DL), as in OWL-DL; if we pass to more expressive logics like first-order logic, we lose decidability and thus the raison d’être for Web ontologies. Consider, for instance, the theorem that all differentiable functions are continuous (C1(R,R)⊆C0(R,R)). This subset relation can easily be expressed in DL (C1(R,R)C0(R,R)), if both C1(R,R) and C0(R,R) are declared as classes, but its justification via ε/δ arguments and the definition of Ck(R,R) cannot. Thus, any Web ontology that deals with objects such as the ones above will necessarily have to approximate the underlying mathematical knowledge. Generally in science, knowledge comes in documents and constitutes the context, whereas DL ontologies only reference and approximate the knowledge in a document. Therefore, with OMDOc we propose an alternative vision for a “Semantic Web for science and technology” where the ontologies necessary for drawing inferences are views derived from normative documents. Taxonomic relations are, however, only implicitly expressed in OMDOc: one can write statements (definitions, assertions, and so forth) about mathematical concepts, which, for example, state that one concept (e.g., the set C1(R,R)) is a subset of another one (e.g., the set C0(R,R)). Where ontological fragments cannot be derived automatically (an interesting research problem in itself), they can be embedded into OMDOc-encoded documents as OWL, and later simply extracted. Thus OMDOc, as a document format with embedded taxonomic information, serves as its own ontology language. Thus, for the time being, we restrict ourselves to that semantic information that can explicitly be expressed in OMDOc: those from the theory and statement level, for example, the import relation between theories. A subset of OMDOc’s system
SWiM
Figure 2.
we will concern ourselves with its information model: what a wiki page should comprise, what semantic information can be inferred from the OMDOc documents and the user interaction logs, and finally how this can be utilized.
data model The smallest unit in a wiki that can be displayed, edited, linked to, or archived is a page. Editing of and linking to page sections is possible in some wikis, such as MediaWiki, but only in a limited way. In a non-semantic wiki, one page is a document with arbitrary contents. In a semantic wiki, one page usually describes one concept; for SWiM, we have to consider the following aspects: ontology covering these levels is presented in Figure 2. In particular, the enhancements of the data model semantic wikis bring along—compared to traditional wikis—are already present in the OMDoc format, so that an OMDOc-based wiki only needs to operationalize their underlying meaning. For example, typed links, which are implemented via an extension to the wiki syntax in Semantic MediaWiki or editable through a separate editor in IkeWiki, are implemented by the for attribute in OMDOc (e.g., ). It remains left to the wiki to make them editable easily and to visualize them adequately. More than a general semantic wiki, one targeted at mathematics must ensure that dependencies between concepts are preserved. Results in this area will be interesting for nonmathematical semantic wikis as well, especially when they support higher levels of formalization such as ontologies.
design of swim Before we can go into the design of SWiM, its user interaction and its added-value services,
•
•
•
Ontology: Which OMDOc elements can be considered as concepts? This should be decided in consistence with the OMDOc system ontology. Usability: Small pages generally improve wiki usability, but it should not be too hard for users to split up a document into small pages. Validity: Wiki pages should stay valid OMDOc XML documents to ensure higher quality.
OMDOc groups closely related concepts into “theories” and advises to follow a “little theories approach” (Farmer, Guttman, & Thayer, 1992), where theories introduce as few new concepts as possible. A theory may introduce more than one concept, if they are interdependent, for example, to introduce the natural numbers via the Peano Axioms, we need to introduce the set of natural numbers, the number zero and the successor function at the same time. We follow this intuition and recommend that users restrict the pages of SWiM to single (little) theories to keep them manageable. Moreover, OMDOc distinguishes the knowledge elements in theories into constitutive
SWiM
ones like symbols, definitions, and axioms (these are indispensable for the meaning of the theory) and nonconstitutive ones, such as assertions, their proofs, alternative definitions of concepts already defined, and examples. OMDOc supports rolling out the latter into separate documents, provided they reference their “home theory.” So does SWiM, and additionally, it allows constitutive elements to be rolled out. Small pages improve the effectivity of wiki usage, as they facilitate editing and re-use by linking and allow for a better overview through lists of recent changes and other automatically generated index pages. To facilitate the import of large documents (e.g., courseware), SWiM does not force users to create small pages; actually, any valid OMDOc document can be a SWiM page. The user is, however, rewarded for giving each statement its own page, as most semantic annotations (e.g., page and link type) are only extracted per page. As the presentation module supports the inclusion of the contents of one document fragment into another document, the reader, or learner, can still coherently view a whole theory on one Web page.
The System Ontology, the Core of SWiM In order to facilitate making statements (here, RDF triples) about OMDOc concepts and, in particular, to facilitate semantic Web applications in re-using the knowledge contained in OMDOc documents, a common vocabulary, that is, an ontology, has to be fixed. As this ontology “express[es] the document structure [. . . ] as an ontology,” we will use the term system ontology coined in (Krieg-Brückner, Lindow, Lüth, Mahnke, & Russell, 2004, p. 280) for it. In Müller (2006b, p. 5), it is more precisely defined as “an ontology describing the data model of a system or the representation language the system and its applications are based on independently of their respective syntactical realization.”
SWiM differs from other semantic wikis in that it comes with a prebundled system ontology of a domain-specific data format. Most generalpurpose semantic wikis allow for importing or modeling arbitrary ontologies for arbitrary domains, but due to the great differences between those ontologies, they cannot utilize them further than for displaying navigation links, some editing assistance, and searching. As the OMDOc system ontology contains uniform terms for semantic relations between mathematical statements and theories, like “dependency” or “containment,”added-value services built on top of SWiM can be formally specified in terms of the system ontology. The most fundamental concepts in OMDOc, which constitute documents or parts of them, are theories and statements. The fundamental concepts in a wiki are pages and users. Basic relations are provided by the individual theories and statements. Then, there are basic relations given by the user interaction logs. Further, inferable relations can be defined as transitive closures of the former and as unions of OMDOc and wiki relations. Finally, there are other useful relations that the authors have to provide by manual annotations.
OMDOc Types and Relations Relations between OMDOc concepts include the import of one theory by another, the containment relation between a statement and its home theory, and the further specification of one statement through another one, for example, definition defining a symbol, an example exemplifying a statement, or a proof proving an assertion. All of the former ones can be subsumed by a generic “concept–depends-on–concept” relation, which is transitive. So far, SWiM does not extract semantic relations from OMDOc’s object level. The latter would be suitable for a future integration of computer algebra systems or automated theorem provers.
SWiM
Relations Given by User Interaction (to be implemented) The basic relation given by user interaction is, “Who edited which page when?” This information is available for free in a wiki; it can be logged when a page is saved. Accordingly, a relation that states that a user read a page could be defined—this is, however, hard to determine because of HTTP caching. Further relations can be defined by user feedback to navigation choices proposed by the wiki.
Inferable Relations (to be implemented) Further relations can be inferred from those introduced so far, for example a metric estimating the degree of difficulty of a concept, calculated by counting the questions on its discussion page, as soon as discussion pages, as known from MediaWiki and widely used in Wikipedia, and additional OMDOc elements for structuring them (questions, explanations, opinions) have been implemented. From the user interaction log, sets of related pages can be identified, which are not already related through dependency. For this purpose, a notion of transaction must be introduced, that is, edits carried out by the same user in short succession. Just as for products bought in online shops, two theories are considered “related” when many users edited them in the same transactions. Even more sophisticated relations can be inferred from both OMDOc and the SWiM interaction relations. The software could, for example, track, how many examples to a theory users read and improve the difficulty estimation by including those statistics.
Metadata Furthermore, SWiM should allow the user to search and enter metadata associated with any wiki page. OMDOc allows for annotating documents and fragments of them with Dublin Core metadata
and Creative Commons licensing information (Kohlhase, 2006, Chapter XII). Part of them, such as the last editor and the last editing date of a page, are recorded by any wiki, while others, such as dc:description, will be made editable via a separate form. IkeWiki, on which the system SWiM is based, supports metadata about pages, thus integrating OMDOc metadata into IkeWiki’s user interface is an important to-do item.
OWL-DL Implementation So far, a subset of the OMDOc system ontology has been modeled in OWL-DL, covering most of the ST module (statements, Kohlhase, 2006, Chapter XV) and a small part of the PF module (proofs, Kohlhase, 2006, Chapter XVII). Other parts of OMDOc still need to be modeled, for example abstract data types (module ADT, Chapter XVI)), complex theories and development graphs; modules CTH and DG (Chapter XVIII). The concrete implementation of the ontology has been designed in a modular, extensible way using owl:imports. One main file includes the files that model the respective OMDOc modules, and each of them inherits the generic base classes and relations defined in another shared document. It is being continuously expanded and adjusted to the needs of SWiM and other OMDOc applications. Figure 2 shows the most important concepts (in OWL: classes) and relations between them (in OWL: object properties) that have been modeled.
Extracting Semantics from OMDOc XML per se does not carry any explicit semantics, so ways of extracting the implicit semantics—as, for example, specified in a human-readable documentation of the respective XML document format—and making it explicit as an RDF ABox (possibly backed by an RDFS or OWL TBox) must be found. An informal solution to that problem
SWiM
is writing an ad-hoc XSL transformation that is specialized to a specific XML input format (OMDOc in our case) and outputs an RDF/XML ABox using a specific ontology (the OMDOc system ontology in our case), as proposed by the GRDDL (Gleaning Resource Descriptions from Dialects of Languages, World Wide Web Consortium, 2006) W3C standard. SWiM cannot use RDF/XML directly; an in-memory representation of an RDF graph as a result of the ABox extraction would be preferred. So far, this is hard-coded in a mixture of procedural and declarative style, but we are looking for a more formal solution, which is more scalable. WEESA (Reif, Gall, & Jazayeri, 2005), a powerful declarative language that defines a mapping from XML to RDF using classes and properties from a given OWL ontology and XPath expressions for extraction, looks promising and will be evaluated for integration into SWiM.
user interface Rendering Pages are presented to the user in a human-readable form (XHTML plus presentation MaThML) generated by a multi-pass XSL transformation (Kohlhase, 2006, Chapter XXV). The XHTML contains inline hyperlinks where appropriate, for instance, from a symbol in a formula to its definition. As OMDOc documents, however, need not contain any human-readable sections or comments—after all, the knowledge base might be used to support a theorem prover, not to create a textbook!—there is also a source code view with lines indented, keywords highlighted and URIs displayed as hyperlinks. An intermediate view mode that displays mathematical objects in the source code as formulae using MathML or TeX -generated images is planned.
Dynamic Navigation Links Displaying dynamic links to concepts related to the concept described on the current page—as, for example, import links on a theory page—improves usability by answering the questions “Where am I?” and “Where can I go?” (Aumüller, 2005). If the knowledge base contains RDF triples with the current page as subject or object, these triples are displayed on a navigation bar (labeled “references”), grouped by incoming and outgoing links and by their type (i.e., the predicate; see Figure 3).
Editing While wiki pages can be edited in a WYSIWYG editor in IkeWiki, this is not yet possible for OMDOc pages in SWiM, as OMDOc is much more complex than wiki markup. Currently, OMDOc pages can only be edited in a slightly simplified raw XML representation. Following the wiki spirit, there is a short-hand syntax for links: A statement on a theory page can be referenced as theory#statement instead of the full URI reference. More comprehensive measures to make editing more user-friendly are planned.
implementation notes SWiM, as it is presented in this chapter, is currently in a prototype stage under active development, which is available under the GNU General Public License from http://kwarc.info/projects/swim/. We have based our system on IkeWiki as a development platform because of the modular design of back-end and GUI, its rich Semantic Web infrastructure, including the Jena Semantic Web framework (“Jena,” 2007), the Pellet OWL-DL reasoner (Sirin, Parsia, Grau, Kalyanpur, & Katz, 2006) and RDF import/export, and the user assistance for annotation. IkeWiki is implemented
SWiM
Figure 3. A theory page with navigation links
in Java, using Java Server Pages. The wiki pages are stored in a PostgreSQL database, which also hosts Jena’s RDF triple store. The triple store not only contains page metadata and semantic links extracted from the pages, but also RDF representations of the ontologies used by the system—including Dublin Core for the metadata, as well as the OMDOc system ontology. Some parts of SWiM are, however, very different from IkeWiki’s operating principles and hence required substantial amounts of refactoring and rewriting; for example: •
•
The presentation view of an OMDOc page, for example, cannot be generated by a singlepass XSL transformation from OMDOc to XHTML+MathML; instead, the multi-pass OMDOc presentation workflow (Kohlhase, 2006, sec. 25) had to be adopted. In contrast to wiki text pages, which can (optionally) be edited in a WYSIWYG edi-
•
tor, OMDOc pages can only be edited via the source editing interface so far. The semantic relations between OMDOc theories are not exclusively stored as RDF triples, as is the case with semantic relations between IkeWiki pages; instead, SWiM has to keep the annotations in OMDOc synchronized with the knowledge base, which is still used for reasoning.
We did not integrate OMDOc into IkeWiki by replacing code handling traditional wiki text by new, OMDOc-specific code. Instead, we extracted generic code to base classes and created subclasses both for wiki text and for OMDOc. This peaceful coexistence of two formats can easily be extended to other semantic formats, such as future OMDOc derivatives for other sciences. The prototype, see Lange (2007) for details, still has many limitations, which we plan to overcome in the future (see https://trac.kwarc. info/swim/ for bug tracking and feature plans).
SWiM
Figure 4. Refactoring of wiki classes before adding OMDoc functionality
• •
•
•
•
•
Feedback in case of invalid XML and semantic inconsistencies needs improvement. The ABox extraction (i.e., the mapping from XML elements to ontological concepts) should be formalized instead of being hardcoded. The metadata editor and storage facilities of IkeWiki and the metadata capabilities of OMDOc must be integrated. The rendering must be improved w.r.t. readability (rendered formulae in the source view) and navigation (inline links not only in the navigation box, but also in the document view). Exporting the ABox to other Semantic Work Environments as RDF/XML is possible, but importing knowledge must be implemented: Importing RDF is possible, but it is not accessible through wiki pages, and importing OMDOc is not yet supported. So far, we have not optimized SWiM for performance. The rendering of pages in presentation mode will receive major optimizations, for example, by caching.
future work: swim as a serviCe platform Over the next 2 years, we plan to evolve SWiM into an integrated platform for added-value services for technology and science.
The base system of SWiM—that is, IkeWiki with OMDOc as its page format—is almost complete, and its advantages and shortcomings have been evaluated (Lange, 2007, section 5). Realizing the features for lowering the burden of contributing to a SWiM site, for rewarding users for their contributions and for exploiting the contributed knowledge will, however, is not be possible through simple hacks or ad-hoc development. Furthermore, it is crucial that the system and the services will be independent of a particular scientific domain and the content entered into the system—otherwise, the system itself would have to be ported to a new domain, not only the disciplinary content exchanged. So to arrive at a sensible level of integration, we need a service interface that only builds on the OMDOc system ontology. Furthermore, we aim to make the system as independent of the concrete OMDOc language as possible (to make it applicable to other sciences); therefore we plan to abstract the system ontology to an “upper system ontology”1 (that models the information about “containment” or “dependency” needed by the services), of which the OMDOc system ontology is a specialization. This will allow application of certain services to all specializations of this upper system ontology, that is, to other scientific markup languages. We will not restrict the system ontology to the language part, but model the whole system (i.e., SWiM) in the system ontology, which is part of
SWiM
the system architecture, not editable by the user. Note that the wiki-specific part of the ontology is already available in IkeWiki. The SWiM prototype does not yet utilize more of it than IkeWiki already does, but some of the planned interactive services will. Basing part of the system’s behavior on an explicitly represented ontology rather than hard-coding it is beneficial, since it supports conceptual clarity and rapid prototyping. Including the SWiM components into the ontology allows including, for example, user interactions into the system model. To determine the requirements for the service API, we will formally specify some of the planned services with regard to the following aspects:
Navigating the Dependency Graph
•
•
•
•
•
•
What kind of added value does it provide to individual users and to the community, respectively? How much knowledge does it use? Just the text of the current page, semantic information about the current page, or (explicit or inferred) information about relations between multiple documents? Does it only depend on the system ontology behind the data format used (e.g., OMDOc), or does it rely on a specific notation (e.g., XML)? Does it offer a one-step workflow, or does it require additional user feedback, before further steps are executed? Should it be entirely implemented as a part of SWiM, or does it make sense to integrate an external tool instead?
Figure 5.
The user shall not only be able to navigate along the dependency graph given by the transitive closure of the depends relation using dynamic navigation links; he shall also be able to explore dependencies interactively. Suppose that the user is currently reading a page about the theory ring, which depends (via import) on group and monoid, with group depending on monoid and monoid in turn depending on semigroup. In this case, the wiki shall not only display navigation links to the direct dependencies group and monoid, but it shall also provide unobtrusive buttons that allow the user to give one of the following acknowledgments:
•
•
•
No, thanks! “I already know group and monoid, please let me just read about ring.” Explain “Please show me group and monoid so that I can learn about ring’s prerequisites.” Group and monoid will be displayed. Explore “Please show me all prerequisites for ring.” In our example, these are group, monoid, and semigroup, which could be opened in separate windows or serialized into one page. Suspend “I want to know about group and monoid, but only later.” The system keeps a notice in the user’s profile that he wants to read group and monoid sometime. Reminder links to suspended concepts are shown on a separate navigation bar.
Figure 6.
SWiM
Not only the last case should be recorded—the others are interesting as well for social bookmarking. For example, if many users requested a concept c to be explained, the system could default to display not only the direct dependencies but also the level-two dependencies, for it seems that c is too difficult for only being explained shallowly. Furthermore, the system will not only keep track of which concepts the user wants to be explained, but also which concepts the user has already learned. For each concept, a button will be offered for telling the system “I have learned this.” Links to concepts learned can then be disabled or displayed in a more unobtrusive color than links to concepts that are new to the user. Concretely, this service comprises two steps: 1.
2.
The first step (making suggestions, presenting the action buttons) requires as input the currently viewed concept c, a reference to the dependency graph, and, possibly later, the user’s preferences and background knowledge. Its output is a tree t of concepts that c depends on. DL reasoning is needed in this step. The second step (displaying wanted pages, bookmarking) requires as input c, t from step 1, and the information which button the user pressed. It returns the desired pages to the user and keeps a bookmarking record in the knowledge base.
Another idea for improving navigation is presenting the details of theory imports together with the respective navigation links. If inheritance via renaming is used, for example, when fixing the multiplicative structure of a ring by importing the monoid theory, then the morphism that maps the monoid’s ◦ operator to the ring’s multiplication operator · and renames the identity element from e to 1 could be displayed on request. It remains to be investigated whether theory morphisms can be adequately modeled in the OWL-DL system ontology, that is, whether this service can be implemented on top of the ontology part of the
0
service interface. For example, in OWL-DL, it is not possible to annotate an import link between two theories with an additional property, that is, the morphisms used for importing.
Change management assistance So far, there has not been any approach to preserving dependencies between pages in a semantic wiki. Tracking dependencies and reasoning about them is an integral part of mathematical practice and hence cannot be neglected in a semantic work environment for mathematics. Known results are often generalized to find the “real” dependencies, mathematical theories and books are rewritten to make dependencies minimal. In the special case of OMDOc, where dependencies need not be formally verifiable when they have sufficient structural properties, a dependency could formally be broken but seem intact to the system nevertheless. If, for example, a theory t depends on a theory t’, which can be edited independently from t and still is under development, modifying t’ might break t because some axiom in t’ required by t might have been changed. A lightweight, simple-minded solution to this problem is based on the evident approach to have all hyperlinks not point to concepts in general but to specific versions of them. (Recall that old versions of a page are available for free in a wiki!) When an author enters a link to a theorem thm, for example, this reference will be stored internally as thm/v _ latest. Editors of documents with outdated links will be offered to update them: 1.
2.
For each concept di linked from the currently edited concept c, the version numbers vi in each link are checked for up-to-dateness. All (di, vlatesti ), where vlatesti > vi , are returned. The editing box on the user interface shows indicators next to each updatable link di. If the user clicks on such an indicator, a pop-up dialog with links to di/vi (i.e., the old version of page di), di/vlatesti and a comparison
SWiM
3.
page diff(di/vi, di/vlatesti) showing an XML diff, probably formatted by a diff viewer2 , as well as two buttons labeled “keep” and “update” appears. An alternative user interface could allow the user to select multiple links with check boxes and have all of them updated at once. If the user wants to have the link di/vi updated, its source code is replaced by di/vlatesti.
Note that this specification is independent of the definition of a “dependency link” in the system ontology; it does, however, make sense to restrict the algorithm to those links that actually denote dependencies. Furthermore, manual confirmation of an update should only be demanded when the semantics of di has changed. As this is nontrivial to decide, editors should have the possibility to classify their changes. Many wikis already distinguish between “major” and “minor” changes. More sophisticated classifications of changes in the context of ontologies are discussed in Klein, Fensel, Kiryakov, and Ognyanov (2002), Müller (2006b), and Plessers and Troyer (2005). A second service could warn the user upon changing a concept e that many other concepts f i depend on, that changing the semantics of e might affect the integrity of the f i: the service queries the knowledge base for a list of all concepts {f i}i depending (via the transitive closure of the dependency relation) on the currently edited concept e. To the user, this list can be presented as a warning like “n concepts depend on the one you are editing.” If the user makes a major change (the classification mentioned above) that affects many dependents, SWiM could offer copying e to a new concept e’ leaving e intact for the dependents to reference. So far, we have described a simple-minded assistant that helps human editors to prevent common mistakes in change management. Real change management solutions both from the domains of structured data formats and ontologies will be evaluated in the context of SWiM: The
locutor project (Müller, 2006b) developed in our group aims at realizing a practicable ontology-based change management for OMDoc and other structured document formats on top of informal document engineering processes. Change management for generic structured documents with semantic interrelations has been realized for MMiSSLaTeX (Krieg-Brückner et al., 2004), a structured LaTeX-based format whose system ontology served as an inspiring example for OMDOc’s system ontology. Change management for mathematical and logic-based documents with strong dependencies modeled by development graphs, which are also supported by OMDOc (Kohlhase, 2006, Chapter 18.5), but not yet regarded by the OWL-DL implementation of the system ontology, has been formally investigated in (Hutter, 2004). Change management for OWL ontologies is described in (Klein et al., 2002). We anticipate that an integration of locutor can turn the change management assistant introduced above into an automated service that requires less human reasoning and is therefore tractable for larger document collections. locutor allows users to classify their changes a “taxonomy of change relations” and will be able to find out whether one change actually affects other documents by computing “long-range effects” of changes (Müller, 2006b). It will either be able to automatically make adaptations required after a change, or at least it will pinpoint all effects of changes, so that a human editor would exactly know what to fix. A locutor prototype is currently being implemented as a modular extension of the version management system Subversion (“Locutor,” 2007); thus, it can be integrated into SWiM as an alternative back end.
User-Friendly Editing In contrast to usual wiki text, OMDOc’s XML syntax is hard to edit because of its verbosity and the XML validity constraints. Therefore, SWiM must offer some assistance to authors. We
SWiM
are currently investigating several approaches: a very simple form of authoring assistance is to split documents into smaller parts to enhance manageability. For the Dublin Core metadata in the OMDOc documents, we can utilize the formbased editor from IkeWiki. Generally, we want to integrate external OMDOc editors that offer assistance on their part, and develop a simplified syntax for text fragments that do not use the full representational power of OMDOc. Note that all of these measures can be combined. Two other editing assistance measures warrant a closer look and a more thorough discussion.
2.
Section-Wise “Edit in Place” Users can manually split large OMDOc documents into their individual concepts in the SWiM prototype, but in some cases, even a single concept can be too large to edit—consider a complex proof with many steps or case distinctions. Some wikis, such as MediaWiki, allow for editing individual paragraphs of pages (Wikimedia Foundation, 2006a). The Edit-in-place interface (The Connexions Team, 2006) of the Connexions system (see also chapter XI) is even more user-friendly; it is particularly suitable for editing or inserting sections in large XML documents with shallow structures. The documents are displayed in a near-WYSIWYG view, but clicking on a section replaces its view by a text area containing its XML source. The section can be deleted or edited and saved by an asynchronous request to the server. The user interface to the edit-in-place service will be embedded into the presentation mode: If the user has the permission to edit a page, an “edit” button is added to every section. The user interacts with the service in three steps: 1.
In the first step, the current page is structured section-wise. This is implemented as a part of the transformation of the page for presentation. To determine which XML elements
3.
denote sections, the service first queries the system ontology of the language of the current page for subclasses of the “section” class from the upper system ontology; then it queries the ontology-to-XML mapping for those XML elements that represent them. The output is a presentational view of the page, with each section marked (e.g., by a frame) and prepared to be edited upon user’s request via embedded JavaScript code. The user triggers the second step by selecting a section for editing. The service is provided an identifier of the section (e.g., its xml:id or an XPath expression). The presentation view of the respective section is replaced by an editing box with the source code of the section’s text and buttons for saving and canceling the edit as well as deleting the section. “Save” and “Delete” requests are sent to the server, while “Cancel” can be handled on the client by just replacing the editing box with the cached presentation view. If the user requests the section to be saved or deleted, the third step is triggered. The source code of the page, with the respective section replaced or deleted, is stored to the page database. RDF triples whose subjects are fragments within the section are re-generated. While it is desirable to have only the replaced section re-rendered for presentation—instead of the whole page—it is open whether that is possible using the available transformations of the respective scientific markup language to XHTML.
For mathematical formulae, Edit-in-place must be augmented with specialized facilities that cater to their deeply nested structure, and theory-driven visibility of symbols. This can be done either by short-hand languages for mathematical formulae like LaTeX or even QMath (Palomo, 2006a), using a batch processor that transforms these to OMDOc. Or SWiM could employ specialized
SWiM
OMDOc editor plug-ins at the formula- or even page level and make use of the existing OMDOc editing tools, for example, an OMDOc-mode for the popular Emacs editor or Sentido (Palomo, 2006b), a Mozilla extension for near-WYSIWYG editing and browsing OMDOc documents.
Auto-Completion When the user enters a link like CE + CR. Figure 1 shows the general personal knowledge management dilemma: we never know if our costs of authoring and retrieval are worth the effort.
Cost of Authoring A rather simple form of authoring is writing plain text. In a next step, a user can add formatting to the text, which gives it a structure. For example, different levels of headlines imply a tree structure. Upon retrieval, one can then more easily navigate
to the relevant part of a document. Furthermore, a user can add cross-references to other parts of the same text or to other documents. In academic works, such cross-links enhance the chance for successful retrieval; for example, a citation to another work makes the other work more likely to be found. Each step of externalisation described so far lowers the cost for retrieval (CR) but comes at the expense of higher externalisation costs (CE). Articulating semantic statements about concepts or semantic links between concepts has high costs in many tools (e.g., ontology editors such as Protégé), since the user must change his familiar user interface paradigm (document and text editing) for a different paradigm (ontology editing) and must fully formalise all content or loose the relation between the concepts in the document and the concepts in the ontology.
the Cost gap To sum up the situation, current tools offer two primary choices: On the one hand, one can make very “cheap” notes, which have little structure and thus have a low chance to be found other than through a keyword match on the full-text. This low-cost strategy (comparable to, for example, post-it stickers) does not scale if many documents about the same topic exist. More formally, the cost of externalisation (CE) is low, but the costs
Personal Knowledge Management with Semantic Technologies
of retrieval (CR) are high, as one needs many searches before finding a note again—if it is found at all. On the other hand, one can use a custom database application or ontology editor with high costs of externalisation to lower the search costs. The high costs, due to the paradigm switch and the strict constraints of the editing environment, are often too high for everyday information management as one cannot sit down and design a database or ontology when trying to externalise some fact obtained, for example, from an e-mail. This PKM cost gap can be bridged in two ways. One can lower the cost of search on collections of loosely structured notes. Desktop search engines do this by offering fast full-text search. Other approaches like ontology learning try to extract structures from unstructured data. Alternatively one can lower the cost of authoring information with explicit structure and/or semantics. This will also lead to lower search costs, as more structured data leads to higher precision (Kando, 1997). The second approach, lowering the cost of authoring structured knowledge, is the one we pursue in this chapter.
Outline In the remainder of this chapter, we present general requirements for PKM obtained from a literature study. Then existing “classic” (nonsemantic) PKM tools are reviewed. Next, the notion of a semantically-enhanced PKM tool (SPKM), see Figure 3, is introduced as a novel approach to the PKM problem. The following section reviews existing prototypes of SPKM tools and lists their drawbacks. We then present personal semantic wikis as a best-of-breed implementation of the SPKM vision. In this approach we do not use wiki technology as a community platform but as a personal authoring environment. The final section discusses future trends and concludes the chapter.
0
reQuirements for personal knowledge management We live in a knowledge society in which people have access to tremendous amounts of information and communicate with others all over the world. Although most of this information and communication is digital, people still predominantly use traditional analogue techniques: several studies (Blandford & Green, 2001; Campbell & Maglio, 2003; Jones & Thomas, 1997) show that simple to-do-lists, paper calendars, address books, and diaries are the most commonly used tools, all of which are analogue paper-based tools. Although e-mail is increasingly used for some personal information tasks (Bellotti, Dalal, Good, Flynn, Bobrow, & Ducheneaut, 2004; Whittaker, Bellotti, & Gwizdka, 2006), it is mostly unstructured (Dai, Lutters, & Bower, 2005).
Requirement 1: Acceptable Costs As argued, a working PKM solution must have acceptable costs both for externalisation and for search. Based on an exhaustive literature analysis of information management and knowledge work (Oren, 2006),1 we derive six additional requirements for personal knowledge work.
Requirement 2: Focus on the Individual Many works on information and knowledge management indicate that “knowledge is ultimately created by individuals” (Polanyi, 1958). This motivates our conceptual shift from organisational knowledge management to personal knowledge management. Individuals are personally committed to knowledge creation (Nonaka, 1994) but this commitment relies on their intentions (understanding and actions of individuals) and on their autonomy (self-motivation and freedom to pursue their intentions). Personal autonomy is
Personal Knowledge Management with Semantic Technologies
thus crucial and individuality and freedom should be supported by tools. Traditionally, three types of office workers can be distinguished (Kidd, 1994): the knowledge worker (who creates new knowledge), the communication worker (who amplifies information and connects people), and the clerical worker (who manages documents). All three of them perform administrative tasks, which are repetitive, structured, and document-driven, and research tasks, which are flexible, unstructured, and information-driven, but do so in different proportions: clerical workers perform mostly administrative tasks, while knowledge workers mostly do research tasks. These research tasks usually have no structured procedures and workers have no clear idea of their next steps. The unstructured nature of their work makes it difficult to support knowledge workers in general, and highlights the need for their personal autonomy and freedom.
Requirement 3: Forget Rigid Classification Strict hierarchical classification does not work for many individuals (Hearst, 2006); therefore we see a rise of more flexible structures: tagging and ontologies. Many people categorise information mainly by context (Lansdale, 1988) and retrieve information based on contextual clues (associations). Contrasting, most classifications in the computer are hierarchical (e.g., file folders), which leads to usability problems (Randall, Bowker, & Leigh Star, 2001). Although research has shown that people prefer category-based search over keyword-based search (Yee, Swearingen, Li, & Hearst, 2003), using strict hierarchies of categorisation worsens the results since they do not work well for most people. The activities of knowledge workers are highly unstructured; the intended use of documents (relevant for later retrieval) is often unclear at the time of filing (Bondarenko & Janssen, 2005; Kwaśnik 1983).
Requirement 4: Follow the Links Although desktop search greatly helps individuals in retrieving their own files, users actually prefer to find information not by searching and jumping to it but by orienteering and browsing between related items (Teevan, Alvarado, Ackerman, & Karger, 2004). Such exploration techniques are not only preferred in an unfamiliar domain (or when browsing somebody else’s data) but also when investigating personal information spaces (Cutrell & Dumais, 2006; Schraefel, Wilson, Russell, & Smith, 2006). This preference stems from the fact that people often have difficulties unambiguously specifying what they are looking for and thus prefer browsing over searching (Barreau & Nardi, 1995). Furthermore, human memory can greatly benefit from context information which is enabled by exploratory browsing between related items. Users clearly benefit from being able to follow the links in their data and browse their information space. The ability to automatically identify and present links between relevant data requires the data to be interlinked and semantic relations between data elements to be identified.
Requirement 5: Remember the Context Contextual information is crucial in human information retrieval. People categorise information based on its context and recalling therefore also benefits greatly from contextual information (Lansdale, 1988). In a personal classification system, the classification of a document is strongly affected by its intended use and context (Kwaśnik, 1983); that means that we should capture such document context to facilitate retrieval. Dumais, Cutrell, Cadiz, Jancke, Satin, and Robbins (2003) report that rich contextual information such as people’s names and dates, that is, the personal and temporal dimensions, provide beneficial cues for retrieval in a personal information system and seem even more important than standard ranking
Personal Knowledge Management with Semantic Technologies
functions. Which context information to use in knowledge management is still an open question. Often used dimensions are the five “who, what, when, where, how” or the “who, what, when, where, why” dimensions (Ranganathan, 1962).
Requirement 6: Value the Power of paper Despite all the progress of our PC desktops, physical paper remains a crucial tool for most people. Even the advent of the Internet has only increased the amount of printed paper (Sellen & Harper, 2003, p. 7). This seeming paradox (a continuous rise of paper usage together with an increased use of digital media) is understandable since (i) the Internet gives people access to more and more information which often ends up printed, since (ii) printing technology is evolving, making printing easier, faster, and better, and since (iii) paper is extremely well-suited for authoring, reading, and reviewing documents (Sellen & Harper, 2003, p. 13-15). Research has shown that reading stimulates writing (Adler, Gujar, Harrison, O’Hara, & Sellen, 1998) and that paper is very well-suited for combined reading and writing because of its possibilities for flexible, spontaneous annotation (draw or write with a pen), quick navigation between documents (simply flip a page), and spatial layout to form a mental model of documents (O’Hara & Sellen, 1997). A recent study showed that 85% of reading activities were paper-based although almost all information was available to people digitally, on their computer. It seems that digital technologies, rather than replacing paper, shift the point where paper is used: from publishers to the individuals who download, print, and read documents. Also, paper fits the requirements for individual autonomy and freedom very well: compared to digital media, paper puts almost no restrictions on the content that can be written on it (sketches, text, or both).
Requirement 7: Keep it Simple Perhaps the most important requirement shown in the literature is the simplicity of tools. The adoption rate of digital technology for personal information (even in today’s age of ubiquitous mobile phones and PDAs) is quite low (Jones & Thomas, 1997). This relatively low adoption may be explained by the unawareness of most users with the features of their existing tools; most people, for example, are even unaware of long-existent features such as automatic e-mail filtering (Bondarenko & Janssen, 2005). Research has also shown that people use many tools quite differently than expected; for example, people use folders on their computer not only to organise their files but also to remind them of tasks, to decompose problems, and to plan their work (Barreau & Nardi, 1995; Jones & Thomas, 2005). Simple tools do not constrain user workflows but support their autonomy and are easy to understand and use.
Requirement 8: Keep the Flow As an additional requirement from the authors own observations, a support for personal work processes is crucial: One must allow the information and structures to travel from one application in a workflow to the next. We illustrate this requirement with an article writing scenario. Writing is a central activity for all kinds of knowledge workers. They have to compile reports or write articles for scientific journals. Writing an article includes reading related work—and often also taking personal notes on it. Then an outline or other kind of high-level structure is usually created (Esselborn-Krumbiegel, 2002). This structure is then refined to the argument-level and fleshed out into a linear text. Next, the text is partially rewritten and references to figures, other sections and literature are added. Eventually the text is typeset and thus the final layout is created.
Personal Knowledge Management with Semantic Technologies
state of the art in “ClassiC” pkm approaChes and their proBlems Several different approaches for personal knowledge management exist. In the following, we concentrate on popular tools used for this task: Weblogs, wikis, mind-mapping, and personal information management (PIM) tools. We also discuss common problems for personal knowledge management in these tools.
weblogs A Web log is a specific kind of personal Web site where content is published in the form of small articles and displayed in reverse-chronological order (latest article first), similar to a personal but publically readable diary. Readers can leave comments to articles. A particularly interesting feature of Weblogs is the so-called Trackbackfunction which allows a Web log to become aware of other Weblogs that refer to its articles, and the so-called Blogroll which lists or even syndicates other Weblogs that are interesting to the owner. These two features together allow forming the so-called Blogosphere, which describes the network formed between personal Weblogs by hyperlinks. Weblogs are primarily interesting not because of their technology but rather because of the social interactions they enable by commenting and referring to each others Web log articles. A Web log unfolds its true value only when connected with others. In personal knowledge management, Weblogs are mainly used to record ideas and other knowledge bits quickly. Since articles are usually publically readable, external users can comment on them and thus help improving the quality. On the other hand, private, confidential, or not yet very elaborate ideas should often not be publically available; some Weblogs support this by restricting
the group of people that can read articles. In Weblogs, access to knowledge is primarily oriented on the time-axis, that is, browsing through articles primarily by publication time. Some Weblogs allow users to associate articles with additional categories that support a more selective browsing through the articles.
wikis A wiki (Leuf & Cunningham, 2001) is essentially a collection of Web pages connected via hyperlinks. Many different wiki systems exist, but they commonly have a straightforward interface for editing content with a simplified syntax that makes it very easy to set hyperlinks to other pages within the wiki. Therefore, content in a wiki is usually strongly connected via hyperlinks. Furthermore, editing of content in wiki systems is Web-based and access is often unrestricted or at least hardly restricted. Most wiki systems also provide a rollback mechanism for reverting back to previous versions in case of accidental or undesired changes. Wikis are used in many areas, like encyclopaedia systems (e.g., Wikipedia), as personal or group knowledge management tools, as collaboration tools, or in collaborative learning environments. Concerning personal knowledge management, wikis can be used as very flexible and powerful tools (Wagner & Bolloju, 2005). The simple wiki syntax allows users to easily create content with a low technical barrier, and since it allows entering free text, the user is free to choose his own process and workflow. Easy hyperlinking allows connecting knowledge for navigation purposes and improves the retrieval of relevant knowledge. Cleverly used links and back-links allow also for hierarchies and categorisation. The plug-ins available for many wiki systems provide additional means of entering and visualising content, for example, as a calendar, as a task list, and so forth. Content can easily be made publically avail-
Personal Knowledge Management with Semantic Technologies
able, and most wikis allow restricting access to content to specific user groups. It is also possible and useful to install a wiki on the user’s personal computer. There even exist projects that aim to install a personal wiki on a USB stick. The main disadvantage of wikis with regard to knowledge management is that whereas creating content is easy, retrieval usually is not. Users are often limited to full text search and hyperlinks, which often does not allow to find the relevant content, for example, when synonyms are used or when the hyperlinks are not set properly. Also, wikis that are not maintained very well tend to be rather chaotic, which further aggravates the problem. For note-taking, wikis typically do not allow users to indicate the context of notes (notes are usually related to projects, tasks, responsibilities, e-mail communication, etc.). Therefore users cannot query their personal notes, for example, to find all notes about a certain e-mail discussion or navigate between two notes related to the same project. All navigation links have to be added explicitly because current applications do not support the personal meaning (semantics) of the notes.
sheet of paper/the computer screen only suffices for the visualisation of relatively few concepts at once) and the fact that a mind-map is always centred on a single concept.
personal information management (PIM) Tools Personal Information Management tools usually offer ways to manage a calendar, appointments, tasks, and addresses. Often, e-mail and simple note taking are also included. Popular PIM applications are MS Outlook, KDE Kontact, and Gnome Evolution. Recently gaining importance is the combination of the Google services Google Mail, Google Calendar, and Google Docs. The main advantage of PIM systems is that they integrate the different knowledge sources of office workers into a single interface. Unfortunately, most PIM tools are simply a collection of different systems and the actual information integration is not very deep. Neither is it possible to query the information nor are the relations between information items explicitly represented.
mind-mapping Mind-mapping and concept mapping are methods for structuring ideas, words, topics, or other items using graph representations. Centred around a key concept, further items are arranged around the centre concept. Mind maps are used in many different areas, for example, brain storming and collection of ideas, note taking, learning, summarising, structuring, and so forth (Haller, 2002). Mind-mapping is not bound to computers; the method is much older and can equally or even superiorly be used on paper. Mind-mapping is a traditional tool for personal knowledge management. Its main advantages lie in the structuring of content and the quick overview one gets when looking at a mind-map. The disadvantages are the limited scalability (a
summary of existing approaChes Weblogs are meant as a tool for the individual (Req. 2) for publishing and do not work well for restructuring knowledge. Strengths of Weblogs and wikis are handling of links (Req. 4) and simplicity (Req. 7), but Weblogs lack acceptable search costs (Req. 1), context of notes (Req. 5), and import/export support (Req. 8). A comparison table can be found in Figure 2. A wiki is great to keep a big repository of linked snippets, but it is hard to get an overview of the stored content. Wikis focus mainly on collaborative usage (Req. 2); their interlinked nature allows finding content by associative browsing (Req. 1).
Personal Knowledge Management with Semantic Technologies
Figure 2. An overview of existing PKM and SPKM tools; requirements
Legend: + = feature present, ~ = feature partially present
Figure 3. Semantic personal knowledge management supporting externalisation (authoring) and internalisation (learning) of personal knowledge
Mind-map tools are probably the only tools which have a paper-like work style (Req. 6). They are simple to use (Req. 7) and often have export functions from mind-map to textual outline (Req. 8), however usually additional links and icons are lost and re-import is impossible. PIM tools are good for the narrow domains they are designed for, but fall short when a set of structured notes has to be managed (Req. 1). At least they often can export structured content in usable formats (appointments, contact data, etc.). Overall, acceptable search costs and integration into workflows are the weakest points of existing PKM tools.
introduCing semantiC personal knowledge management (SPKM) We define an SPKM tool as a PKM tool that supports personal knowledge management by managing additional explicit semantic representations. An SPKM tool allows a user to maintain a personal explicit representation of his world view. Instead of large document collections a knowledge worker can centre his work on a single personal knowledge model (Völkel, 2007). For an SPKM tool to be useful, it should offer a good ratio between the effort it takes to externalise and (partially) formalise knowledge and
Personal Knowledge Management with Semantic Technologies
the benefit gained by enhanced query answering and browsing abilities. Figure 3 depicts the knowledge processes described in Nonaka and Takeuchi (1995) as they happen in PKM. Socialisation (direct face-to-face) becomes rare in an always online world. As most communication with oneself (PKM) and others (collaboration) happens through digital channels, efficient externalisation and internalisation are becoming the PKM bottleneck. By mapping structural features of a document to semantic statements of the underlying knowledge model, the computer could assist the user much better. Tables are a particular example of structures with implicit semantics, which are quite difficult to formalise (Pivk, Cimiano, & Sure, 2005). Existing tools do not handle semantics of structures: For example, John might write a document, and mark some parts in red; these markings mean “statements do be discussed with Alice.” If he exchanges the document he needs to communicate these ad-hoc semantics (discuss with Alice) implied by structures (red) as well. Currently, he would do so separately, by e-mail or phone. Making the semantics of structures explicit allows for better search (“what has to be discussed?”) and more efficient knowledge exchange. A truly usable SPKM system should allow the user to use the different editing paradigms (wiki, document, mind-map) at wish—on the same data. Existing PIM objects (tasks, addresses, appointments) and desktop resources (files, folders) have to become first-class citizens, so that they can be annotated and interlinked as well. The importance of flexible authoring methods has been recognised in knowledge engineering (Fensel et al., 1994). An SPKM tool supports the user in these processes. Each individual uses his own SPKM tool as a personal knowledge repository; he benefits personally from this system by having better retrieval of his knowledge. His personal SPKM
tool is connected to other applications and in a loose peer-to-peer fashion to other SPKM tools. This network allows individuals to combine their knowledge through sharing and exchanging. If designed correctly, SPKM tools are easy to use and cognitively adequate for modelling and refactoring knowledge; enable information sharing and reuse within the personal knowledge space, with other knowledge workers, and with existing information systems. And they enable structured access to personal and collaborative knowledge through queries, categorisation, and associative browsing.
existing spkm tools and their drawBaCks Currently, not many SPKM tools exist. A brief overview is presented in this section. IMemex (Dittrich, 2006) calls itself a “A Platform for Personal Dataspace Management” and is centred around a data model (IDM) (Dittrich & Vaz Salles, 2006) for the semantic desktop. IDM’s core goal is to cross the boundaries between files and resources in files. All items, be it folders, files, sections, or paragraphs are mapped into a single model. IDM emphasises performance, expressivity, lazy data sets, and data streams. There is no publically available end-user tool, but first prototypes focusing on search will be available soon. However, authoring of structured data seems not to be the scope of iMemex. Another existing SPKM system is Artificial Memory (Ludwig, O’Sullivan, & Zhou, 2004), which uses a tree-like structure in a Web interface to interact with the user. It represents semantics with icons and allows the user to add new statements. However, unlike a semantic wiki, the user does not have the freedom to not structure his writings. The European project NEPOMUK aims to bring forward the state-of-the-art by developing a social semantic desktop. Within NEPOMUK, a
Personal Knowledge Management with Semantic Technologies
data model for structuring knowledge in explicit yet vague relations is developed as Conceptual Data Structures (CDS) (Völkel & Haller, 2006). NEPOMUK builds on Gnowsis (Sauermann, 2005), which included a semantic wiki from the start to allow a user to make arbitrary statements. In Gnowsis, a central ontology could be browsed and edited in parallel, using the same concepts as those of the semantic wiki. Haystack (Quan, Huynh, & Karger, 2003) is another semantic desktop which emphasizes browsing through and interacting with a heterogeneous collection of RDF resources. However, Haystack does not foresee creating completely unstructured items first, and thus places the burden on the user to formalise her knowledge in one big step. Summary: Although all these tools focus well on the individual (Req. 2, Figure 2) and offer plenty structuring abilities (Req. 3, 4, and 5), they are neither simple to use (Req. 7) nor have they acceptable costs for externalisation (Req. 1).
Semantic wikis enhance classical wikis with the ability to author and use formal semantics: in the same wiki style of free text editing, semantic statements can be added. They can describe the page or parts thereof semantically. A semantic wiki offers a uniform way to work with all levels for formality
(text, structured text, and formal statements). As shown in Figure 4, they allow users to structure and annotate their data but they do not force them to do so. Using enhanced wiki syntax (plain-text with few mark-up commands and few semantic annotation commands) has several benefits: (a) most users are used to text typing and avoid familiarising with yet another user interface; (b) existing skills for text manipulation (e.g., copy and paste of text blocks) are leveraged to edit a document structure; (c) users refine interactively the input until the result matches the intended structure; (d) wikis allow soft transitions between knowledge layers including free-text, therefore no knowledge of any syntax is required to start authoring; (e) wiki syntax has little layout options, forcing the user to focus on the structure and the content; (f) text is in general a faster method of entering semistructured information than graphical approaches. Several semantic wikis exist today. A fullday workshop on semantic wikis was held in 2006 (Völkel & Schaffert, 2006). By using the authoring capabilities of semantic wikis for personal knowledge management—ignoring wiki community aspects—we get a personal semantic wiki (PSW). One of the systems of particular interest is the system SemperWiki (Oren, Völkel, Breslin, & Decker, 2006), which has been designed for personal use and allows the user to integrate simple wiki texts with formal semantic annotations. SemperWiki can be used
Figure 4. Semantic wikis handle a continuous spectrum of knowledge types
Figure 5. Semantic Wikis can author in different paradigms simultaneously
personal semantiC wikis (PSW)
Personal Knowledge Management with Semantic Technologies
as a traditional personal wiki for note-taking, but can also be augmented with simple semantic annotations. These annotations can be shared with others (using RDF, the standard Semantic Web language) but more importantly, enable improved navigation to related items and intelligent queries. Arbitrary annotations can be made and the tool can be customised for usage in a certain domain that use specific terms and ontologies. Such domain ontologies can contain background knowledge (e.g., in the biology domain possibly a taxonomy of biological species and their relations) that can be used in conjunction with the manually entered wiki annotations. SemperWiki integrates with the Gnome (Linux) desktop: it is available across the whole desktop with a single keypress, it automatically saves all changes and updates all navigation links instantly. PSWs allow users to explicitly indicate the semantics of information items and their relations to other information objects. Linking to desktop objects is often still limited or difficult to use. Semantic relations between information objects allow for contextual navigation even between pages that have not explicitly been related to each other but that can be related based on their meaning, such as two notes about the same project. The flexibility and freedom of wikis is maintained: users can annotate notes with their own terms and can later add background knowledge that relates their terms to those used by others in their working environments, enabling those others to reuse personal annotations without requiring a-priori agreement on terms or classifications. However, even semantic wikis do not fully exploit the opportunities of supporting the user. They have currently a severe lack of refactoring tools, a feature found in most advanced IDEs today, which allows renaming or moving items while maintaining all references. Second, semantic wikis do not exploit the structural parts of a page and hence cannot return, for example, short sections relevant to a query but instead return only full documents.
Scenario: Writing an Article using a psw Writing is a central activity for all kinds of knowledge workers. They have to compile reports or write articles for scientific journals. Writing an article includes reading related work—and often also taking personal notes on it. An outline or other kind of high-level structure is usually created. This structure is then refined to the argument-level and fleshed out into a linear text. Next, the text is partially rewritten and references to figures, other sections and literature are added. Eventually the text is typeset and thus the final layout is created. First, the related work can be managed in a PSW. Different from standard reference management tools, a PSW allows annotating and relating references. Second, personal notes on the topic at hand can be managed, structured, refined, and related in the same environment. The benefit of using a PSW is the unified management of heterogeneous artefacts in one environment with one language. Here, language refers to the names used for relation and entity types. A consistently used vocabulary with clear semantics—even if only known to the user in the first place—is of great value in information processing, for example, for posting queries. Such queries can then return a heterogeneous item collection. A second benefit is that a PSW allows users to externalise the semantics of relation and entity types. Once a relation has, for example, been defined as transitive or symmetric, further relations can be computed by inference, leading to better search results. The usual top-down refinement process in article writing is well supported by PSWs: As entities are supposed to be fine-grained and referenceable, items can be re-used. An outline evolving into a draft document can thus be represented by a hierarchy of interlinked items. Smaller items allow for better re-use in other contexts, and semantic annotations help to find the items
Personal Knowledge Management with Semantic Technologies
needed. In collaborative work, multiple users are able to work together explicitly on argument and text structures, something rarely possible with classic tools, that is, only a few dedicated argumentation management tools exist. Another possibility for closely collaborating parties is the direct exchange of model parts from one PSW to another, without the need to create a document at all. The other user can than import and link the other’s knowledge model. A more detailed description how and why a cultural shift from a document-centred to a model-centred society could happen is explained in Völkel (2007).
Evaluating Personal Semantic Wikis The main advantage of PSWs compared to other PKM and SPKM approaches is the use of stepwise, gradual formalisation leading to acceptable costs (Req. 1) both for externalisation and search. PSWs offer the same support for classification and links (Reqs. 3 and 4). Until PSW are integrated with semantic desktops, their ability to track context is still limited (Req. 5). PSWs are simple to use (Req. 7), but have no clear way of working together with paper (Req. 6). As the resulting knowledge base is partially structured, an export to and import from existing formats is partially possible (Req. 8).
ConClusion In this chapter we have introduced the concept of personal knowledge management enhanced with semantic technologies (SPKM). We presented results from an exhaustive literature study on requirements for information management. Then we analysed existing approaches for PKM and evaluated them with respect to the requirements. We found existing tools lead to a high degree of information fragmentation: structures made explicit in one tool become implicit again in the
next tool. There are currently no tools allowing the user to use the different editing paradigms (wiki, document, mind map) at wish—on the same data. Existing PIM objects (task, address, appointment) and desktop resources (files, folders) can currently not be annotated and linked.
Outlook A semantic wiki by itself does not address the requirements: detection of user context and importance of ordinary paper, which are open research issues that are actively worked on in for example ubiquitous computing and in electronic paper. Both are likely to minimise the gap from real to digital world. Advances in scanner technology, optical character recognition (OCR) and natural language processing (NLP) are also likely to integrate paper tighter into the digital world. For privacy and cultural adoption, it seems, the only way is to educate people in the same manner as we teach them reading, writing, and calculating. On future curriculae we will probably also find the subjects semantic modelling and data privacy.
Future Research Trends An SPKM tool should analyse and cluster the information to find related items. All information should be stored in a content repository that can apply rules with background knowledge, and one should be supported in reusing existing terminology. SPKM systems should be connected to each other forming a network of knowledge; this network should allow sharing knowledge with others. The interface of the SPKM system should be able to be personalised to each user and adapt to his preferences. Importing and exporting with existing and future nonsemantic tools is an issue. Also the integration between different semantic applications—although easier—is still a research issue. Another concern is privacy. If people continue to
Personal Knowledge Management with Semantic Technologies
publish a lot of their semantic data, they will be surprised to learn how easy such information can be aggregated later on. Nontechnical issues such as semantic data handling as a cultural technique, the gap from paper to the digital world, and simplicity in use are still open. A critical success factor of SPKM solutions will be the soft introduction of formalization: A user must, for example, always have the option not to formalize at all. A gradual, step-wise formalization of the existing knowledge structures should let the user decide how much effort (K E) he is willing to spend. At any point in time, more formalization effort has to be rewarded with better querying and browsing capabilities (lower K R). The Achilles heel of semantic tools will be the authoring part. Only if the end-user has an easy-to-use environment to create semantic structures on the fly and explicitly, semantic can technologies can improve searching and browsing. Of course, this approach should be accompanied by automatic generation of semantic data from existing content.
aCknowledgment Parts of this work have been funded by the European Commission 6th Framework Programme in the context of the Knowledge Web Network of Excellence Project, FP6-507482, and the EU IST NEPOMUK, the Social Semantic Desktop, FP6-027705. Parts of this material are based upon works supported by the Science Foundation Ireland under Grants No. SFI/02/CE1/I131 and SFI/04/BR/CS0694 and parts of this work have been funded by Salzburg Research, Austria.
referenCes Adler, A., Gujar, A., Harrison, B. L, O’Hara, K., & Sellen, A. (1998). A diary study of work-related
0
reading: Design implications for digital reading devices. In CHI (pp. 241-248). Barreau, D., & Nardi, B. A. (1995). Finding and reminding: File organization from the desktop. SIGCHI Bulletin, 27(3), 39-43. Bellotti, V., Dalal, B., Good, N., Flynn, P., Bobrow, D. G., & Ducheneaut, N. (2004). What a to-do: Studies of task management towards the design of a personal task list manager. In CHI (pp. 735-742). Blandford, A., & Green, T. R. G. (2001). Group and individual time management tools: What you get is not what you need. Personal and Ubiquitous Computing, 5(4), 213-230. Bondarenko, O., & Janssen, R. (2005). Documents at hand: Learning from paper to improve digital technologies. In CHI (pp. 121-130). Braganza, A., & Mollenkramer, G. J. (2002). Anatomy of a failed knowledge management initiative: Lessons from PharmaCorp’s experiences. Knowledge and Process Management, 9(1), 23-33. Campbell, C., & Maglio, P. (2003). Supporting notable information in office work. In CHI (pp. 902-903). Cutrell, E., & Dumais, S. T. (2006). Exploring personal information management. Commun. ACM, 49(1), 50-51. Dai, L., Lutters, W. G., & Bower, C. (2005). Why use memo for all? Restructuring mobile applications to support informal note taking. In CHI (pp. 1320-1323). Dittrich, J.-P. (2006). iMeMex: A platform for personal dataspace management. In SIGIR PIM. Dittrich, J.-P., & Vaz Salles, M. A. (2006). iDM: A unified and versatile data model for personal dataspace management. In VLDB, Seoul, Korea (pp. 367-378).
Personal Knowledge Management with Semantic Technologies
Dumais, S., Cutrell, E., Cadiz, J. J., Jancke, G., Sarin, R., & Robbins, D. C. (2003). Stuff I’ve seen: A system for personal information retrieval and re-use. In SIGIR (pp. 72-79).
Ludwig, L., O’Sullivan, D., & Zhou, X. (2004). Artificial memory prototype for personal semantic subdocument knowledge management (PS-KM). ISWC demo.
Esselborn-Krumbiegel, H. (2002). Von der Idee zum Text. Eine Anleitung zum wissenschaftlichen Schreiben., Utb.
Nonaka, I. (1994, February). A dynamic theory of organizational knowledge creation. Organization Science, 5(1), 14-37.
Fensel, D. et al. (1994). Integrating semiformal and formal methods in knowledge-based systems development. In Proceedings of the Japanese Knowledge Acquisition Workshop (JKAW-94), Hitachi, Japan (pp. 73-89).
Nonaka, I., & Takeuchi, H. (1995). The knowledge-creating company. New York: Oxford University Press.
Haller, H. (2002). Mappingverfahren zur Wissensorganisation. Diploma thesis at Freie Universität Berlin. Hearst, M. A. (2006). Clustering versus faceted categories for information exploration. Communications of the ACM, 46(4). Jones, S. R., & Thomas, P. J. (1997). Empirical assessment of individuals’ personal information management systems. Beh. & Inf. Techn., 16(3), 158-160. Kando, N. (1997). Text-level structure of research papers: Implications for text-based information processing systems. In BCS-IRSG Annual Colloquium on IR Research, Workshops in Computing, BCS.
O’Hara, K., & Sellen, A. (1997). A comparison of reading paper and online documents. In CHI (pp. 335-342). Oren, E. (2005, November). SemperWiki: A semantic personal wiki. In Proceedings of the ISWC Workshop on the Semantic Desktop. Oren, E. (2006, November). An overview of information management and knowledge work studies: Lessons for the semantic desktop. In Proceedings of the ISWC Workshop on the Semantic Desktop. Oren, E., Völkel, M., Breslin, J. G., & Decker, S. (2006, September). Semantic wikis for personal knowledge management. In Proceedings of the International Conference on Database and Expert Systems Applications (DEXA).
Kidd, A. (1994). The marks are on the knowledge worker. In CHI (pp. 186-191).
Polanyi, M. (1958). Personal knowledge: Towards a post-critical philosophy. London: Routledge & Kegan Paul Ltd.
Kwaśnik, B. H. (1983). How a personal document’s intended use or purpose affects its classification in an office. In SIGIR (pp. 207-210).
Pivk, A., Cimiano, P., & Sure, Y. (2005, October). From tables to frames. Journal of Web Semantics, 3(2), 132-146.
Lansdale, M. (1988). The psychology of personal information management. Applied Ergonomics, 19(1), 55-66.
Quan, D., Huynh, D., & Karger, D. R. (2003). Haystack: A platform for authoring end user Semantic Web applications. In International Semantic Web Conference (pp. 738-753).
Leuf, B., & Cunningham, W. (2001). The wiki way: Collaboration and sharing on the Internet. Addison-Wesley.
Randall, D. W., Bowker, G., & Leigh Star, S. (2001). Sorting things out: Classification and
Personal Knowledge Management with Semantic Technologies
its consequences - review. Computer Supported Cooperative Work, 10(1), 147-153. Ranganathan, S. R. (1962). Elements of library classification. Bombay: Asia Publishing House. Sauermann, L. (2005). The gnowsis semantic desktop for information integration. In Wissensmanagement (pp. 39-42). Schraefel, M. C., Wilson, M., Russell, A., & Smith, D. A. (2006). M-space: Improving information access to multimedia domains with multimodal exploratory search. Communications of the ACM, 49(4), 47-49. Sellen, A. J., & Harper, R. H. R. (2003). The myth of the paperless office. Cambridge, MA: MIT Press. Teevan, J., Alvarado, C., Ackerman, M. S., & Karger, D. R. (2004). The perfect search engine is not enough: A study of orienteering behavior in directed search. In CHI (pp. 415-422). Völkel, M. (2007). From documents to knowledge models. In Proceedings of ProKW workshop, Konferenz Professionelles Wissensmanagement, Potsdam, Germany. Völkel, M., & Haller, H. (2006a). Conceptual data structures (CDS) - towards an ontology for semi-formal articulation of personal knowledge. In Proceedings of the 14th International Conference on Conceptual Structure, Aalborg University – Denmark. Völkel, M., & Schaffert, S. (Eds.). (2006). Proceedings of the First Workshop on Semantic Wikis - From Wiki to Semantics, ESWC. Wagner, C., & Bolloju, N. (2005, April-June). Knowledge management with conversational technologies: Discussion forums, weblogs, and wikis. Journal of Database Management, 16(2), i-viii.
Wenger, E., McDermott, R., & Snyder, W. M. (2002, March). Cultivating communities of practice. Harvard Business School Press. Whittaker, S., Bellotti, V., & Gwizdka, J. (2006). E-mail in personal information management. Communications of the ACM, 49(1), 68-73. Yee, K.-P., Swearingen, K., Li, K., & Hearst, M. (2003). Faceted metadata for image search and browsing. In CHI.
additional reading Bardini, T. (2000). Bootstrapping: Douglas Engelbart, coevolution, and the origins of personal computing (Writing Science). Stanford University Press. Davenport, T. H. (2005). Thinking for a living: How to get better performances and results from knowledge workers. Harvard Business School Press. Engelbart, D. (1963). A conceptual framework for the augmentation of mans intellect (Tech. Rep.). London, Washington DC: Spartan Books (pp. 1-29). Friedewald, M. (2000). Der Computer als Werkzeug und Medium. Die geistigen und technischen Wurzeln des Personalcomputers (Taschenbuch). Goodman, D. (1988). The complete hypercard handbook. Random House Information Group. Lethbridge, T. C. (1994). Practical techniques for organizing and measuring knowledge. Ph.D. thesis, University of Ottawa. Rheingold, H. (2000). Tools for thought: The history and future of mind-expanding technology. The MIT Press. Sowa, J. F. (1999). Knowledge representation: Logical, philosophical, and computational foundations. Course Technology.
Personal Knowledge Management with Semantic Technologies
endnote 1
The literature survey started in November 2006 from recent issues of relevant conferences (ESWC, ISWC, CHI, and SIGIR conferences and the CACM journal) and followed both backward and forward citations.
Chapter X
DeepaMehta:
Another Computer is Possible Jörg Richter DeepaMehta Company, Germany Jurij Poelchau fx-Institute, Germany
introduCtion machine dreams A crucial experience during my time at university—computer science (with focus on AI) and linguistics—was the documentary “Maschinenträume” (1988) by Peter Krieg. It features the long-term AI project “Cyc,” in which Doug Lenat and his team try to represent common sense knowledge in a computer. When Cyc started, in 1984, it was already known that many AI projects failed due to the machine’s lack of common sense knowledge. Common sense knowledge includes,
for example, that two things cannot be in the same place at the same time, or that people die, or what happens at a children’s birthday party. During the night, while the researchers are sleeping, Cyc tries to create new knowledge from its programmed facts and rules. One morning the researchers were surprised by one of Cyc’s new findings: “Most people are famous.” Well, this was simply a result of the researchers having entered, besides themselves, only celebrities like, for example, Einstein, Gandhi, and the U.S. presidents. The machine-dreaming researchers, however, were in no way despondent about this obviously wrong finding, because they figured they would only
Copyright © 2008, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
DeepaMehta
have to enter the rest of the population, too. The underlying principle behind this thought is that it is possible to model the whole world in the form of ontologies. The meaning of the world can be captured in its entirety in the computer. From that moment the computer can know everything that humans know and can produce unlimited new insights. At the end of the film Peter Krieg nevertheless asks: “If one day the knowledge of the whole world is represented in a machine, what can humans do with it, the machine having never seen the world.”
the potential of ontologies In order to create computer applications that suit the human way of thinking and working, one needs to think about ontologies. There are ontologies, for example, for molecular biologists, for news editors, for tourist agents, or for connoisseurs of wine. By developing an ontology people agree on the meaning (semantics) of certain computer codes. Every community of interest is free to create their own ontology or to cowork with likeminded people on the development of a shared ontology. This development process—the ontogenesis—is at least as important as the resulting ontology itself. An ontology of the entire world will never exist because the meaning of terms depends on their usage context. A wine merchant probably has different priorities than a wine connoisseur which will be reflected in their ontologies. When developing an ontology, local or global communities of interest focus on that parts of the reality that are relevant to their intended usage context. The authors see the prior potential of ontologies not in creating an one-to-one representation of reality, in order to enable automatic reasoning, but in “learn[ing] to think together by building shared structures of meaning” (Murray, 2003, p. 11). That is not in automation, but in collaboration. We can accept that invitation not only to think about application domains and usage contexts
but also to rethink the underlying concepts of the computer itself, especially the human-computerinterface. It is interesting to bring to mind that ontologies are firmly molded into every software system—long before the Semantic Web effort. These ontologies are made up of the concepts and their relations defined by the software architect, and according to which the user is supposed to think when using the software. So, the concepts of, for example, “presentation,” “slide,” and “masterslide” and their relations are as firmly molded into the software “Powerpoint” as the concepts “application,” “window,” “file,” and “folder” in the software “user interface.” It would be significantly easier for the computer user if the user could work semantically not only in a single application but if the entire computer were designed as a semantic work environment. In such an environment, the user would no longer work in applications, or store files in folders, but would be confronted with the terms of his/her way of thinking and working directly. At the lowest level such an environment could provide the concepts “more or less structured information unit,” “relation between information units,” “view of a information context,” “shared workspace,” and “private sphere.” At the next higher level more specific concepts of yet general usage like “contact info,” “appointment,” “task,” and “project” could be provided. And at the highest level the user would find the concepts of its individual work and leisure domains, for example, a molecular biologist and movie fan would work with the concepts “chromosome,” “gene,” “protein,” as well as “movie,” “actor,” and “cinema.”
The Trouble with Computers and their Solutions When learning how to use a computer nowadays, one understands quickly that for every purpose one needs a specific application. To write a text, one uses a word processor. E-mails are dealt with using an e-mail application. To surf the Internet
DeepaMehta
one needs a Web browser and one’s contact information is stored in the address book. Launching an application causes a window to open, showing one the application controls as well as the actual content (texts, e-mails, Web pages, contact details). When writing a text, one needs to save it into a file. This file is located in a certain folder on the hard disc. When one wants to access one’s text later on, one has to use another application: a file browser to locate and open the respective file. Within the first weeks of learning every computer user experiences the loss of his/her text (image, etc.)—either because the user forgot to save it or because the user cannot find it anymore. Working with applications, files, and folders and the importance of saving is surely not difficult to learn, and even may—as soon as one has internalized the logic of the computer—seem reasonable. However, if we turn away from the machine logic to human work situations, it becomes apparent how unnatural and inefficient this mode of operation is. A typical work situation involves a number of heterogeneous content objects. Take, for example, the production of this book, “SWE.” There are about 20 chapters addressing different topics. Each chapter is written collaboratively by several authors. For each author there are several contact details (e-mail address, homepage, telephone number). Each chapter refers to a number of further information resources (projects, Web sites, other articles). During the review phase, authors review each others’ chapters leading to further chapter revisions. Eventually the editors assemble the accepted chapters into the final book ready for the print shop. By means of this work scenario, two fundamental flaws of the computer and the resulting problems can be made clear:
Missing Relations The meaningful relations between information resources are not represented in the computer.
Thus, they neither can be displayed on-screen nor be exploited for navigation. There is no relation between, for example, the author of a Word document and its entry in the address book application. The user has to switch to the address book and search for the contact details manually. Even within a single application, relations are not easy to represent: if an article, as well as its reviews, are created with, for example, Microsoft Word, it is not possible to represent the relations between these files within Word, but only indirectly in the file system structure, if at all. Because the relations are not represented in the computer, they can not be shared with other users. This makes collaboration inefficient, because every coworker has to reconstruct the relations individually. To represent the relations between, for example, the articles and their reviews one could store every article in its own folder and its reviews in respective sub folders. If a review is sent to a coworker as a mail attachment, the relations to the main article gets lost and the receiver has to reconstruct it in the receiver’s own way. This additional effort increases with the number of coworkers, thus a lack of synchronization and various misunderstandings between the coworkers are programmed. The problem of missing relations can be solved by releasing the contents (texts, e-mails, Web pages, contact details) from their applications and storing them in a corporate memory using a neutral data format. Within the corporate memory, arbitrary content objects can be set into relation, and external resources can be integrated by storing reference objects in the corporate memory. The problem of inefficient collaboration can be solved by letting all coworkers operate on a central (server side) corporate memory instead of their local hard discs. For both problems, the suggested solutions are already in use through specific applications (e.g., Document Management, Content Management, Personal Information Management, Workflow Management, Groupware, and Wikis), but to the
DeepaMehta
knowledge of the authors, there is no computer platform that operates system-wide according to this paradigm.
Missing Work Context The greatest problem which makes using a computer so cumbersome is that the user’s work context is not represented on-screen. This applies especially to the knowledge worker who deals with a number of applications and windows simultaneously. In the work context of “SWE Book,” for example, a number of heterogeneous content objects (texts, e-mails, Web pages, contact details) are involved. A book author will probably use the concept of “folders” to set up his computer as follows: on the hard disc there is a folder “SWE
Book” to hold the article and further assets. In the Web browser there is a folder “SWE Book” to hold the bookmarks of the project’s Web site and other Web sites. In the e-mail application there is a folder “SWE Book” to hold the mails of the book editors and other authors. And in the address book application there is a folder “SWE Book” to hold the contact details of the project’s members. Conclusion: in the user’s mind there is one project, “SWE Book,” whereas in the computer the project is chopped into pieces and fragmented to at least four different work environments. The user has to switch between several applications on a regular basis. Every switch changes the display as well the usage rules abruptly. What is displayed in one moment has vanished (resp. is obscured) in the next, the usage rules that are ap-
Figure 1. Current window-based user interface with four open applications: Web browser, file browser, e-mail client, and address book.
Problem 1: the meaningful relations are not displayed. Information belonging to one project (here: “SWE Book”) are fragmented to several work environments. Problem 2: the user’s work context is not displayed. The user must switch between applications frequently and has to cope with permanent context changes
DeepaMehta
plicable in one moment are not so in the next. The user can, of course, recover his/her “SWE Book” folder in each application, but probably along with another 100 folders which are not related to the current work context in any way. If the content objects belonging to the current work situation—and only these—were visible together on-screen, the cognitive load of the user would be reduced significantly. This would free the user’s mind for concentration on work instead of on the workings of the machine. Within the scope of the current user interface paradigm—every application opens another window and the application’s content objects are bound to that window—the problem of the missing work context can not be solved. The kind of navigation that results from that paradigm is called here “GoTo Navigation.” To look up, for example, an e-mail address while being in a Web browser the user must go-to that e-mail address (that is switching to the address book application) and cope with a complete context switch. This situation can not be abolished by the development of ever further applications because this only leads to a further fragmented user experience. The problem of the missing work context can only be solved by establishing a new user interface paradigm in combination with a new application model. This new interface paradigm can realize a kind of navigation that is called here “Bring-To-Me Navigation.” To look up, for example, an e-mail address while reading a Web page, the e-mail address is brought to the user, that is, it is searched for and displayed within the current work context. The on-screen work context remains stable. Heterogeneous content objects (texts, e-mails, Web pages, contact details) and their meaningful relations (problem 1) are displayed within the same window. The aim of Bring-To-Me Navigation is to let the interface itself disappear, and let the display become a “visual cache” (Canfield Smith, Irby, Kimball, Verplank, & Harslem, 1982) of the user’s state of mind.
In Richter, Völkel, and Haller (2005), the terms “Stable Views” and “Constructive Browsing” are used to describe this new interface paradigm, but here the term “Bring-To-Me Navigation” is used to express that information is brought to a single window and to contrast it to the traditional Go-To Navigation. In order for the content objects from different applications to share the same display context, the application logic must be separated from the display. The application as such will no longer be visible to the user, but only the content objects. Because there is no application-specific user interface anymore, the content objects must provide the application-specific operations themselves, for example, an e-mail object must provide a “send” operation to the user. This requires a new application model. The new application model will be realized as an application framework to allow application developers to bind operations to content objects and to interfere with the shared display context. To our knowledge there is no computer platform that offers stable on-screen work contexts system-wide.
the vision of an integrated work environment The vision of the DeepaMehta platform is to provide the knowledge worker with an integrated environment that supports his/her work, thought, and collaboration process. The DeepaMehta platform replaces the traditional computer desktop by a semantic desktop that “push[es] the user interface farther out from the computer itself, deeper into the user’s work environment” (Grudin, 1990). DeepaMehta envisions: •
Removing machine concepts (applications, document formats, and so forth) from the user interface and thus from the user’s mind. Confronting the user only with the concepts
DeepaMehta
•
•
•
of daily work and thought. Allowing the user to fully control the display in order to represent work context on-screen. Proving that “a well-designed computer system can actually improve the quality of your thinking” (Canfield Smith et al., 1982) Breaking down the “application prison” (Nelson, 2001) and freeing the data from their applications in order to let the user navigate associatively across applicationborders. Allowing the user to re-use information objects in different work contexts. Designing a user interface that allows the user to apply the natural faculties like a sense of orientation: “I’m located at a certain place within a stable environment.” Designing a user interface that accommodates the individual learning process. Designing a software architecture which allows software developers to contribute domain-specific application logic without confronting the user with applications.
•
•
•
Supporting collaboration by allowing workgroups to operate on a shared information repository and to build shared structures of meaning. At the same time, providing the user with protected spaces to encourage creativity. Designing a work environment that supports the whole process, from (a) content creation, to (b) enrich content by structure, and (c) enrich structured content by application logic. Designing a work environment that allows constant changes at every stage. Delivering computers that boot directly into DeepaMehta as the standard user interface and work environment.
The developers of DeepaMehta strive to identify generic operations that are common to all applications, for example, editing, searching, displaying, navigating, and to build them right into the platform. Domain-specific operations may be implemented in the scope of the DeepaMehta
Figure 2. Old world—New world
The traditional computer user is bothered with operating systems, and applications which are built around document formats and network protocols (left side). In contrast, the DeepaMehta user is confronted only with content, and performs operations on the content directly—all on a semantic foundation (right side)
DeepaMehta
application framework. DeepaMehta applications are running at the server side and are not in the sight of the user.
•
the deepamehta platform The DeepaMehta software platform for collaboration and knowledge management is a comprehensive integrative concept that removes existing barriers that make current computer usage so cumbersome. DeepaMehta combines concepts and research findings in the fields of software engineering, information visualization, human computer interaction, Semantic Web, and creativity techniques in an innovative manner. DeepaMehta has the potential to be a great integrator: •
•
•
•
0
Mind Maps/Concept Maps: The DeepaMehta semantic desktop combines the cognitive virtues of mind maps with the computational virtues of concept maps resp. semantic networks. Visualization/Workspace: In DeepaMehta there is no separation between the graphic visualization of content structures and the actual work environment. All kinds of content is created and edited in-place. There is no separation between file-level and application-level. Brain Storming/Structuring/Processing: DeepaMehta supports the whole information handling process: from creating information in a brainstorming-mode, to structure information and building models, and to processing information by implemented logic—all is performed in one environment. File Level/Application Level: DeepaMehta steps away from the file-application-dichotomy and establishes a new paradigm of content and operations. Typed content objects provide the manipulative operations
•
themselves. Generic operations are provided by the DeepaMehta platform. Network/Local Machine: DeepaMehta removes the barrier between the local desktop machine and the network by establishing a uniform user interface for personal content and shared content. Working with local content and remote content results in no different user experience. Topic Maps/RDF: The DeepaMehta data model is inspired by ISO 13250 Topic Maps but has extensions to incorporate RDF-like features. DeepaMehta has the potential to marry the ISO Topic Maps standard and the W3C RDF standard.
topic maps frontend The DeepaMehta desktop is split into two areas. At the left hand side a topic map consisting of typed topics and typed associations is displayed. On the right hand side, detail information about the currently selected topic, association, or the topic map itself, is shown. This panel is called the Property Panel. If, for example, an e-mail topic is selected, the e-mail (with its “From,” “To,” “Subject,” and “Text” properties) is shown in the property panel. If a Web page topic is selected, the page (with its “URL,” “Title,” and “Content” properties) is rendered in the property panel. The user performs basic text editing and image-manipulation operations directly in the property panel, without the use of external applications. To perform operations on a topic, an association, or the topic map itself, the user utilizes context menus. Generic operations such as “Hide,” “Retype,” “Delete,” or “What’s Related?” and “Google Search” are provided by every topic. Depending on their type, topics may provide more specific operations, for example, an e-mail topic provides a “Send” operation, and a Web page topic provides a “Reload” operation. Topics and associations can be created manually or
DeepaMehta
Figure 3. The “DeepaMehta” networked semantic desktop
The left side displays information objects of different kinds and origins as well as their meaningful relations as a topic map that represents the current work context of the user. The right side displays detail information about the selected topic, for example, an e-mail or a Web page. The information objects are edited and manipulated in-place, for example, e-mails are written and send straight from the desktop
programatically. Topics and associations can result from a variety of sources such as mailservers, Web servers, databases, and Web-services. Associations can be created between any two topics, regardless of their origin. Topic maps are not like documents containing contents, but always personal views to contents existing elsewhere. All topics and associations are stored in a server-side repository, called the Corporate Memory. The corporate memory is accessible to various users and workgroups simultaneously, exposed to an access control mechanism of course. A topic map is an individual view to extracts of the corporate memory that are relevant in a particular working context. It is up to the user to decide which topics and associations to retrieve, and where to show them.
Topic maps are of unlimited size and are moved by mouse dragging. Topic maps that serve as common views within workgroups are published into shared workspaces. A query to the corporate memory is visualized graphically and the result set is displayed as a topic of the form of a ton. In order to avoid cognitive overload, DeepaMehta does not reveal a search result at once if it comprises more than seven topics (Miller, 1956). If the result does not comprise more than 150 entries, single topics may be revealed via a popup menu. Large result sets may be reduced by applying a narrower filter. A topic query may involve the topic name, topic type, topic properties, and associations the topic is involved in. The result may be sorted. Result sets in DeepaMehta can be regarded as “smart
DeepaMehta
Figure 4. The context menu of the person topic “Douglas C. Engelbart”
By the means of the “What’s Related?” command associated topics are retrieved from the corporate memory and displayed in the current topic map. Here, the submenu reveals Douglas C. Engelbart is associated with 2 other persons, 1 computer, 2 articles and so on.
Figure 5. In DeepaMehta large amounts of data are displayed as a ton
DeepaMehta desktop, exactly as it was left in the previous session. The DeepaMehta Platform is based on ISO 13250 Topic Maps. Topic maps consist of topics and associations, and both are typed. Types are Topics too. The user can define new types by deriving them from existing types, create additional properties, and defining relations to other types. New types can be used immediately, also together in shared workspaces. Every topic can be retyped at any time without losing content. All this provides the basis for supporting the dynamic collaborative process of building new ontologies.
System Architecture Features of the DeepaMehta software architecture: • • • • • •
A ton represents a query to the corporate memory and the result set at the same time. In this example an unspecific person search results in 267 topics — too much to reveal at once. Applying a filter “kay” yields to a result set small enough to be revealed immediately.
• • • •
folders,” that is, the user can retrigger the query that underlies a ton by double-clicking it. A ton may represent the query, for example. “All e-mails I have received from Jurij in the last 30 days.” The user interface is fully personalized. After logging in the user finds himself directly on the
•
Java-based application server multi-layer architecture Supported Semantic Web standards: ISO 13250 Topic Maps, RDF DB-neutral storage layer, currently MySQL and HSQL (pure Java DB) Variable frontends: Topic Maps GUI (Thin Client), Web browser, PDA, mobile phone Object-oriented framework for application developers SOA (Service Oriented Architecture) Access to external Web services via SOAP Access to external datasources: SQL, LDAP XSLT-based publishing engine for dynamic SVG, PDF and XHTML generation Integrated mail and Web support: SMTP, POP3, IMAP, HTTP
The DeepaMehta system architecture comprises all the layers of an IT system: the storage layer, the application layer, and the presentation layer. DeepaMehta is a distributed architecture, so that every layer can reside on a different machine.
DeepaMehta
Figure 6. DeepaMehta is a multilayered distributed software architecture
The heart of the DeepaMehta software architecture consists of an application server. DeepaMehta applications are developed in the scope of the DeepaMehta application framework and run at server-side. Applications can access a variety of data sources and can be served to a variety of frontends
The heart of the DeepaMehta software architecture consists of an application server. DeepaMehta defines a unique application model and provides a framework for application developers. A DeepaMehta application is actually a collection of topic types and association types that may be assigned to a workspace. Every type can be attached to a Java class that implements the behavior of the instances of that type. The topic type “Postal Address,” for example, may be attached to an implementation that fetches a map from Google Maps for a particular address. New applications can be aggregated from existing types. Thus every application that deals with postal addresses will benefit from the Google Maps behavior. Types can be assigned to shared workspaces. The user “deploys” an application just by joining a shared workspace. Once a user joins a shared workspace, the user gets access to the assigned types, and thus to their functionality.
data model The DeepaMehta data model is inspired by ISO 13250 Topic Maps. On the one hand the Topic Maps standard is not fully implemented; on the other hand, there are extensions to incorporate RDF/RDFS-like features. There are a lot of proposals for the integration of the ISO Topic Maps standard and the W3C RDF/RDFS standard (Pepper, Vitali, Garshol, Gessa, & Presutti, 2006) but DeepaMehta chooses its own ad-hoc approach because when the project started, in early 2000, these proposals did not yet exist. Furthermore in DeepaMehta there are higher-level concepts like Query, Datasource, Workspace, and User defined.
Topic Maps Concepts that are not realized resp. modified in DeepaMehta: n-ary Associations: For the sake
DeepaMehta
of simplicity, DeepaMehta supports only binary associations. This is not a serious lack because an n-ary association can be emulated by n binary associations. •
•
•
•
•
Association Role, Association Role Type: because DeepaMehta supports binary associations only, and associations are explicitly directed from node 1 to node 2, there is no need to realize the concepts of Association Role and Association Role Type. The meaning of the involved nodes is represented in the direction of the association. Occurrence, Occurrence Role, Occurrence Role Type: because DeepaMehta pursues an integrated GUI approach, occurrences are not realized explicitly. External resources are represented as topics; for example, a file is represented as a topic of type Document, and a Web page is represented as a topic of type Web page. Facet: because occurrences are represented as topics and because DeepaMehta provides the concept of properties, there is no need to realize the concept of facets. Scope: not yet realized. To a great extend ambiguity may be diminished by typing topics. In DeepaMehta there would be, for example, two topics “Tosca,” one of type Opera the other of Type Character. Furthermore DeepaMehta provides the concepts of Workspaces and Users. To Workspaces, a number of types are assigned. Users are members of workspaces and have access to the respective types. Topic Maps: In DeepaMehta, topic maps are topics too. Thus, topic maps can act as containers for other topic maps. (This is exploited by the GUI to realize the personal and shared workspaces which are in fact topic maps that serve as storage spaces for other topic maps.)
DeepaMehta Topic Maps Extensions to Incorporate RDF/RDFS-like Features •
•
Property, Property Value: part of the type system. To a topic type or association type a number of properties can be assigned. For example, the type Person has the properties “Birthday” and “Gender.” Property Values are a enumeration of predefined property values. For example, for the Property “Gender” the values “Male” and “Female” are predefined. Relation: to define a relation between types; part of the type system. Part of the definition is the Cardinality and the Association Type to be used at instance-level. For example, to model “City of birth,” a relation between the types “Person” and “City” may be defined, cardinality would be set to “One” and association type would be set to “City of birth.”
Higher-Level DeepaMehta Concepts •
•
•
Query: a query to the corporate memory and the corresponding result set of topics is a topic itself (and is presented at the GUI as a ton). A query can involve the Topic Name, Topic Type, Property Values (at instance level) and associations a topic is involved in. Datasource: external datasources like SQL databases or LDAP repositories are represented as topics too. A datasource is specified via its connection string (an URL starting with jdbc or ldap, for example) and the assignment of topic types whose instances are created from datasource entities. Workspace: a shared workspace with a number of members (users). A workspace is an exchange place for topic maps. Furthermore there are topic types and association types assigned to a workspace to hold the concepts which are used in it. Also the access
DeepaMehta
•
control mechanism is based on workspace memberships. Workspaces are topics, too. User: a user of the platform. A user is a member of a number of workspaces. The user has access to all the types assigned to the workspaces of which the user is a member, as well as to private types. A user has its private sphere (a topic map itself) to store private topic maps. A user is a topic too (derived from Person).
DeepaMehta applications are not visible to the user as such but only their topic types and associations appearing in the context menus. Types can be assigned to workspaces; the user obtains access to types by joining a workspace. The application’s data is modeled as type definitions and the application’s behavior is realized by attaching a Java class to a type. A type definition comprises a set of properties, a derivation from a basis type, and relations to other types:
the application framework • The DeepaMehta platform defines its own application model and provides an application framework. By means of the DeepaMehta Application Framework software developers create applications running on the DeepaMehta platform. A DeepaMehta application consists of a collection of types: topic types and association types. To create, for example, a calendar application, one could define the topic types “Calendar,” “Event,” “Location,” “Person,” and the association type “Participant.”
•
• Figure 7. By choosing from the list of widgets one can specify how to render a property in the property panel.
A Property models an untyped single-value data field of a topic type or association type. The topic type “Event,” for example, could have the properties “Begin Date” and “Begin Time” and the topic type “Person” could have the properties “First Name,” “Last Name,” and “Gender.” For a property, a list of possible values can be predefined. For the “Gender” property, for example, the values “Male” and “Female” could be defined. By the means of Derivation, a type definition can be build by specialization of an existing type. The derived type inherits all the properties and behavior of the basis type. A Relation models the relation between two topic types. In order to model, for example, the place of birth, one could define a relation between the topic types “Person” and “City.” A relation includes the specifications of the cardinality—one or many—and the association type to be used at instance level.
All the building blocks of the data model—topic types, association types, properties, property values, derivations, relations—are topics and associations themselves. Thus, the data model of a DeepaMehta application can be created directly in DeepaMehta as a topic map. As soon as the data model is defined, the basis functions of the application can be used immediately. To create, for example, an event and its participants, the user creates an Event-topic and connects it via Par-
DeepaMehta
Figure 8. The elements of the data model—topic types, association types, properties, and property values—are topics themselves and are handled as topic maps as well.
Here, the topic types of a calendar application are displayed. The topic types “Calendar,” “Event,” and “Person” derive basis properties from the “Topic” base class and define their own properties. To realize application-specific behavior every type can be attached to a Java class
ticipant-associations with Person-topics. Further basis functions like changing, deleting, or searching for events (e.g., all my upcoming events) and also the collaborative calendar usage is possible immediately, because standard information processing and communication functions are already built right into the DeepaMehta platform. An application consists not only of a data model and generic data manipulation operations but also of domain-specific application logic. The calendar application, for example, could notify the participants of an event in due time via e-mail or instant messaging. This is possible in DeepaMehta because topics and associations are not just information carriers but also provide active behavior. Every type can be attached to a Java class which implements the behavior of the instances of the respective type. The Java class
must be compliant to the DeepaMehta application framework, that is, it must be derived directly or indirectly from a certain base class (“LiveTopic”) and override specific methods (hooks) to let the topic instance react upon certain events. The DeepaMehta application framework is primarily event driven. It defines a number of events to which a topic or an association can react. A topic, for example, can react once: •
•
•
It is clicked: Most of the topics react by displaying their properties in the property panel (right side). It is right-clicked: Most of the topics react by dynamically assembling and displaying a context menu. An “E-mail”-topic, for example, can provide a “Send” command. A command has been chosen from its context menu: The base class provides the
DeepaMehta
Figure 9. This class diagram shows a selection of the LiveTopic subclasses that come with the DeepaMehta platform
The platform’s core features like “User Management & Collaboration” (grey areas) as well as the standard applications like “Personal Information Management” (blue area) are implemented as LiveTopics. The base class “LiveTopic” provides the hooks to be overridden by application-specific topic classes, in order to react on certain events
•
•
standard behavior for handling generic topic commands like “Hide,” “Retype,” “Delete,” “What’s Related?” and “Google Search.” One of its properties has been changed: An “Event”-topic, for example, could notify all the participants once an event is postponed. Furthermore, a topic can check the new property value and possibly reject it, or prohibit a property change a priori. It is associated with another topic: An “Event”-topic, for example, could notify a newly assigned participant. Furthermore, both of the associated topics get the chance to specify a certain association type or to reject the association.
•
•
It is moved within a topic map: This can be useful, for example, if the topic map acts as a time or geo grid. Furthermore a topic can lock itself to prohibit any movement. The topic map in which it is contained has been published in a shared workspace: A “Document”-topic, for example, uploads its assigned file to the server-side file repository.
The former list provides just an overview of the most important events. The DeepaMehta application framework defines about 40 events. The event handler hooks are ordinary Java methods. Within the hooks all Java APIs can be
DeepaMehta
used that are available on the server. Furthermore, the DeepaMehta application framework provides a number of service calls in order to navigate in the corporate memory, for example. All hooks are informed by the framework about the user who triggered the event. Thus the topic can impose access restrictions, for example, by disabling the menu commands for which the current user doesn’t have the required credentials.
the DeepaMehta Unified Process The development process is divided into three stages. Traditionally, at every stage another tool is used. At the stage of brainstorming one creates text or graphic content, for example, by using text editors or dedicated brainstorming tools like MindManager. To be able to process the contents later on by the means of application logic, a model must be built, for example, by creating database tables. Finally, the application logic must be coded by a programmer. At each of the three stages, different persons with different skills are involved and different work environments are used, each with a different user interface. This makes for
Figure 10. Processes (left side) and artifacts (right side) as involved in every IT-project
a slow and cumbersome development process. Content must be migrated from one stage to another, changes in one stage may require changes in the other stages. Communication between the involved persons is difficult because of the different jargons. The DeepaMehta Unified Process enables smooth transitions between all three levels (content, structure, and logic). Content can be created before any structure exists, and unstructured content can later be turned into structured content. No content will be lost, even if the structure changes later. Structured content, as well as unstructured content, and even the structure itself may be subject of later brainstorming sessions. Standard logic for, for example, navigating, searching, editing, and displaying content are built right into the DeepaMehta platform. Structured content may be processed by implementing custom logic. In order to support the communication process between the involved persons collaboration features are built into the platform. To build contents and structure collectively, the DeepaMehta platform offers shared workspaces. For the negotiation about the meaning of structures, every shared workspace provides a forum and chat as standard communication tools. The DeepaMehta Unified Process provides a significantly more efficient development process than other existing processes because the DeepaMehta platform simultaneously copes with visual, verbal, and virtual modalities.
Customer solution examples kiezatlas, a geographical Cms
The DeepaMehta Unified Process accommodates constant changes in the Content, Structure, and Logic levels. The DeepaMehta platform supports the Brainstorming/Data Acquisition, Modeling, and Coding processes within one user interface
The first commercially deployed DeepaMehta application was “Kiezatlas”, a geographical content management system (CMS). It was contracted by the Verband für sozial-kulturelle Arbeit, (www. stadtteilzentren.de) the German umbrella organization of settlements and neighborhood centers.
DeepaMehta
Since 2004 Kiezatlas is successfully deployed to publish (city) maps of social relevant institutions on the Web site www.kiezatlas.de.
outlook Extended Support for Semantic technologies
amina knowledge platform The amina knowledge platform was contracted in 2006 by the German amina foundation, (www. amina-initiative.de). The amina initiative aims to promote corporate responsibility (CR) projects by establishing a dialog between companies, universities, and avant-garde thinkers. The amina knowledge platform is built on the basis of DeepaMehta. An interactive public demo is available (in German) at www.amina-wissensplattform.de. DeepaMehta is also utilized as a live-mapping tool during the various amina events.
Currently DeepaMehta can import and export topic maps in a modified XTM format. Future versions of DeepaMehta will support further semantic technologies and domain-specific applications: • •
DeepaMehta type definitions will be built from RDF Schema or vice versa. All topics and associations will be annotated by a Subject Identifier. This allows, for example, merging or interconnecting topic maps or whole corporate memories with each other while preserving their semantics.
Figure 11. The public Web frontend of the Kiezatlas geographical content management system
The left side displays locations of stores and institutions in a city map. The right side shows detail information about the selected institution. Institutions can also be found by category or by entering a search term
DeepaMehta
Figure 12. The Kiezatlas administrators use the DeepaMehta topic map frontend to define the underlying data models of city maps.
In the upper area DeepaMehta standard topic types and properties are visible, for example, “Person,” “Institution,” and “Topic Map.” In the lower area one can see how the Kiezatlas-specific topic types and properties are derived from (blue associations) and set into relation (purple associations) the DeepaMehta standard types. The topic type “Stadtplan” (city map), for example, derives its properties and behavior from “Topic Map” and adds its own property (green association). Furthermore the search criteria for the city map contents are defined via derivations and relations. Also part of the topic map are users, workgroups, and memberships (orange associations), to define access control (turquoise associations), that is, the responsibilities of the various (sub)administrators. The public Web site (Figure 8) as well as the editor backends for the institution owners (Figure 10) are generated directly from this data model, for example, if a new property or search criteria is added to the model, the Web site and the editor backend are updated automatically
•
0
DeepaMehta will import semantically enriched domain-specific data and transform and visualize them as a topic map, for example, when dropping a RDF enabled business card (involving the “foaf,” “contact,” and “geo” ontologies) to the DeepaMehta desktop, it will visualize the contents as a topic map, showing the person, with all relations to friends, projects, and a city map retrieved from google maps.
Extended Collaboration Features Essential features of every collaboration environment are (a) versioned data storage, (b) a change history, (c) notification, and (d) access control. •
Versioning is a good method to cope with competing change requests without establishing a locking mechanism. Currently DeepaMehta contents are not versioned.
DeepaMehta
Figure 13. The Kiezatlas editor backend is a form-based Web application by which institution owners can update institution information on their own.
The institution form is generated dynamically by the DeepaMehta Web engine, based on complex type definitions (Figure 9). The contact person of an institution, for example, is modeled as relation between the “Institution” topic type and the “Person” topic type. The DeepaMehta Web form generator embeds the Person form (with “First Name,” “Last Name,” “Gender” fields) inside the Institution form. To the editor the form looks like an ordinary HTML form, but with the DeepaMehta Web engine the user input is stored as a semantic network in the corporate memory. The contact person of an institution, for example, is represented as topic of type “Person” that is associated with the “Institution” topic
•
•
Future versions of DeepaMehta will support versioning at four levels: topic contents, association contents, topic map geometry/visibility, and file contents. A change history helps to keep track of content changes performed by users: what was changed by whom and when? Changes can be presented visually like in Microsoft Word’s Change-View or in Wikis. Certain changes can be reverted. Currently DeepaMehta provides no change history. A notification mechanism informs users of relevant actions performed by other users: what has been done by my colleagues since my last login? A crucial concern is granu-
•
larity: who should be notified and in what detail? Currently DeepaMehta’s notification mechanism is quite limited: members of shared workspaces are informed via messaging and e-mail once a topic map is updated but not about what has been changed. An access control mechanism is crucial to protect confidential information and privacy and to enforce user hierarchies. Currently DeepaMehta provides an access control mechanism but it is not flexible enough. Basically it works on type-level and has the concept of a topic-owner. Future versions of DeepaMehta will provide access control at instance-level and even property-level.
DeepaMehta
Figure 14. A topic map of the amina network
Relations between amina Corporate Responsibility topics (blue balls) and suitable university courses are shown in pink. Amina agents and their affiliations to corporations and universities are displayed alongside their mentorships (blue associations) for the amina topics. Every amina topic is related to a shared workspace for the students and mentors collaborative work (not visible here)
Extended Standard Applications
Architectural Concerns
The DeepaMehta platform comes with standard applications for Personal Information Management (PIM), Document Management, and Web browsing/searching. PIM includes handling emails, contact information, appointments, and notes. All these functions are at prototype-level and can not yet replace the traditional applications. The rendering of HTML pages, in particular, is currently too limited. Future versions of DeepaMehta will be able to replace the traditional e-mail, Web, text, and image applications and will import their data. The feature set that is used by 90% of the users will be provided. On high demand is the integration of a Web engine like Gecko. Furthermore, audio and video contents will be supported.
Currently DeepaMehta is a client-server system. The graphic DeepaMehta client is connected to one DeepaMehta server at a time. One server instance serves one corporate memory at a time. In order to fully exploit the network effect, future versions of DeepaMehta will allow one client to be connected with multiple servers resp. corporate memories at once. The requirements of associating topics from different corporate memories and of synchronization of certain parts of different corporate memories is apparent. A matching approach for topics is required. The Topic Maps concepts of Subject Indicators and Subject Identifiers would help here, but there is no obvious solution to these requirements yet. In order to support the growth of a large-scale network of DeepaMehta servers, one can replace
DeepaMehta
the client-server architecture by a peer-to-peer architecture. This opens up a lot of questions and requires in-depth discussions. In order to integrate the DeepaMehta application server with other (non-Java) back-end applications and services, the DeepaMehta server should provide the DeepaMehta applications as Web services. Because of the layered DeepaMehta architecture which clearly separates the application layer from the storage and presentation layers, it is already very close to a Service Oriented Architecture (SOA). For the moment there is no language independent interface to the application layer. Future versions of DeepaMehta will provide a SOAP interface to the DeepaMehta applications.
related work semantic desktop There are other semantic desktop environments, for example, “IRIS” (www.openiris.org), “Haystack” (http://groups.csail.mit.edu/haystack/), “Gnowsis” (www.gnowsis.org), or “Nepomuk” (http://nepomuk.semanticdesktop.org). But none
of them solve the problem of the missing work context in a cognitively adequate fashion (see “The Trouble with Computers and their solutions”).
graph-Based information Visualization There are other popular applications, for example, “TheBrain” and “Inxight StarTree” that deploy tree or graph-based visualization to navigate in information spaces. With “TheBrain” the user can organize notes and files into a tree structure. The application displays an extract of the tree as nodes and edges. The node currently focused by the user is displayed in the middle of the screen. Around the focused node the application places all neighboring nodes. These comprise all the nodes that have a direct connection to the focused node. All other nodes are not displayed. To navigate the tree structure, the user clicks on a visible node. The application then moves the clicked node to the middle of the screen and again displays its direct neighborhood. The tree layout is done automatically, according to rules not transparent to the user. Therefore “TheBrain” is not cognitively adequate as it does not satisfy
Figure 15. “The Brain” displays an extract of a tree structure, with the focused node in the middle of the screen. Setting another focus causes a complete rearrangement of the display. www.thebrain.com
DeepaMehta
Figure 16. “Inxight StarTree” deploys a hyperbolic projection to display different hierarchy levels at once. While navigating, the spatial neighbor-hoods of the nodes are not preserved. www.inxight.com/products/sdks/st/
the criteria of free positioning. Haller (2003) points this out in his thesis “Mappingverfahren zur Wissensorganisation”: The main advantage of [visual] mapping approaches is the possibility to organize information spatially, according to the user’s Cognitive Map (Chen & Czerwinski, 1998; Dillon, McKnight, & Richardson, 1993). So, it is important to let the user position the nodes freely in order to adapt the map to his/her internal spatial model. The nodes should keep their positions (at least relatively to their neighborhood), if the map is modified. Otherwise orientation in information space by means of Cognitive Maps is hindered. “Inxight StarTree” allows the visualization of extensive tree and network structures on a limited display space. Like “TheBrain,” the node that is focused by the user is displayed near the middle of the screen. But unlike “TheBrain,” not only the direct neighborhood is displayed, but also deeper levels of the node hierarchy. This is possible because “Inxight StarTree” deploys a projection
of a hyperbolic plane to a region of the screen. Effectively, an increasing scaling factor is used towards the screen borders. The tree or network structure is navigated quasi by moving the screen region within the hyperbolic plane. Due to the hyperbolic projection, it can happen that one minute node A is above node B and the next minute it is the other way around. This visualization approach is also cognitively inadequate as it does not allow the user to orientate himself within the information space. Both, “TheBrain” and “Inxight StarTree” allow the user to navigate large information spaces in an associative manner. But their automatic layout approaches are not cognitively adequate because they do not support the process of knowledge acquisition—learning—of the user. The visualization approach does not consider the mental state of the learner. A work environment for knowledge workers can be regarded as cognitively adequate if it supports associative navigation and a visualization approach that enables the user to arrange, and thus create, the display.
future researCh direCtions Until now artificial intelligence and Semantic Web have brought no significant benefit for the computer user. This situation will not change as long as computer scientists adhere to the rationalist tradition in AI and its reduced and mechanical understanding of our environment and human nature itself. The authors propose to reanimate the principles of soft cybernetics and to examine the images that underlie the current computer research and system designs.
Reanimating Soft Cybernetics The modern computer age is in its infancy and our understanding of what computers do and how their functioning is related to human language,
DeepaMehta
thought, and action is very limited. This is evident when software engineers use terms like “intelligence,” “recognition,” “meaning,” “learning,” “reasoning,” “knowledge,” and “understanding,” for example, to describe their systems. Computer science is practiced mainly by engineers. The authors propose interdisciplinary collaboration between computer scientists and humanists: psychologists, linguists, philosophers, and epistemologists, as well as with biologists and artists. To the knowledge of the authors, the last crucial effort for such collaboration were the Macy conferences held from 1946 to 1953. During the following years, computer research split into two schools of thought: hard cybernetics, which later became the AI movement, and soft cybernetics. It is the school of hard cyberneticists and the AI advocates that increasingly dominates computer science research. They receive the major funding and set the research agenda, while the soft cyberneticists seem to have disappeared from the scene.
The central points of these two schools of thought are: •
•
The hard cyberneticists and AI advocates believe that all things and processes, including language, understanding, learning, and social interaction, are describable by the means of logic. The meaning of a thing exists independently from a person that uses that thing, for example, the meaning of a text is hidden in the text itself and is independent from the reader. Cognitive aspects play no role in this belief, because cognition is a phenomenon that can be simulated by a mechanical-mathematical model. The soft cyberneticists believe intelligence is an evolutionary result of the environment in which it has emerged. Meaning emerges only in the moment of action. Cognitive systems are closed systems which emerge from themselves, in a process that can be called “Autopoiesis” (Maturana & Pörksen, 2002).
Figure 17. Feedback cycle of the human-machine-system
Human beings have intentions and negotiate/cooperate with each other about how to use the computer in a certain usage context. They make a mathematical model with which the machine can compute. The results are interpreted by human beings at two levels: (1) what to do with the result in the usage context? and (2) Meta-Interpretation: how did the result come about? Is the model correct?
DeepaMehta
Intelligence is inseparable from cognition and information is inseparable from its use. Computers can not be intelligent as long as they are not closed systems but dependent on a programmer. The authors suggest a redirection of attention away from the school of hard cybernetics and AI to a focus on the school of soft cybernetics, and to study the human-machine-system and the relation of cognition and computers. A soft cyberneticist does not see the computer as an entity that performs a dialog with the user, or that cooperates with the user, or that has any intention, because a computer is not a cognitive system. Even if the property of having intentions or the process of interpretation is included into a mathematical model, no new quality is established in the machine. The cycle is just delayed. In the end, it remains up to the human being to interpret the value of the generated results in respect to his/ her usage context. Human beings and machines
belong to different semantic realms, and the dividing line can not be removed. Interpretation can not be automatized. Interdisciplinary collaboration would help to get a better understanding of the human-machinesystem and to build computers with a greater benefit for the user.
Examining Underlying Images For the direction of future computer research, one needs to examine the underlying images that computer scientists and system designers have of the machine. One would foresee completely different application domains and create different user interfaces depending on whether one sees the computer, for example, as an assistant or as a tool: •
With the image of an assistant in mind, the computer is regarded as an intelligent agent, one who performs a dialog with the user, and understands the user’s intentions.
Figure 18. The underlying image of the machine determines the research direction and the resulting computer designs
If one sees the computer as an intelligent assistant (left side), one tries to build a machine with cognitive faculties. If one sees the computer as a tool (right side), one tries to design it to meet the demands of human beings in their environment
DeepaMehta
•
This is evident, for example, when the word processor asks one “A sentence must begin with a capital. Shall I do it for you?” Or when Semantic Web researchers try to delegate the process of semantic annotation to the machine, as if the machine could read and understand Web pages on one’s behalf. With the image of a tool in mind, the computer is regarded as a thing. The human being performs tasks and uses the tool to augment faculties.
Outside from computers, the building of tools has a very long tradition. We are far away from harnessing the digital power as we harnessed, for example, a hammer or a pencil. But if we ask the right questions about how digital tools should be built, we are on the right track. The authors propose that researchers and engineers adapt the tool image when formulating research issues and designing computer systems.
Research Issues Computer Science/Human Computer Interaction •
•
•
•
What are the implications for the Semantic Web, if semantics is not hidden in texts but only emerges when the text is used by human beings in a certain usage context? (Meaning as Use as described in Wittgenstein, 1953) What are the implications for artificial intelligence and the Semantic Web if “information and its use are inseparable and actually form a single process”? (Jerzy Konorski, cited in Foerster, 1993) How can a collaborative semantic work environment be designed to support constant changes of content, structure, and logic? What images support a sustainable technology development?
Cognitive Science • •
How can the process of knowledge creation be supported by a computer? How can a user interface be designed to exploit the inherent human cognitive faculties?
Communication Science/Linguistics •
How can the process of semantic emergence be supported by a computer?
Philosophy •
Do computers act?
Cultural Studies •
What comes after postmodernism? What could be the features of post-digitalism?
referenCes Canfield Smith, D., Irby, C., Kimball, R., Verplank, B., & Harslem, E. (1982). Designing the Star User Interface. Byte, 4, 242-282. Chen, C., & Czerwinski, M. (1998, June). From latent semantics to spatial hypermedia—an integrated approach. In Proceedings of the 9th ACM Conference on Hypertext (Hypertext ‘98), Pittsburgh, PA. Retrieved March 9, 2008, from www.pages.drexel.edu/~cc345/papers/ht98.pdf Dillon, A., McKnight, C., & Richardson, J. (1993). Space—the final chapter or why physical representations are not semantic intentions. In C. McKnight, A. Dillon, & J. Richardson (Eds.), Hypertext: A psychological perspective (pp. 169191). Chichester: Ellis Horwood. Foerster, H. v. (1993). Wissen und Gewissen. Versuch einer Brücke. Frankfurt am Main, Germany: Suhrkamp.
DeepaMehta
Grudin, J. (1990). Interface. In Proceedings of the 1990 ACM Conference on Computer Supported Cooperative Work (pp. 269-278). Los Angeles, CA: ACM Press. Haller, H. (2003). Mappingverfahren zur Wissensorganisation. Thesis. Published at KnowledgeBoard Europe. Retrieved March 9, 2008, from www.heikohaller.de/literatur/diplomarbeit/mapping_wissorg_haller.pdf Maturana, H. R., & Pörksen, B. (2002). Vom Sein zum Tun. Die Ursprünge der Biologie des Erkennens. Heidelberg, Germany: Carl-Auer-Systeme Verlag. Miller, G. A. (1956). The magical number seven, plus or minus two: Some limits on our capacity for processing information. Psychological Review, 63, 81-97. Murray, J. H. (2003). Inventing the medium. In N. Wardrip-Fruin & N. Montford (Eds.), The new media reader (pp. 3-11). Cambridge, MA: The MIT Press. Nelson, T. (2001). Talk at ACM conference on hypertext (Hypertext 2001). Retrieved March 9, 2008, from http://asi-www.informatik.uni-hamburg.de/personen/obendorf/download/2003/nelson_ht01.avi.bz2 Pepper, S., Vitali, F., Garshol, L. M., Gessa, N., & Presutti, V. (2006, February 10). A survey of RDF/topic maps interoperability proposals (W3C Working Group Note). Retrieved March 9, 2008, from www.w3.org/TR/rdftm-survey/ Richter, J., Völkel, M., & Haller, H. (2005, November). DeepaMehta — a semantic desktop. In S. Decker, J. Park, D. Quan, & L. Sauermann (Eds.), Proceedings of the 1st Workshop on The Semantic Desktop. 4th International Semantic Web Conference, Galway, Ireland (Vol. 175, CEUR-WS). Wittgenstein, L. (1953). Philosophische Untersuchungen. Frankfurt am Main, Germany: Suhrkamp (2003).
additional reading Semantic Web/Semantic Desktop Decker, S., & Frank, M. (2004). The networked semantic desktop. In Workshop on Application Design, Development and Implementation Issues in the Semantic Workshop at WWW2004, New York, USA. Retrieved March 9, 2008, from http://triple.semanticweb.org/svn/stefan/DeckerFrank.pdf Manola, F., & Miller, E. (2004, February 10). RDF primer (W3C Recommendation). Retrieved March 9, 2008, from www.w3.org/TR/rdf-primer/ Pepper, S. (2000). The TAO of topic maps. Finding the way in the age of infoglut. Retrieved March 9, 2008, from www.ontopia.net/topicmaps/materials/tao.html Pepper, S., & Moore, G. (2001). XML topic maps (XTM) 1.0 (TopicMaps.Org Specification). Retrieved March 9, 2008, from www.topicmaps. org/xtm/1.0/ Computer System Design Landauer, T. K. (1996). The trouble with computers: Usefulness, usability, and productivity. Cambridge, MA: The MIT Press. Norman, D. A. (1986). Cognitive engineering. In D. A. Norman & S. Draper (Eds.), User centered system design (pp. 31-61). NJ: Erlbaum. Suchman, L. A. (1987). Plans and situated actions: The problem of human-machine communication (learning in doing: Social, cognitive & computational perspectives). Cambridge, UK: Cambridge University Press. Winograd, T., & Flores, F. (1986). Understanding computers and cognition. A new foundation for design. Addison-Wesley Professional.
DeepaMehta
Philosophy of Language/Semantics Austin, J. L. (1962). How to do things with words. Cambridge, MA: Harvard University Press (2005). Searle, J. (1969). Speech acts. Cambridge, UK: Cambridge University Press. Cognition Foerster, H. v., & Pörksen, B. (2006). Wahrheit ist die Erfindung eines Lügners - Gespräche für
Skeptiker. Heidelberg, Germany: Carl-Auer-Systeme Verlag. Maturana, H. R., & Varela, F. J. (1992). The tree of knowledge. The Biological roots of human understanding. Boston, MA: Shambhala. Miscellaneous Weizenbaum, J. (1978). Die Macht der Computer und die Ohnmacht der Vernunft. Frankfurt am Main, Germany: Suhrkamp (2003).
Section III
Methods for Semantic Work Environments
Chapter XI
Added-Value:
Getting People into Semantic Work Environments Andrea Kohlhase Jacobs University Bremen and DFKI Bremen, Germany Normen Müller, Jacobs University Bremen, Germany
aBstraCt In this chapter we will look at users’ taking action processes in Semantic Work Environments. We argue that the underlying motivational problem between vast semantic potential and extra personal investment can be considered as a “Semantic Prisoner’s Dilemma” that builds on two competing value perspectives: The micro and macroperspective. The former informs a user’s decision for action, whereas the latter informs a designer’s decision for offering services. An in-depth analysis of the term “AddedValue” reveals its double relativity, which allows a sophisticated evaluation of such services from a microperspective. We use this property of double relativity for suggesting the “Added-Value Analysis” as a design method for getting people into Semantic Work Environments—showcasing its strength with a description of cPOint and cOnneXiOnS.
introduCtion In 1998, WWW inventor and W3C director Tim Berners-Lee proposed a rather gigantic project now called the “Semantic Web.” His road map is based on his understanding of the Semantic Web as “a Web in which machine reasoning will be ubiquitous and devastatingly powerful”
(Berners-Lee, 1998, p. 50) assuming that its data exists in machine-processable documents. Even though he was aware of the fact that “instead of asking machines to understand people’s language, it involves asking people to make the extra effort” (Berners-Lee, 1998, p. 50), he was so enamoured by the possibility to manage the Web’s data, see also Berners-Lee and Fischetti (1999),
Copyright © 2008, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
Added-Value
Berners-Lee, Hendler, and Lassila (2001), that he neglected the cost-benefits ratio involved for its users. Although the grand idea of a Semantic Web is well-established by now, it has not come into real life yet. To save the idea on a smaller scale and lighten the burden involved, Semantic Work Environments (SWE) have been proposed, but face similar difficulties to motivate users into (voluntary) action. This is because formalizing or explicating semantics per se is unnecessary for humans with their complex interpretation capability. If they do, they do it for a machine to understand them in the long run: is that worth the effort? Note that this is a problem inherent to semantic technology, not to collaborative or social technology like “Wikipedia.” We argue that the underlying motivational problem between vast semantic potential and extra personal investment can be analyzed in terms of the well-known nonzero-sum game “Prisoner’s Dilemma.” This “Semantic Prisoner’s Dilemma” consists in two competing perspectives on taking action: The micro- and the macroperspective. The latter is a view from without, having the overview of the value landscape, whereas former is a view from within, where not all value information is available. As only the user can take action, the user’s microperspective is decisive for getting her into an SWE. In contrast, an SWE design standpoint tentatively takes the macroperspective and expects users to go for the global optimum in the value landscape. We will show why a rational user can only go for the local optimum. In order to tip the scale of taking-action towards getting people into SWEs, we propose to change the values in the decision landscape, so that from a microperspective the local gains for the decision with the global optimum increase above the critical threshold for acting. In particular, if we enrich an SWE by elaborate, semantic services for the user’s concrete situation, then it is more probable that the scale tips in the desired direction.
But how to design such elaborate, semantic services? We suggest the “Added-Value Analysis” (AVA) as a design method. We will explicate the double relativity of the term “Added-Value,” which allows us to take various microperspectives into account in the design process. Even though the AVA process may feel familiar—and then “just” presents an explication of formerly implicit design processes, it lifts these good practices to a conceptual reflective level. For instance, the awareness about easy-to-fall-for catches (even for professional designers) allows to systematically avoid their consequences. Moreover, by its formalization, such a practice can be replicated by newcomers as well as all people involved in a software design process. Since the concept of “Added-Value” is often misinterpreted, we will elaborate on its history and usage, particularly because “the way in which Added-Value is defined effectively determines its role” (de Chernatony, Henry, & Riley, 2000, p. 43). We illustrate the technique by applying it to the SWEs cpOinT and cOnneXiOnS. Both are based on strong semantic representation formats for course materials, which make them comparable but complementary in their semantic services. cpOinT (Kohlhase, 2005b; Kohlhase, 2005a; Kohlhase & Kohlhase, 2004) is largely a personal SWE for managing and flexibly delivering large collections of MS PowerPoint (PPT) presentations. It is an open-source Semantic Work Environment from within PPT that facilitates semantic classification and annotation of PPT objects like images or text boxes. cpOinT was implemented by one of the authors within the Course-Capsules project at Carnegie-Mellon-University, Pittsburgh, PA. The system can convert semantically annotated PPT documents into the OMDOC format (Kohlhase, 2006). In contrast, cOnneXiOnS (Baraniuk et al., 2002; CNX, 2006) is a community-centered, Web-based content management system for advanced scholarly materials. These “scholarly
Added-Value
modules” are managed in a way that enables instructors to rapidly build and share courses, and assists students in self-steered learning and exploration of interrelations between various disciplines. The system has been developed at Rice University, Houston, Texas; our working group “Knowledge Adaptation and Reasoning for Content” (KWARC) at the Jacobs University, Bremen, Germany hosts the European cOnneXiOnS Centre, supported by ONCE-CS (2005).
the semantiC prisoner’s dilemma As a user’s motivation for taking action crucially depends on the trade-off between the (potential) benefit of and the investment needed for achieving it, we will now scrutinize the cost-benefits ratios induced by semantic work environments. All SWEs share the same problem: Semantically structured data are hard to come by. This problem is known as the “Authoring Problem” and invites two approaches: Either to let highly motivated or paid workers produce the semantic content, or to involve the user as a producer herself. As semantic technology realizes its potential only on large data sets, either the motivation or the money runs out before the potential could be realized. Therefore, the scheme of the “user as consumer and producer,” currently revolutionizing the Internet as Web 2.0 (Downes, 2005; O’Reilly, 2005; Weinberger, 2002), is also very attractive for developers of semantic technology, particularly SWEs. Hence, the responsibility for producing structured information is often given to the users. Their collaborative effort is expected to bring the potential of semantic technology to full bloom. But can the expectation for semantic potential (unspecific as it is) be enough to motivate users into taking action? If an action is considered to be a subjective, intentional activity, then the execution of actions are dependent on their execu-
tors’ appraisal of their effects. According to Heid (2004, p. 146), this recognition is guided by three questions: Who influences the value of an action’s outcome? Whose interests are implemented in that value? and Who assigns responsibility? In the semantic technology frame, the answers include the user, but are dominated by the other collaborators (including technology). Therefore, the user needs to decide whether to take action or not in a cooperation scenario with unspecific expectations about the will to collaborate. This situation was profoundly researched in Psychology and is called “Prisoner’s Dilemma,” which we introduce next.
the prisoner’s dilemma The well-known nonzero-sum game “Prisoner’s Dilemma” (Axelrod, 1984) is often used for analyzing short-term decision-making processes in cooperation scenarios, where the actors do not have any specific expectations about future interactions or collaborations. Concretely, two players, say famous Bonnie and Clyde, are imagined in a prison scenario, where they are independently confronted with cooperation offers by a public prosecutor, the sheriff. They can choose between two moves, either “cooperate” or “defect” (see Figure 1). The idea is that each player gains when both cooperate (i.e., if Bonnie and Clyde do not betray each other, then both will get only a few prison
Figure 1. Bonnie’s value landscape
Added-Value
terms), but if only one of them cooperates, the other one, who defects, will gain more. In particular, if Bonnie decided not to turn Clyde in, then her prison terms depend on his behaviour: If he cooperates with Bonnie, then she will serve 2 terms, but if he decides otherwise, she will serve 10 terms. If both defect, both lose (that is, if Bonnie as well as Clyde blow the whistle on the other, then both will serve 5 terms in prison), but not as much as the cheated cooperator, whose cooperation is not returned. The analogy of the “Prisoner’s Dilemma” to the SWE author’s situation is apparent since the potential of semantic technology does not represent specific expectations about future interactions. For instance, when a semantic author creates a content unit, then it can be fed into semantic systems (thereby fulfilling some of the potential), but the value of the invested knowledge did not increase by this indirect publication process. The addressee in this process is the machine, the objective that the machine can now deal with it. The author can only guess what happens to the content unit later on. In contrast, the aim of publishing a Wikipedia article consists in information collaboration. There, the author’s expectation is rather specific: Distribution of information and publication to fellow humans. Indeed, spelling out the consequences of the semantic interaction process in terms of the Prisoner’s Dilemma sounds all too familiar: If the author decides to invest her time and effort and others contribute as well, everyone profits tremendously from this synergy of cooperation. On the other hand, if just the author works on semantic mark-up, then she will gain nothing in the short run, but some in the long run (see Figure 2). We call this situation the “Semantic Prisoner’s Dilemma.” Since this scenario is a dilemma, a natural question to ask now is: What decision should the SWE author sensibly make?
the microperspectives in the semantic prisoner’s dilemma For a user of semantic material, the motivation for preferring semantically rich data is simple: Explicit document structure supports enhanced navigation and search, semantic mark-up yields context and search by content. Furthermore, the higher the degree of semantic structure, the more services can feed on the material, the higher the benefit for the user. But this is only a standpoint from without—a macroperspective in which all benefits and sacrifices are known and the global decision optimum can be perceived (see Figure 2). The entity of “all” microperspectives informs the macroperspective on the conceptual level towards the global optimum, therefore, the (macroperspective of a) designer is really just concerned with this optimum. From within the situation though, that is, from a microperspective, there is also motivation against taking action: The cost of creating a document is proportional to the depth of the mark-up involved. However, once the mark-up quality passes a certain threshold which supports flexible reuse of fragments—content creation costs may actually go down as they are dominated by the cost of finding suitable (already existent) knowledge elements. Thus, the author is interested in a high reuse ratio, provided that retrieval costs are not prohibitive. The benefits seem obvious for the author who has the opportunity to reuse her own content modules frequently, but the real payoff comes when she is
Figure 2. The semantic prisoner’s dilemma
Added-Value
part of a group of individuals that share content objects and knowledge structures freely. In the Prisoner’s Dilemma, if the decisionmakers were purely rational, they would never cooperate (without at-hand incentives) as they should make the decision which is best for them individually. Suppose the other one would defect, then it is rational to defect yourself: You will not gain much, but if you do not defect you will have all the work. On the other hand, suppose the other one would cooperate. Then you will gain (especially in the long run) whatever you decide, but you will gain more if you do not cooperate (as you do not have to invest your time and effort). So here too, the rational choice is to defect. The problem is that if all content authors are rational, all will decide to defect, and none of them will gain anything. In particular, the sensible decision for an SWE author is her non-cooperation based on individuals’ microperspectives. Therefore, users’ expectations may not solely depend on an SWE’s semantic long-term potential, as each user’s realities dominate the decision process. The Semantic Prisoner’s Dilemma is based on two competing perspectives on the situational value distribution. The macroperspective allows the consideration of all values and hence enforces the decision for the global optimum for all, whereas the microperspective lets the user interpret the known values according to her local optimum. The latter is decisive for the process of takingaction. Therefore, our approach in this chapter, to tip the taking-action scale towards getting people into SWEs, consists of manipulating the values in the decision landscape, so that from a microperspective the gains increase above the critical threshold for acting. In particular, if we enrich an SWE by elaborate, semantic AddedValue services for the concrete situation the user is in, then it is more probable that the tip goes in the wanted direction. But Added-Value services are often misunderstood, therefore we start off with the underlying concepts and develop an SWE design strategy for “Added-Values”.
added-value analysis as a design method The term “Added-Value” has often been used as an umbrella term up to the point of actually losing any serious meaning. In the following we try to reestablish its meaning and its relevance for SWE design by disclosing its history (and marketing aspects), pitfalls, and potential. As there are many (almost) equivalent formulations of the term (see a list further below), we stress the underlying concept character by using the capitalized diction “Added-Value.” The story of “Added-Values” in Science—we surmise despite occasional earlier occurrences— started in 1997 with Don O’Neills statement: “The value add of software to the national economy is not well understood” (O’Neill, 1997, p. 11) and his following description of a study (supported by the American National Software Council) that aimed to understand this “value add” on the level of the national economy of using software vs. traditional means. The central question was how people can be motivated to replace their formalizable procedures by software processes. O’Neill tried to analyze and then to “sell” the advantages of software to the public. Note that the term “Added-Value” is strongly connected to marketing issues here. Subsequently, the term was used in phrases like “added value” (Mana-Lopez, 2004; Nielsen, Overgaard, Pedersen, Stage, & Stenild, 2006), “adding value” (Acken, 1998; Cosley, Frankoswki, Terveen, & Riedl, 2006; Dow, Hackbarth, & Wong, 2006; O’Reilly, 2005), “value-added” (Berghel, 1999; Lindgaard, 2004), “value add” (O’Neill, 1997), “value-based” (Boehm, 2003), and so forth in papers in Computer Science, almost always to convince people of the “real” value of its respective product or requesting value considerations. In an online survey about semantic Added-Value services by the authors, the marketing character of the term was confirmed. For instance, someone associated the well-known
Added-Value
phrase “It’s not a bug, it’s a feature” with AddedValue services, another was reminded of AddedValue discussions in the UMTS debate with the “connotation that this would make people pay for weird data services.” The reason for the difficulty using the term is the subjectivity of the “value” concept and the use of such emphases like “more” or “added”: All of them are relative concepts and do not have any absolute or objective meaning. Therefore, we speak of the “double relativity of Added-Value.” This double relativity is based on the microperspective, which we are mainly interested in here. We will analyze and discuss the term “Added-Value” from the macro- as well as microperspective to mark off their respective properties. We will start out with recalling an analysis of the term within Marketing Science by de Chernatony et al. (2000) and combining it with semantic technology design attitudes. From a literature review, de Chernatony et al. (2000) discerned three subdomains with distinct value definitions: Pricing, Consumer Behaviour, and Strategy literature.
Strategy In the Strategy articles the macroperspective on value was the strongest and the most undifferentiated: A value was simply described as “what buyers are willing to pay” (de Chernatony et al., 2000, p. 41), that is, the price of a product or service. This subdomain is only interested in setting the general frame, so they explicitly take the view from without. They understand value in terms of suppliers, not of buyers (even though the word is used); therefore they use the monetary phrasing. This can be compared with scientific visions of semantic technology like Berners-Lee’s “Semantic Web,” setting the frame in terms of offered potential.
Consumer Behaviour The value definition in the Consumer Behaviour subdomain differs from the one in the strategy domain as the value is here “defined in terms of customer needs and what is desirable” (de Chernatony et al., 2000, p. 40). A consumption value is considered to have five components: Functional, social, emotional, epistemic, and conditional (Sheth, Newman, & Gross, 1991). The product is seen as “complex cluster of value satisfactions” (de Chernatony et al., 2000, p. 41, citing Levitt). Surprisingly, we see the macroperspective at work here even though the consumer has the central role in these definitions. But modelling the consumption value is clearly a view from without, which makes the customer more comprehensible. Analogously, positing the product as a mixture of value satisfactions, does not imply a customer perspective, because just the satisfactions at the end and not the process seem to be of value.
pricing In contrast, we find that the Pricing articles with respect to “value” take the microperspective. Here, value has been defined as “the trade-off between customer’s perceptions of benefits received and sacrifices incurred” (de Chernatony et al., 2000, p. 40). The pricing subdomain takes into account that the most rational price might not be the one that the user is actually willing to pay. The optimal value depends on the customer’s perception, that is, it is contingent on the here-and-now of the individual. We think this value definition to be the most suited one for our purposes, and we can approach the definition of “Added-Value.” To contrast the latter from “value” Grönross distinguishes “an offering’s core value [. . . to be] the core solution and its added value as additional services” (Grönross, 1997, p. 408). It is striking that for the definition of Added-Value, we have to settle on what the core solution is, that is, we need to know
Added-Value
the core problem first. In particular, we have to specify the core problem (possibly comprising several subproblems) to know what the core solution is, and then we can look at this solution with our value term (henceforth called core value), see Figure 3. Therefore, the main task in determining Added-Value consists in establishing the (perceived) benefits and sacrifices of the core solution with respect to the core problem. Quite often, this core problem is kept rather veiled. For instance, in the online questionnaire mentioned above, the core problem was frequently seen to be the argumentation for semantic technology against traditional technology. But if we accept that, the core solution is the concrete implementation satisfying a traditional task (others can by definition not be solved by traditional technology), then all advantages of the underlying semantics could be used for producing AddedValues. In contrast, if we define the core problem as making use of machine-understandable data or equivalently as the question “How can computers help us to rationalize our processes (at work or at home)?” then semantic services deliver core solutions. Therefore, here Added-Value services can only be non-semantic ones, for example, reducing the sacrifice of semantic mark-up. As we can see, different core problem settings allow different Added-Value services (AVS), that is, services that are evaluated with a specific core problem and solution in mind from a microperspective. Now, how can Added-Value services with their inherent double relativity be of use in
lifting the values in the decision situation towards taking-action?