<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Human and Social Aspects of Decentralized Knowledge Communities</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science, University of Saskatchewan Saskatoon</institution>
          ,
          <addr-line>SK S7N 5C9</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>To design an infrastructure for knowledge communities, we need both technical expertise and an understanding of human and social aspects of communities. Technologies for implementing such infrastructures are often available. However, there is no clear, proven procedure for building successful communities. In this paper, we review research literature concerning user practices and social aspects of information and knowledge management. Based on this review, we propose preliminary design criteria for Semantic Desktop systems.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Designing an infrastructure for knowledge communities requires not only
technical expertise, but also a proper understanding of the human and social aspects
of communities. Understanding these aspects is necessary because the success of
communities often depends on subtle design issues [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ].
      </p>
      <p>The structure and dynamics of a community emerge from local interactions of
its members. These interactions cannot be controlled to produce specific
collective behaviour, as each community member is autonomous and interdependent.
However, we can support communities by designing an infrastructure that fosters
characteristics of successful communities, such as a high level of participation,
contribution, and cooperation among community members.</p>
      <p>
        Recently, a vision [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] has emerged of building peer-to-peer (P2P),
semantically rich knowledge communities. The basic idea is to apply Semantic Web
principles [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] to personal information management (PIM), resulting in Semantic
Desktop systems (e.g., [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ]). Then these systems are interconnected using a
P2P protocol, providing an infrastructure for online communities. Some of the
technical aspects of such infrastructures have been discussed elsewhere (e.g., [
        <xref ref-type="bibr" rid="ref3 ref5 ref6 ref7">3,
5–7</xref>
        ]). However, the discussions so far have overlooked the existing user practices
in PIM and social aspects of communities. Unless the new infrastructures
accommodate these practices, they will not be adopted by users, and their applications
will be severely limited.
      </p>
      <p>
        In this paper, we review previous research on personal information
management and social aspects of knowledge management, so that lessons from many
user studies about PIM and online communities can be used for implementing the
vision of P2P knowledge communities [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The paper consists of five main parts:
(1) user practices in PIM, (2) problems in information management, (3) various
approaches to solving the problems, (4) design criteria for Semantic Desktop
systems, and (5) social aspects of knowledge communities.
      </p>
      <p>In the first three parts, we give background information about PIM—activities
in organizing and managing information for personal use. The discussion focuses
on human factors in PIM, which then become the basis for the development
of criteria for designing Semantic Desktop systems. In the last part, we discuss
social aspects of communities, such as the role of social networks in information
and knowledge management, and factors that motivate users to contribute to
their communities.
2</p>
    </sec>
    <sec id="sec-2">
      <title>User Practices in Personal Information Management</title>
      <p>This section discusses existing research on user practices in personal information
management. First, it outlines common purposes of PIM, then discusses different
types of filing behaviours, and finally highlights the importance of various cues
in information management.
2.1</p>
      <sec id="sec-2-1">
        <title>Basic Purposes: Finding and Reminding</title>
        <p>
          People manage their documents not only to make it easier to find them later,
but also to remind themselves of their tasks [
          <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
          ]. To make finding documents
easier, people arrange the documents according to some logical order. To achieve
the reminding function, they make relevant documents more visible than others.
For example, putting a document on a computer desktop can remind the user
to work on the document.
        </p>
        <p>
          To support finding and reminding, people organize their documents using
“files” and “piles” [
          <xref ref-type="bibr" rid="ref10 ref8">8, 10</xref>
          ]. Files are organized document collections and usually
contain archived information. Piles, on the other hand, are disorganized
document collections and typically contain work-in-progress documents. A pile can
function as a reminder and a temporary organizational unit. Although not
organized explicitly, elements of a pile may naturally follow reverse chronological
order [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>
          When searching for specific information on their personal computer, users
prefer to browse their directories manually than to use a search tool [
          <xref ref-type="bibr" rid="ref11 ref12 ref9">9, 11, 12</xref>
          ].
This preference may result from users’ familiarity with their personal workspace:
they feel that they know where they have saved a document. Users tend to use
a search tool only when they cannot find a document manually, or when they
search information that is available outside their personal workspace, such as on
a shared file server or on the Web.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Filing Behaviour</title>
        <p>A common activity in information management is to file documents; that is, to
place documents in an appropriate folder or category.</p>
        <p>
          People’s behaviour in organizing their documents ranges from “pilers” to
“filers” [
          <xref ref-type="bibr" rid="ref12 ref13 ref14">12–14</xref>
          ]. Pilers are users who do not categorize their documents. An
example is an email user who leaves all incoming messages in the inbox. Filers,
on the other hand, are those who use folders extensively; they create many folders
and classify their documents into various folders on a daily basis.
        </p>
        <p>
          Personality traits and job types affect people’s filing behaviour. Some people
tend to be more organized than others. People whose tasks are structured and
routine tend to file their documents more frequently than those whose tasks are
unstructured [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. For knowledge workers [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], for example, filing information is
often not so important, as their work relies heavily on creativity and knowledge
that is in their mind. Thus, knowledge workers focus on absorbing information
contained in documents, rather than relying on them.
        </p>
        <p>
          Researchers have observed filing behaviour in various applications, such as
email [
          <xref ref-type="bibr" rid="ref12 ref14">12, 14</xref>
          ], Web bookmarks [
          <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
          ], and file systems [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. The classification of
filing behaviour in these studies, however, is not absolute. People’s behaviour is
complex, so it is possible to refine the suggested classification schemes. Boardman
and Sasse [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] observe that users in practice use multiple strategies to manage
emails and Web bookmarks. Specifically, some email users file important
messages immediately (frequent filers), but leave other messages in the inbox and
organize them occasionally (spring cleaners). Similarly, Internet users organize
some of their new Web bookmarks at the creation time (creation-time filers),
but leave others as they are (no-filers).
        </p>
        <p>The research discussed above studies how frequently and when people file
their documents, but it does not discuss how people group their documents.
What factors affect classificatory decisions?</p>
        <p>
          Documents’ intended use or purpose appears to be a strong factor that
affects classificatory decisions [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. People tend to group documents based on the
task related to the documents, such as grouping all materials for teaching a
course Computer Science 101. Basic properties of documents—their size, type,
or author—are less influential than their intended use. In organizing photos [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ],
however, people typically use temporal information, such as events or date, as
the main factor in making classificatory decisions.
2.3
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>The Importance of Context and Cues</title>
        <p>People use various cues to maintain contextual information of their documents.
A business card attached on a paper may serve as a reminder to send the paper
to a particular person. A date written on top of a document may remind the
user of a project’s deadline. A red folder may indicate the urgency of documents
within it. These cues, however, can be interpreted and used in different ways.
Therefore, knowing the context in which such cues are being used is crucial.</p>
        <p>
          Context is important for a proper understanding of information and in the
recall process [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. A classic example, as discussed in [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ], is a chess study [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
This study suggests that chess experts can reconstruct chess positions from real
play well because the positions are meaningful to them, which helps in recall.
When the positions are randomized, their ability to recall declines significantly.
In the context of information management, associating a document with various
cues—visual, spatial, chronological, or contextual—can improve people’s ability
to find the document because humans are good at remembering the appearance,
essence, and context of a document. Without such cues, people have to remember
details, such as filenames, which they are not good at.
        </p>
        <p>
          Spatial locations of documents also carry semantic information to the user. In
office organization, people keep documents that are more recent or urgent closer
to the centre of their working area [
          <xref ref-type="bibr" rid="ref20 ref8">8, 20</xref>
          ]. In desktop organization, computer
users arrange their screen systematically [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]: they group program shortcuts on
a specific region, put related documents close to each other, and try to arrange
their screen’s layout symmetrically. Such spatial organizations can help users
locate frequently used programs and documents on their computer.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Problems in Information Management</title>
      <p>Current systems for PIM are far from being perfect. Studies report four areas
where improvement is necessary: supporting information organization better,
maintaining context and retrieval cues, dealing with the problem of information
overload, and supporting interoperability between individuals or organizations.
3.1</p>
      <sec id="sec-3-1">
        <title>Filing</title>
        <p>
          Filing information is difficult. It has been observed in various studies, including
office organization [
          <xref ref-type="bibr" rid="ref10 ref8">8, 10</xref>
          ], email management [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], and desktop organization [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
In these studies, users state that filing is a heavyweight cognitive activity: they
cannot make classificatory decisions easily. When filing a document, users try
to put the document into a category in which they expect to remember it for
later retrieval. Because there are many ways to organize documents, as discussed
in section 2.2, a classification scheme that is currently appropriate may become
unsuitable as the user requirements or goals change over time.
        </p>
        <p>
          The currently predominant hierarchical structure in information management
makes filing information difficult and inflexible. In the physical world, people are
limited to having to put a document into one specific folder, unless they make a
copy of the document, which then can be put in a different folder. Unfortunately,
most file systems and computer applications impose the same restriction: they
do not allow users to classify a document into multiple categories (e.g., folders
or directories). Although users can alleviate this problem by making copies of
documents or links to files, they normally do not do this [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
        </p>
        <p>Hierarchies also restrict users from capturing multiple semantics of a
document. Where should a user save a paper about the Semantic Web and ontology,
in a “Semantic Web” or an “Ontology” directory? Filing the paper in either of
these categories causes loss of information about the document’s content. And
it complicates the retrieval process, as the user has to remember exactly the
location of the paper. Although the user could create a “Semantic Web and
Ontology” directory, it is uncommon to have a category with multiple semantics.</p>
        <p>The ambiguity of natural languages also contributes to the difficulty of filing
information. A word can refer to different things. A category “Networks” may
refer to network protocols, Internet applications, or even network marketing.
Thus, it is difficult to choose good names for semantic categories. In addition,
it is hard later to remember the intended semantics of the categories, as the
mind-set of the user may change in the meantime. Often a category created with
a specific semantics “evolves” due to filing of documents that do not exactly fit
in it, because users are reluctant to create a new category, since this may require
reorganization of the previously classified documents.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Maintaining Context and Retrieval Cues</title>
        <p>
          Computer systems offer limited supports for maintaining context and retrieval
cues in information management. Visual, contextual, and spatial cues are
important for finding and reminding [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. In the physical world, tangible documents
have rich features, such as colour, size and thickness, which can serve as retrieval
cues. For example, when searching for a book, people may forget the book’s title,
but they usually can still remember the book’s appearance. Therefore, they can
limit their search based on these cues. Unfortunately, many of these cues are
lost in the digital world. Instead of maintaining visual retrieval cues, computer
systems display details of files, such as their name, type, and size, which are
less useful for retrieval cues. Furthermore, there are only limited possibilities for
users to arrange the spatial layout of their document collections.
        </p>
        <p>
          Filing documents removes some contextual information of the documents.
Suppose that in an office, a user keeps urgent documents in a red folder. While
the folder is on a desk, it can remind the user of the urgency of the documents
within it. However, when the user puts the folder into a filing cabinet, the user
can no longer see the urgency denoted by the red colour. A similar effect applies
to digital documents. For example, saving an email attachment in a file folder
removes the contextual information (e.g., from whom and when the document
was received), which is usually available in the email body [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ].
        </p>
        <p>Context can also be lost because of some habitual use of computer
applications. For example, an email’s subject and its content are not necessarily
consistent, as users often simply press “reply” to an old message when starting new
conversational threads. In a long conversational thread, users may not include all
previous messages when sending a reply. They may also discuss topics that are
irrelevant to the initial topic of discussion without changing the email subject.
3.3</p>
      </sec>
      <sec id="sec-3-3">
        <title>Information Overload</title>
        <p>
          People often have to deal with amounts of information exceeding their processing
capability. This phenomenon appears in various studies of management of files
[
          <xref ref-type="bibr" rid="ref9">9</xref>
          ], paper archives [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ], email [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], and social networks [
          <xref ref-type="bibr" rid="ref22 ref23">22, 23</xref>
          ]. Across these
studies, the main problem is related to the volume of information that people have
to manage. On a closer look, however, there are finer issues in the information
overload problem as discussed below.
        </p>
        <p>
          People need to manage many ephemeral documents [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ], such as emails and
memos. Ephemeral documents usually serve as reminders, so they should be kept
visible. However, computer screens are spatially limited, so users cannot arrange
such documents freely. Moreover, the lifetime of these documents sometimes
depends on other people. For example, a note is only relevant until a reply from
another person arrives. Unfortunately, not all people respond to others’ requests
timely, making the management of ephemeral documents more difficult.
        </p>
        <p>
          Studies [
          <xref ref-type="bibr" rid="ref14 ref24">14, 24</xref>
          ] observe that people use email not only for communication,
but also for reminders, personal archiving, and task and contact management.
These practices exacerbate the information overload problem, as they cause users
to receive and manage more messages without using the right tool.
        </p>
        <p>
          Another problem related to information overload, called premature filing, is
observed in the management of paper archives [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. This problem is described as
follows. When receiving many documents, people cannot always decide the
usefulness of these documents immediately. While they do not want to keep useless
documents, they consider the potential value of these documents and hence
hesitate to discard them right away. So they decide to file these documents, hoping
to find time to assess their value later. Unfortunately, filing makes documents
less visible. As people receive many new documents, they often forget about
their filed documents. As a result, they keep many documents, which have little
value to them, and are often discarded later without ever being read [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ].
3.4
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>Interoperability</title>
        <p>Problems in personal information management escalate when people have to
share documents. People are familiar with their personal workspace: they
organize it personally, know the contents of their document collections well, and
decide the semantic organization of their workspace by themselves. These
characteristics, however, do not exist in a shared repository: several people have
access to the repository; others may add new documents to it; and as a team,
they have to agree to some convention of how to organize this repository.</p>
        <p>
          Due to the rich semantics in natural languages, people often use different
words to refer to the same concept, and use the same word to refer to different
concepts. According to Furnas et al. [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ], the probability of two persons choosing
the same word to describe the same concept is less than 0.20. In other words, it
is unlikely that people will use the same vocabulary to describe the same things.
        </p>
        <p>
          In collaborative work involving different groups of people, each group may
require local customizations of documents, have different views of the shared
objects, or favour a certain filing scheme [
          <xref ref-type="bibr" rid="ref26 ref27">26, 27</xref>
          ]. Dourish et al. [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] report that
in an organization that has a standard filing scheme, each group still needs to
adjust the standard filing scheme to meet requirements of different projects. As
each group has its own local view, document sharing between groups becomes
complicated. To be understandable, local customizations should be presented to
each group differently, ideally, according to the corresponding group’s local view.
        </p>
        <p>
          Even for a small, relatively homogeneous team [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ], interoperability
problems exist. These problems include personal preferences over coarse- or
finegrained categorization, topic- or purpose-based categorization, and syntactic- or
semantic-based categorization.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Approaches to Handling Problems in Information</title>
    </sec>
    <sec id="sec-5">
      <title>Management</title>
      <p>A variety of approaches have been proposed to deal with the problems discussed
in the previous section. We focus on four main approaches below: tagging, flexible
collections, temporal-based organizations, and the Semantic Desktop.
4.1</p>
      <sec id="sec-5-1">
        <title>Tagging</title>
        <p>
          The basic principle of tagging is to assign attributes (i.e., hfield, valuei pairs)
to documents, and then to allow users to use these attributes to organize and
retrieve documents [
          <xref ref-type="bibr" rid="ref29 ref30 ref31">29–31</xref>
          ]. This principle enables users to assign multiple
attributes to a document, so they can express the semantics of a document more
flexibly. Users are no longer limited to having to classify a document into a single
category as with filing.
        </p>
        <p>
          The concept of tagging has been applied to several file systems [
          <xref ref-type="bibr" rid="ref29 ref30 ref32">29, 30, 32</xref>
          ].
These systems use tagging for providing a flexible way of retrieving and grouping
files. To retrieve and group files, users are no longer restricted to one strict
hierarchical structure. Instead, they can group files based on a certain attribute
of the files. For example, in a Semantic File System [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ], to retrieve all papers
about Semantic Web, a user can submit a query “topic=semantic web”1 and the
system will create a virtual directory containing all files that match the query.
        </p>
        <p>
          Attributes have been used not only for providing associative access in file
systems, but also for providing personalized services [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ] and managing
documents [
          <xref ref-type="bibr" rid="ref31 ref34 ref35">31, 34, 35</xref>
          ]. In general, these systems use attributes to capture metadata
and to provide a flexible way of organizing and retrieving documents. Placeless
Document Systems [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ], however, extend this usage by allowing an attribute’s
value to be active code. So, for example, users can assign a program to a
document, which backups the document periodically. This allows to associate not
just semantics, but also computation with the corresponding documents.
4.2
        </p>
      </sec>
      <sec id="sec-5-2">
        <title>Flexible Collections</title>
        <p>
          Collections are an abstraction for handling the limitations of a hierarchical
structure and for providing a flexible way of organizing various types of documents.
There are two main principles of collections [
          <xref ref-type="bibr" rid="ref31 ref36">31, 36</xref>
          ]: (1) a document can
belong to multiple collections, and (2) a collection can contain different types of
documents.
        </p>
        <p>
          The first principle allows a document to become a member of several different
collections. This membership can be static, dynamic, or a combination of static
1 The actual form of queries in Semantic File Systems is specified as virtual directory
names, e.g., /sfs/topic:/semanticweb.
and dynamic. For example, semantic directories [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] and fluid collections [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]
enable users to specify an inclusion list, an exclusion list, and a query to create a
collection. The inclusion list contains a list of documents that must be included
in the collection regardless of the query. The exclusion list specifies documents
that must be excluded from the collection even if they match the query. The
query states the criteria of documents to be included in the collection.
        </p>
        <p>The second principle enables users to put various types of documents—such
as emails, Web bookmarks, appointments, contact lists, and Word documents—
together into a collection. Users can organize their documents in a more logical
and meaningful way, as document organization is abstracted from the
applications that produce the documents.
4.3</p>
      </sec>
      <sec id="sec-5-3">
        <title>Time-Based Approaches</title>
        <p>
          Time-based approaches provide an alternative to the desktop metaphor for
managing information. These approaches are based on the fact that time is an
important retrieval cue in information management [
          <xref ref-type="bibr" rid="ref17 ref37 ref8">8, 17, 37</xref>
          ]. Examples of such
approaches include Lifestreams [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ] and Time-Machine Computing [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ].
        </p>
        <p>
          Lifestreams [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ] stores a user’s personal information chronologically as a
lifestream. A lifestream contains old documents, working documents, and
possibly, future documents, such as appointments and reminders. A document’s name
is not mandatory because the system is responsible for identifying and placing
the document in the lifestream. To facilitate information organization and
retrieval, the user can create substreams to display only subsets of documents in
the lifestream. Within a substream, the user can refine the query further by
creating other substreams. Finally, Lifestreams is also capable of summarizing
information in a substream and presenting the result to the user.
        </p>
        <p>
          Time-Machine Computing (TMC) [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ] extends the idea of Lifestreams [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ]
by capturing both temporal and spatial information of a document. To do so,
TMC provides a special desktop that allows users to keep and organize their
documents spatially on this desktop. Users may remove documents from their
desktop. However, these documents are not deleted permanently because TMC
keeps track of any state changes on the desktop. Thus, users can access their
removed document by setting their desktop’s time back to a point before they
remove the desired document, and TMC will restore the state of the users’
desktop at the specified time.
4.4
        </p>
      </sec>
      <sec id="sec-5-4">
        <title>The Semantic Desktop</title>
        <p>
          The core technology of the Semantic Desktop is the Semantic Web [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]: an
extension of the current World Wide Web that enables machines to “understand”
and process information intelligently. As discussed in [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], the main components
of the Semantic Web consist of the Extensible Markup Language (XML), the
Resource Description Framework (RDF), and ontologies. XML enables users to
create arbitrary tags for describing the structure of documents. RDF provides a
framework to express the meaning of information using XML. And an ontology—
“an explicit specification of conceptualization” [
          <xref ref-type="bibr" rid="ref40">40</xref>
          ]—makes information sharing
meaningful by providing a set of vocabulary to discuss a particular domain.
        </p>
        <p>
          The main idea of the Semantic Desktop [
          <xref ref-type="bibr" rid="ref3 ref5 ref6">3, 5, 6</xref>
          ] is to apply principles of the
Semantic Web [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] to personal information management. This approach allows
the creation of semantically rich PIM tools. Semantic Desktop systems can use
RDF to express both the structure and semantics of webs of information on a
user’s personal computer as metadata. Because this metadata can be
“understood” by machines, this approach has potential for improving current practices
in PIM: information overload can be reduced by delegating well-defined tasks to
agents; information sharing can be more meaningful and contextually rich, as the
corresponding metadata is also shared and described using common ontologies.
        </p>
        <p>
          Like the Semantic Web, the Semantic Desktop treats information as a Web
resource, so information is identified using a Uniform Resource Identifier [
          <xref ref-type="bibr" rid="ref3 ref6">3,
6</xref>
          ]. Some projects developing Semantic Desktop systems include Haystack [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ],
Gnowsis [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], Chandler,2 and Fenfire.3
5
        </p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Design Criteria for Semantic Desktop Systems</title>
      <p>
        To be adopted widely by users, Semantic Desktop systems must be designed
properly. One of the most important aspects in design is to know the users. Thus,
based on the existing user practices and limitations of approaches to personal
information management, we propose preliminary design criteria for evaluating
Semantic Desktop systems as follows:
– Flexibility: A Semantic Desktop system should support flexible
information organization. This organization should be abstracted from both the
structure of information storage (e.g., hierarchical file systems) and desktop
applications (e.g., email tools, Web browsers, and task management tools).
Grouping and regrouping information should be easy. Users should be able
to arrange information based on their logical views, intentions, or usage
patterns. For example, users should have options to sort information based on
its frequency of access, its level of importance, or its level of urgency.
Flexibility is important because users have different needs and preferences in
organizing information (see section 2.2).
– Retrievability: Users should be able to find desired information easily. Just
like other Web resources, users’ personal information should be accessible
virtually from anywhere. Users do not need to know where their data actually
resides on. And since users like browsing their personal workspace [
        <xref ref-type="bibr" rid="ref11 ref12 ref9">9, 11, 12</xref>
        ],
a Semantic Desktop system should provide a good browser, which supports
multiple information visualizations and allows users to see cues and
contextual information of their documents to facilitate retrieval. In other words,
the search mechanism should favour recognition over recall.
      </p>
      <sec id="sec-6-1">
        <title>2 http://www.osafoundation.org/Chandler Compelling Vision.htm 3 http://fenfire.org/vision.html</title>
        <p>
          – Security: While easy access to information is desirable, security must not be
compromised. Every access to the user’s data must be authorized. Sensitive
information should be transferred through a secure channel and encrypted.
A Semantic Desktop system should authenticate shared data and metadata.
Also, it should allow users to control access privileges of their information
(e.g., public, group, or private data).
– Context maintenance: Contextual information of documents is usually
stored as metadata. Creating metadata sometimes requires manual input
from users. Unfortunately, users are generally reluctant to do more work,
such as typing additional information about a document. Thus, a Semantic
Desktop system should be able to capture or create metadata automatically,
for example, by using context analysis [
          <xref ref-type="bibr" rid="ref41">41</xref>
          ] or data-mining techniques. If
user input is unavoidable, then the system should provide a mechanism that
allows easy annotation (e.g., [
          <xref ref-type="bibr" rid="ref42">42</xref>
          ]). Presenting summaries of interactions [
          <xref ref-type="bibr" rid="ref43">43</xref>
          ]
can also help users recall the context of interactions while communicating
with other people.
– Proactiveness: A Semantic Desktop system should be proactive in
promoting awareness to the user. Examples include notifying users when they
receive emails from their important contacts, highlighting important or
related documents, and reminding users of their appointments and tasks.
– Cognitive load: A Semantic Desktop system should minimize the user’s
cognitive effort necessary to use the system. Reducing cognitive load can
be achieved using various ways, such as encapsulating technical details from
users, enabling users to delegate well-defined tasks to agents, presenting
summaries of information, and filtering in/out incoming information.
– Interoperability: Interoperability can be examined from different
perspectives. At a system level, a Semantic Desktop system should promote
interoperability both among desktop applications on a single computer and with
other Semantic Desktop systems. At a user level, the system should resolve
inconsistencies among different ontologies used by users.
– Performance: A system performance should be reasonable and acceptable
to users. Responses to user queries should be timely. Resource consumption
and allocation should be well managed.
        </p>
        <p>Evaluating a PIM tool rigorously requires a well-designed user study and
in-depth analysis. While such rigorous analysis is out of scope of this paper, we
present simple analyses to illustrate trade-offs of existing approaches to PIM.</p>
        <p>Most operating systems and desktop applications currently offer hierarchical
structures for information organization. Such structures are not flexible enough
to meet the user requirements (see section 3.1). Consequently, users feel that
organizing information is a heavyweight cognitive activity. This inflexibility also
complicates information retrieval, as the context of documents can only be
maintained in a limited way. Despite their disadvantages, hierarchical tree structures
are computationally efficient and hence deliver good performance.</p>
        <p>The Semantic Desktop views information, regardless of its type, as a Web
resource. This view allows flexible information organization and easy retrieval.
This approach promotes a contextually rich PIM environment where metadata
is described using RDF and ontologies, which support interoperability 4 among
applications and with other systems. Proactive agents can be used to deal with
information overload. The Semantic Desktop, however, is complex, and therefore
should minimize the user’s cognitive load so that it is usable by average users.
6</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Social Aspects of Knowledge Communities</title>
      <p>We have reviewed practices, problems, and approaches in information
management from individual users’ point of view. While this review is useful for
developing a PIM tool, to build successful knowledge communities, we should also
consider social aspects of communities. What is the role of social networks in
information and knowledge management? How can we use social networks to
develop a better infrastructure for knowledge management? How can users be
motivated to participate and contribute to their communities? These issues are
discussed in this section.
6.1</p>
      <sec id="sec-7-1">
        <title>The Role of Social Networks</title>
        <p>
          Social networks [
          <xref ref-type="bibr" rid="ref44">44</xref>
          ] study relationships and information flows among people,
and play an important role in information and knowledge management. People
set a high priority to messages that they receive from families, bosses, or closed
friends. They prefer to collaborate with their trusted friends. And they are more
willing to share their knowledge in an environment where they feel accepted and
secured—safe to speak up their minds, safe to make mistakes, and so on. In other
words, trust and interpersonal relationships are important. It is not surprising
that people make considerable efforts in maintaining and expanding their social
networks [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
        </p>
        <p>
          Informal conversations, which usually happen in office lounges or other
recreational places, have potential for building trust and relationships [
          <xref ref-type="bibr" rid="ref45">45</xref>
          ]. In such
relaxing places, people can talk informally about work or personal things while
developing relationships with other co-workers. In computer systems, such
informal conversations can be supported by chat applications [
          <xref ref-type="bibr" rid="ref45 ref46">45, 46</xref>
          ].
        </p>
        <p>
          The main activities in maintaining social networks include remembering and
communicating [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. Remembering people’s expertise is necessary for locating the
right resources. Remembering personal details enables people to give a personal
touch to their relationships, for example, by sending birthday or anniversary
cards. To facilitate remembering, people maintain intermittent communications,
especially with members of their social networks who are currently inactive, such
as with collaborators from past projects. Communication is helpful to refresh
memories of both parties and to maintain connections between them.
        </p>
        <sec id="sec-7-1-1">
          <title>4 Achieving large scale interoperability, however, is a non-trivial task.</title>
          <p>
            6.2
Communities need a critical mass of users. Not only the number of users is
crucial, but also their participation in the communities. Without a critical mass,
the systems underlying communities will be abandoned by the users [
            <xref ref-type="bibr" rid="ref47 ref48">47, 48</xref>
            ].
          </p>
          <p>Every person has a personal goal and motivation to join and participate in a
knowledge sharing community. Some may want to meet new people with similar
interests while others want to learn and follow the development of a research
area. Although individual goals may vary, members of a community usually
share a common interest to some degree. In general, people will stay active in
a community if by doing so they can achieve their goals. Despite the variety
of individual goals and motivation, how can we motivate users to participate
actively in their communities?</p>
          <p>
            Giving rewards to active users is a common approach to increasing user
participation in online communities. Rewards can be in various forms, including
getting better services, more privileges, or a higher status or visibility in the
community [
            <xref ref-type="bibr" rid="ref48">48</xref>
            ].
          </p>
          <p>
            Because one’s behaviour is usually influenced by others, another approach
to motivating users is by promoting social awareness within a community [
            <xref ref-type="bibr" rid="ref47 ref49">47,
49</xref>
            ]. The basic idea is to give information about the structure and activities in a
community. Examples include displaying a list of online users, giving notifications
about some events, and visualizing the users’ reputation and social networks. By
knowing that there are activities in their community, users are expected to stay
active in it (i.e., to keep using the system). Furthermore, knowing the “presence”
of others can give a good feeling to users [
            <xref ref-type="bibr" rid="ref46">46</xref>
            ]. Social awareness can also serve
as social control [
            <xref ref-type="bibr" rid="ref50">50</xref>
            ] because when users realize that others know about their
activities or behaviour, they will likely behave according to social norms.
6.3
          </p>
        </sec>
      </sec>
      <sec id="sec-7-2">
        <title>Communities of Practice</title>
        <p>
          In practice, the most effective ways of creating and communicating knowledge
are not through written documents, but through personal interactions, including
informal conversation, storytelling, and dialogue [
          <xref ref-type="bibr" rid="ref45 ref51">45, 51</xref>
          ]. Personal interactions
are important because knowledge is not an isolated entity: knowledge is a
concrete form of what is in a person’s mind, and how others perceive it [
          <xref ref-type="bibr" rid="ref51">51</xref>
          ]. Thus,
knowledge exchange processes involve both knowledge creators and users. When
reading a document, readers can only rely on their perception. They cannot
validate whether they have understood the document correctly. Interactions with
the author can reduce this problem, as readers can argue, ask questions, or
validate their understanding with the author. At the same time, the author can
assess readers’ interest and understanding by looking at their gestures or asking
for feedback.
        </p>
        <p>
          Because of the nature of knowledge exchange processes, people use knowledge
databases not only to find specific information, but also to interact with people
who produce or use the information [
          <xref ref-type="bibr" rid="ref50">50</xref>
          ]. For example, to increase the chance
of getting a project proposal approved, it is very helpful to read examples of
successful proposals and to talk with the authors. The authors can give many
insights that are not available in the proposals, or help introduce key persons as
potential referees. Thus, in addition to storing information, knowledge databases
should help users maintain and expand their social networks [
          <xref ref-type="bibr" rid="ref49">49</xref>
          ].
7
        </p>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>Concluding Remarks</title>
      <p>To design a collaboration infrastructure, we should consider both its technical
and social aspects. Technologies are a prerequisite for implementing such
infrastructures. However, whether users will adopt and use an infrastructure often
depends on design subtleties, such as how well the design fits the existing user
practices. While we cannot control the dynamics of communities, we can
support them by designing an infrastructure that fosters characteristics of successful
communities.</p>
      <p>In this paper, we focused mainly on personal information management and
proposed design criteria for Semantic Desktop systems. However, we also brought
social issues in knowledge management to the discussion, as these factors are
crucial in the success of communities.</p>
      <p>Acknowledgments. We thank Joyce Boedianto, Jeff Smith, and Yao Wang for
giving comments and suggestions on drafts of this paper. The development of
design criteria for Semantic Desktop systems is based on a suggestion from an
anonymous reviewer.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Kollock</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Design principles for online communities</article-title>
          .
          <source>In: Harvard conf. on the Internet and society</source>
          . (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Davies</surname>
          </string-name>
          , J.:
          <article-title>Supporting virtual communities of practice. Industrial Knowledge Management (</article-title>
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Frank</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The networked semantic desktop</article-title>
          . In: Workshop on application design,
          <article-title>development and implementation issues in the semantic web</article-title>
          . (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lassila</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>The semantic web</article-title>
          .
          <source>Scientific American</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Huynh</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karger</surname>
            ,
            <given-names>D.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Quan</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Haystack: a platform for creating, organizing and visualizing information using RDF</article-title>
          . In: Semantic Web Workshop. (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Sauermann</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>The gnowsis semantic desktop for information integration</article-title>
          .
          <source>In: 1st Workshop on Intelligent office appliances.</source>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Schmitz</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Towards self-organizing communities in peer-to-peer knowledge management</article-title>
          . In: Workshop on Ontologies in
          <article-title>peer-to-peer communities</article-title>
          . (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Malone</surname>
          </string-name>
          , T.W.:
          <article-title>How do people organize their desks? Implications for the design of office information systems</article-title>
          .
          <source>ACM Trans. Inf. Syst</source>
          .
          <volume>1</volume>
          (
          <year>1983</year>
          )
          <fpage>99</fpage>
          -
          <lpage>112</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Barreau</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>B.A.</given-names>
          </string-name>
          :
          <article-title>Finding and reminding: file organization from the desktop</article-title>
          .
          <source>SIGCHI Bull</source>
          .
          <volume>27</volume>
          (
          <year>1995</year>
          )
          <fpage>39</fpage>
          -
          <lpage>43</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Mander</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Salomon</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wong</surname>
            ,
            <given-names>Y.Y.</given-names>
          </string-name>
          :
          <article-title>A 'pile' metaphor for supporting casual organization of information</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>1992</year>
          )
          <fpage>627</fpage>
          -
          <lpage>634</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Ravasio</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Sch¨ar,
          <string-name>
            <given-names>S.G.</given-names>
            ,
            <surname>Krueger</surname>
          </string-name>
          , H.:
          <article-title>In pursuit of desktop evolution: user problems and practices with modern desktop systems</article-title>
          .
          <source>ACM Trans. Comput.-Hum. Interact</source>
          .
          <volume>11</volume>
          (
          <year>2004</year>
          )
          <fpage>156</fpage>
          -
          <lpage>180</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Boardman</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sasse</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>“Stuff goes into the computer and doesn't come out”: a cross-tool study of personal information management</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>2004</year>
          )
          <fpage>583</fpage>
          -
          <lpage>590</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Abrams</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baecker</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chignell</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Information archiving with bookmarks: personal web space construction and organization</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>1998</year>
          )
          <fpage>41</fpage>
          -
          <lpage>48</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Whittaker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sidner</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Email overload: exploring personal information management of email</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>1996</year>
          )
          <fpage>276</fpage>
          -
          <lpage>283</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Kidd</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The marks are on the knowledge worker</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>1994</year>
          )
          <fpage>186</fpage>
          -
          <lpage>191</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Kwasnik</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>How a personal document's intended use or purpose affects its classification in an office</article-title>
          .
          <source>In: Proc. 12th ACM SIGIR conf. on Research and development in information retrieval.</source>
          (
          <year>1989</year>
          )
          <fpage>207</fpage>
          -
          <lpage>210</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Rodden</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wood</surname>
            ,
            <given-names>K.R.</given-names>
          </string-name>
          :
          <article-title>How do people manage their digital photographs?</article-title>
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>2003</year>
          )
          <fpage>409</fpage>
          -
          <lpage>416</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Lansdale</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The psychology of personal information management</article-title>
          .
          <source>Applied Ergonomics</source>
          <volume>19</volume>
          (
          <year>1988</year>
          )
          <fpage>55</fpage>
          -
          <lpage>66</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Chase</surname>
            ,
            <given-names>W.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Simon</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          :
          <article-title>Perception in chess</article-title>
          .
          <source>Cognitive Psychology</source>
          (
          <year>1973</year>
          )
          <fpage>55</fpage>
          -
          <lpage>81</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Bondarenko</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janssen</surname>
          </string-name>
          , R.:
          <article-title>Documents at hand: learning from paper to improve digital technologies</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>2005</year>
          )
          <fpage>121</fpage>
          -
          <lpage>130</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Whittaker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hirschberg</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The character, value, and management of personal paper archives</article-title>
          .
          <source>ACM Trans. Comput.-Hum. Interact</source>
          .
          <volume>8</volume>
          (
          <year>2001</year>
          )
          <fpage>150</fpage>
          -
          <lpage>170</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>B.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whittaker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schwarz</surname>
          </string-name>
          , H.:
          <article-title>Networkers and their activity in intensional networks</article-title>
          .
          <source>Computer Supported Cooperative Work</source>
          <volume>11</volume>
          (
          <year>2002</year>
          )
          <fpage>205</fpage>
          -
          <lpage>242</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Whittaker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Creech</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Terveen</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Isaacs</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hainsworth</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>ContactMap: organizing communication in a social desktop</article-title>
          .
          <source>ACM Trans. Comput.-Hum. Interact</source>
          .
          <volume>11</volume>
          (
          <year>2004</year>
          )
          <fpage>445</fpage>
          -
          <lpage>471</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Bellotti</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ducheneaut</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Howard</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Taking email to task: the design and evaluation of a task management centered email tool</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>2003</year>
          )
          <fpage>345</fpage>
          -
          <lpage>352</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Furnas</surname>
            ,
            <given-names>G.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Landauer</surname>
            ,
            <given-names>T.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez</surname>
            ,
            <given-names>L.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dumais</surname>
          </string-name>
          , S.T.:
          <article-title>The vocabulary problem in human-system communication</article-title>
          .
          <source>Commun. ACM</source>
          <volume>30</volume>
          (
          <year>1987</year>
          )
          <fpage>964</fpage>
          -
          <lpage>971</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Simone</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mark</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giubbilei</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Interoperability as a means of articulation work</article-title>
          .
          <source>In: Proc. conf. on Work activities coord. and collaboration</source>
          . (
          <year>1999</year>
          )
          <fpage>39</fpage>
          -
          <lpage>48</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Dourish</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lamping</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodden</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Building bridges: customisation and mutual intelligibility in shared category management</article-title>
          .
          <source>In: Proc. intl. ACM SIGGROUP conf. on Supporting group work.</source>
          (
          <year>1999</year>
          )
          <fpage>11</fpage>
          -
          <lpage>20</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28. Berlin,
          <string-name>
            <given-names>L.M.</given-names>
            ,
            <surname>Jeffries</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O</given-names>
            <surname>'Day</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.L.</given-names>
            ,
            <surname>Paepcke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Wharton</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          :
          <article-title>Where did you put it? Issues in the design and use of a group memory</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>1993</year>
          )
          <fpage>23</fpage>
          -
          <lpage>30</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Gifford</surname>
            ,
            <given-names>D.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jouvelot</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sheldon</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>O'Toole</surname>
            ,
            <given-names>J.W.</given-names>
          </string-name>
          :
          <article-title>Semantic file systems</article-title>
          .
          <source>In: Proc. 13th ACM symp. on Operating systems principles. (</source>
          <year>1991</year>
          )
          <fpage>16</fpage>
          -
          <lpage>25</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Gopal</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Manber</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Integrating content-based access mechanisms with hierarchical file systems</article-title>
          .
          <source>In: Proc. 3rd symp. on Operating systems design and implementation</source>
          . (
          <year>1999</year>
          )
          <fpage>265</fpage>
          -
          <lpage>278</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Dourish</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edwards</surname>
            ,
            <given-names>W.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>LaMarca</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Salisbury</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Presto: an experimental architecture for fluid interactive document spaces</article-title>
          .
          <source>ACM Trans. Comput.-Hum. Interact</source>
          .
          <volume>6</volume>
          (
          <year>1999</year>
          )
          <fpage>133</fpage>
          -
          <lpage>161</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Bowman</surname>
            ,
            <given-names>C.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dharap</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baruah</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Camargo</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Potti</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>A file system for information management</article-title>
          .
          <source>In: Proc. ISMM intl. conf. on Intelligent information management systems</source>
          . (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Adar</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kargar</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stein</surname>
            ,
            <given-names>L.A.</given-names>
          </string-name>
          :
          <article-title>Haystack: per-user information environments</article-title>
          .
          <source>In: Proc. 8th intl. conf. on Information and knowledge management</source>
          . (
          <year>1999</year>
          )
          <fpage>413</fpage>
          -
          <lpage>422</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          34.
          <string-name>
            <surname>Dourish</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edwards</surname>
            ,
            <given-names>W.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>LaMarca</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lamping</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petersen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Salisbury</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Terry</surname>
            ,
            <given-names>D.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Thornton</surname>
          </string-name>
          , J.:
          <article-title>Extending document management systems with user-specific active properties</article-title>
          .
          <source>ACM Trans. Inf. Syst</source>
          .
          <volume>18</volume>
          (
          <year>2000</year>
          )
          <fpage>140</fpage>
          -
          <lpage>170</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          35.
          <string-name>
            <surname>Hopkins</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vassileva</surname>
          </string-name>
          , J.:
          <article-title>Beyond keywords and hierarchies</article-title>
          .
          <source>Journal of Digital Information Management</source>
          <volume>3</volume>
          (
          <year>2005</year>
          )
          <fpage>139</fpage>
          -
          <lpage>145</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          36.
          <string-name>
            <surname>Karger</surname>
            ,
            <given-names>D.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Quan</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Collections: flexible, essential tools for information management</article-title>
          .
          <source>In: CHI '04 extended abstracts</source>
          . (
          <year>2004</year>
          )
          <fpage>1159</fpage>
          -
          <lpage>1162</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          37.
          <string-name>
            <surname>Dumais</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cutrell</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cadiz</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jancke</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sarin</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Robbins</surname>
            ,
            <given-names>D.C.</given-names>
          </string-name>
          :
          <article-title>Stuff I've seen: a system for personal information retrieval and re-use</article-title>
          .
          <source>In: Proc. 26th ACM SIGIR conf. on Research and development in information retrieval.</source>
          (
          <year>2003</year>
          )
          <fpage>72</fpage>
          -
          <lpage>79</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          38.
          <string-name>
            <surname>Freeman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gelernter</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Lifestreams: a storage model for personal data</article-title>
          .
          <source>SIGMOD Rec</source>
          .
          <volume>25</volume>
          (
          <year>1996</year>
          )
          <fpage>80</fpage>
          -
          <lpage>86</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          39.
          <string-name>
            <surname>Rekimoto</surname>
          </string-name>
          , J.:
          <article-title>Time-machine computing: a time-centric approach for the information environment</article-title>
          .
          <source>In: Proc. 12th annual ACM symp. on User interface software and technology.</source>
          (
          <year>1999</year>
          )
          <fpage>45</fpage>
          -
          <lpage>54</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          40.
          <string-name>
            <surname>Gruber</surname>
            ,
            <given-names>T.R.</given-names>
          </string-name>
          :
          <article-title>Toward principles for the design of ontologies used for knowledge sharing</article-title>
          .
          <source>Int. J. Hum.-Comput. Stud</source>
          .
          <volume>43</volume>
          (
          <year>1995</year>
          )
          <fpage>907</fpage>
          -
          <lpage>928</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          41.
          <string-name>
            <surname>Soules</surname>
            ,
            <given-names>C.A.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ganger</surname>
            ,
            <given-names>G.R.</given-names>
          </string-name>
          :
          <article-title>Why can't I find my files? New methods for automating attribute assignment</article-title>
          .
          <source>In: Proc. 9th Workshop on Hot topics in operating systems</source>
          . (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          42.
          <string-name>
            <surname>Gemmell</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bell</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lueder</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Drucker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wong</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>MyLifeBits: fulfilling the memex vision</article-title>
          .
          <source>In: Proc. 10th ACM intl. conf. on Multimedia</source>
          , New York, NY, USA, ACM Press (
          <year>2002</year>
          )
          <fpage>235</fpage>
          -
          <lpage>238</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref43">
        <mixed-citation>
          43.
          <string-name>
            <surname>Fisher</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dourish</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Social and temporal structures in everyday collaboration</article-title>
          .
          <source>In: Proc. conf. on Hum. factors in comp. sys.</source>
          (
          <year>2004</year>
          )
          <fpage>551</fpage>
          -
          <lpage>558</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref44">
        <mixed-citation>
          44.
          <string-name>
            <surname>Garton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haythornthwaite</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wellman</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Studying online social networks</article-title>
          .
          <source>Doing Internet Research</source>
          (
          <year>1999</year>
          )
          <fpage>75</fpage>
          -
          <lpage>105</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref45">
        <mixed-citation>
          45.
          <string-name>
            <surname>Thomas</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kellogg</surname>
            ,
            <given-names>W.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Erickson</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The knowledge management puzzle: human and social factors in knowledge management</article-title>
          .
          <source>IBM Systems Journal</source>
          <volume>40</volume>
          (
          <year>2001</year>
          )
          <fpage>863</fpage>
          -
          <lpage>884</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref46">
        <mixed-citation>
          46.
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>B.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whittaker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bradner</surname>
          </string-name>
          , E.:
          <article-title>Interaction and outeraction: instant messaging in action</article-title>
          .
          <source>In: Proc. ACM conf. on CSCW</source>
          . (
          <year>2000</year>
          )
          <fpage>79</fpage>
          -
          <lpage>88</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref47">
        <mixed-citation>
          47.
          <string-name>
            <surname>Ackerman</surname>
            ,
            <given-names>M.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Starr</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Social activity indicators: interface components for cscw systems</article-title>
          .
          <source>In: Proc. 8th annual ACM symp. on User interface and software technology.</source>
          (
          <year>1995</year>
          )
          <fpage>159</fpage>
          -
          <lpage>168</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref48">
        <mixed-citation>
          48. Cheng, R.,
          <string-name>
            <surname>Vassileva</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>User motivation and persuasion strategy for peer-to-peer communities</article-title>
          .
          <source>In: Proc. 38th Hawaii intl. conf. on System sciences. (</source>
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref49">
        <mixed-citation>
          49.
          <string-name>
            <surname>Bush</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tiwana</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Designing sticky knowledge networks</article-title>
          .
          <source>Commun. ACM</source>
          <volume>48</volume>
          (
          <year>2005</year>
          )
          <fpage>66</fpage>
          -
          <lpage>71</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref50">
        <mixed-citation>
          50.
          <string-name>
            <surname>Erickson</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kellogg</surname>
            ,
            <given-names>W.A.</given-names>
          </string-name>
          :
          <article-title>Social translucence: an approach to designing systems that support social processes</article-title>
          .
          <source>ACM Trans. Comput.-Hum. Interact</source>
          .
          <volume>7</volume>
          (
          <year>2000</year>
          )
          <fpage>59</fpage>
          -
          <lpage>83</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref51">
        <mixed-citation>
          51.
          <string-name>
            <surname>Walsham</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Knowledge management: The benefits and limitations of computer systems</article-title>
          .
          <source>European Management Journal</source>
          <volume>19</volume>
          (
          <year>2001</year>
          )
          <fpage>599</fpage>
          -
          <lpage>608</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>