<!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>
      <journal-title-group>
        <journal-title>Feb</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>An Ontology-based Visual Interface for Browsing and Summarizing Conversations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shama Rashid</string-name>
          <email>shama@cs.ubc.ca</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Giuseppe Carenini</string-name>
          <email>carenini@cs.ubc.ca</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of British Columbia</institution>
          ,
          <addr-line>Vancouver, BC</addr-line>
          ,
          <country country="CA">Canada</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <volume>13</volume>
      <issue>2011</issue>
      <abstract>
        <p>In this paper we present a visual interactive interface to create focused summaries of human conversations via mapping to the concepts within an ontology. The ontology includes nodes for the conversation participants, for Dialog Act (DA) properties such as decision, action-item or subjectivity, as well as for entities mentioned in the conversation. The classifiers used to annotate conversation data with DA property and entity tags can be applied to any conversational modality including face to face meetings, emails, blogs and chats. Our interface allows the user to explore these conversations and identify informative sentences by their association with nodes of interest on the tree-structured visual representation of the ontology. The sentences thus selected by the user as potentially important components of the summary can then be used to derive a brief and focused overview of the conversation. The display interface and data parsing components in the initial prototype were all developed based on Java frameworks and toolkits.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>INTRODUCTION
Multimodal conversations have become an integrated part
of our everyday communication with others. We email for
business and personal purposes, attend meetings in person
and remotely, chat online, and participate in blog or forum
discussions. It is clear that automatic summarization can be
of benefit in dealing with this overwhelming amount of
interactional information. Automatic meeting abstracts would
allow us to prepare for an upcoming meeting or review the
decisions of a previous group. Email summaries would aid
corporate memory and provide efficient indices into large
mail folders. Summaries of technical blogs could become an
important support platform for developers, administrators,
and technology enthusiasts in general.</p>
      <p>
        Summarization of human conversations have been addressed
in the past for different modes of conversation, including
meetings [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], emails [
        <xref ref-type="bibr" rid="ref23 ref3">23, 3</xref>
        ], telephone conversations [
        <xref ref-type="bibr" rid="ref32">32</xref>
        ]
and internet relay chats [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ]. In all these previous works
the dominant approach to summarization has been
extractive, which means that the summary is generated by
selecting and concatenating the most informative sentences from
the source document(s). Extractive summarization has been
popular at least in part because it can be framed as a binary
classification task that lends itself well to machine learning
techniques, and does not require a natural language
generation component. Extrinsic evaluations have also shown
that, while extractive summaries may be less coherent than
human abstracts, users still find them to be valuable tools
for browsing documents [
        <xref ref-type="bibr" rid="ref15 ref19 ref9">9, 15, 19</xref>
        ]. However, these same
evaluations also indicate that concise abstracts are generally
preferred by users and lead to higher objective task scores.
The limitation of a cut-and-paste summary is that the
endusers do not know why the selected sentences are important;
this can often only be discerned by exploring the context in
which each sentence originally appeared. One possible
improvement is to create structured summaries that represent
an increased level of abstraction, where selected sentences
are grouped according to the entities they mention as well
as to phenomena such as decisions, action items and
subjectivity, thereby giving the users more information on why
the sentences are being selected. For example, the sentence
Let’s go with a simple layout is about a simple layout and
represents both a decision and the expression of a positive
subjective statement.
      </p>
      <p>
        Our first attempt to build an interface to create visual
structured summaries of conversations was presented in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. This
interface relied on mapping the utterances of the
conversation into an ontology, similar to the faceted browsers in [
        <xref ref-type="bibr" rid="ref30 ref6">30,
6</xref>
        ], that then could be used to search the conversation
according to the annotation. Our ontology initially contained
only the participants of the conversation and properties of
the utterance such as whether it was expressing a decision,
a subjective statement, etc. Our first prototype comprised
two panels (see Fig 1). The right panel displayed the
ontology, while the left panel displayed the whole conversation,
where sentences are temporally ordered. Given the
information shown in the two panels, the users could generate
visual, structured summaries by selecting nodes in the
ontology. As a result, the sentences that were mapped in the
selected nodes would be highlighted.
      </p>
      <p>
        In this paper we present a novel interface (see Fig 2) that
addresses several limitations of our initial prototype. First,
we have extended the ontology to also include entities
mentioned in the conversation. Searching the conversation
using a particular keyword is suitable only when users already
have an idea about the content and want additional
information on a particular entity. Our assumption is that
representing entities on the ontology tree will not only enable
the users to perform a more refined search and browsing of
the conversation, but the entities would also provide them
with a quick overview of the content of the whole
conversation. Secondly, we have provided a satisfactory solution to
the problem of highlighting the sentences mapped to nodes
selected by the users in the ontology. Instead of using color
(a non-scalable solution that we initially explored) we have
added a column to the left of the interface layout, in which
the (selected) mapping to the (knowledge concepts within)
ontology of the corresponding utterance can be displayed.
The third extension, the summary view (discussed in
details at Display Design section), is the most critical one, as
it opens the door to a possibly highly beneficial integration
of structured visual (extractive) summaries and abstractive
focused summaries. Our hypothesis is that the users, after
they have inspected the conversation through the mapping to
the ontology, may wish to generate summaries covering only
some aspects of the conversation (which are especially
relevant to their current information needs). For instance, users
may need a summary of all the positive and negative
comments that were expressed in the conversation about two
particular entities (e.g., new design and interface layout). The
new interface allows the users to trigger the generation of
such summaries, which will be shown in the bottom panel
(see Fig 2). Most importantly, these summaries can be
generated either by extraction or by abstraction; in the latter case
by applying techniques presented in [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>
        We have developed our prototype using instances of
meeting conversations from the AMI corpus [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. We are
currently extending the interface to Web-based modes of
conversation like emails, blogs, chats etc. and working on this
with the BC3 corpus [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ]. As we move to asynchronous
conversations, one additional complication is that the
conversational structure is not linear anymore, but can be a tree
or a graph. We are currently exploring how the interface
can be extended to deal with more complex conversational
structures. In contrast, the mapping of sentences to the
ontology can be easily transfered from meetings to other
conversational modes, as it relies on very general methods. The
mapping is performed by first identifying all the entities
referred to in the conversation (via syntactic parsing), and then
by utilizing classifiers relating to a variety of sentence-level
phenomena such as decisions and subjective sentences. High
classification accuracy is achieved by using a very large
feature set integrating conversation structure, lexical patterns,
part-of-speech (POS) tags and character n-grams.
      </p>
      <p>
        In this paper we will first describe related work. Then we
will present the process of deriving an ontology and
mapping sentences to it. After that, we shall discuss our
interface to display the conversation to the users for interactive
exploration of the data with the help of the ontology.
RELATED WORK
In HCI and NLP different approaches have been proposed to
support the browsing and summarization of data/documents
with the aid of an interactive interface. Here, we focus on the
ones that are more critical for our current and future work.
The idea of using an ontology to explore data in an orderly
manner is not novel. For instance, the Flamenco [
        <xref ref-type="bibr" rid="ref30">30</xref>
        ] and the
Mambo [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] systems make use of hierarchical faceted
metadata for browsing through image or music collections. In
our approach we adopt similar techniques to support the
exploration of conversations. More specifically, in Flamenco
[
        <xref ref-type="bibr" rid="ref30">30</xref>
        ], while navigating an image collection along conceptual
dimensions or facets (e.g. date, theme, artist, media, size,
color, material etc.), every facet hyperlink that can be
selected to derive a new result set is displayed with a count as
an indicator of the number of results to expect i.e. the count
works as a query preview. Similarly, we have included a
count beside each node of the ontology to indicate the
number of sentences in the conversation that have been mapped
to it. Another idea we have borrowed from the Flamenco
and Mambo systems is to use summary paths to simplify
the user interaction with the ontology. In Flamenco,
different paths may lead to a collection of images at a particular
time; so Flamenco uses a summary path along the top of
the interface to show exactly which path was taken and uses
links along this path to retract to a previous decision along
the path. Similarly, the Mambo system provides breadcrumb
style filter history, which gives an interactive overview of the
active facet filter. In our interface, to facilitate the inspection
of a possibly large ontology, nodes can be minimized (i.e.,
their children are hidden). So, it may happen that the set of
tags selected by the users is not fully visible. To address this
problem, we are working on including a summary of the
ontology node selection at the top of our interface, as it is done
in Flamenco and Mambo.
      </p>
      <p>
        An extractive approach for generating a decision-focused
summary suitable for debriefing tasks has been proposed in
[
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. This type of summary includes only 1-2% of a
meeting recording related to decision making. In addition to the
transcripts, the interface takes advantage of the audio-video
recordings to better understand decision points. While the
interface in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] makes use of only dialog acts for focused
summary generation, ours additionally uses speaker and
entity information. Furthermore, we are not limited to
extractive techniques as we are also exploring focused
summarization by abstraction. The interface proposed in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] also
considers features that are specific to conversations about
designing a new product (see AMI corpus [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]), in which you
typically do not have only a single meeting but a series of
meetings, the kickoff, the conceptual design, the detailed
design, and the evaluation meetings. While we also aim to
consider series of related conversation we intend to do it in
a general way, i.e., not being limited to conversations about
designing a product.
      </p>
      <p>
        The Ferret Meeting Browser [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ] provides the ability to quickly
find and play back a combination of available audio, video,
transcript and projected display segments from a meeting
side by side for comparison and inspection synchronously
and allows navigation by clicking on a vertical scrollable
timeline of the transcript. Users can zoom into particular
places of interest by means of a button and by zooming out
they get an overview of the meeting in terms of who talked
the most, what meeting actions etc. In the future, we’ll
extend our interface to include an overview of the conversation
integrating ideas from the following projects.
      </p>
      <p>
        The Meeting Miner [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] aids browsing multimodal meeting
through recordings of online text and speech collaborative
meetings using timeline navigators of content of edits as the
main control for browsing. In addition, it can retrieve a set
of speech turns spread throughout the conversation focused
on particular keywords that can be selected from a list of
automatically generated keywords and topic. The users can
also navigate to the audio segments that have been identified
as relevant using the audio timeline for random access of the
file. The Meeting Miner [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] automatically identifies a set of
potential keywords and the users can decide to view these
in alphabetical order, ranked by term frequency or simply
by time of appearance in the conversation. A similar
concept has been discussed in the future work of FacetMap [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ]
where the authors mention implementing the ability to
dynamically order the facets, such as by count, alphabetically
by label, by usage, or by some specific facet ordering. The
entities on the ontology tree of our interface are equivalent to
Meeting Miner’s keyword panel entries and we are currently
listing the entities in alphabetical order; but a different
ordering based on the count etc. may prove more helpful to
the users.
      </p>
      <p>
        The CALO meeting assistant [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ] is used for capturing audio
signals and optional handwriting recorded by digital pens
for distributed meetings. During the meeting the system
automatically transcribes the speech to text and the
participants are fed back a real-time transcript to which
annotations can be attached. At the end of the meeting the system
performs further semantic analysis on the transcript like
dialog act segmentation and tagging, topic identification and
segmentation, question-answer pair identification, addressee
detection, action item recognition, decision extraction and
summarization. The result of this analysis is made available
via a web-based interface. The off-line meeting browser
interface displays the meeting transcript segmented according
to dialog acts. Each dialog act is shown along side its start
time, speaker, and a link for streaming audio feedback for the
transcript segment (in case the users want to overcome any
speech transcription errors). The CALO browser also
provides the users views of the extractive summary of the
meeting and above mentioned annotations in separate tabs. A lot
of the annotations provided by the CALO system overlap
with our segmentation of the transcript and knowledge
concepts represented in the ontology tree but the CALO browser
provides more flexibility by providing the users means to
attach their own annotations, which is an interesting direction
we could explore in our future prototypes. Our interface
differs from CALO by providing a way to focus on the users’
particular information need by referring to the ontology and
by providing an option to generate abstractive or extractive
summaries.
      </p>
      <p>
        In iBlogVis [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], the authors use social interaction cues like
comment length, number of comments, regular commenters
etc. and content cues like topics of a blog, blogger’s
posting habits etc. to provide the users with an overview of a
blog archive and to support them in deciding which entry to
read. The font size of a tag for blog topic representation
indicates its popularity, a concept that we shall employ in the
future for our textual collage representation of conversation
content. iBlogVis uses the idea of read wear [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], a means
of graphically portraying the documents readership history,
to help users keep track of entries that have been read, have
not been read, or the one that is currently being read using
different colors. Similarly, we are currently working to
provide users an option to log the current ontology settings so
that they can keep track of the combinations tried before.
MostVis [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ] uses a multiple co-ordinated view for
browsing a catalog for multimedia components in a car. Besides
the textual label of each node in the catalog node-link tree
representation there is an additional icon representing
element type (car series, function block, functions, parameters
etc.). This is similar to our use of a short string
representation or icon beside the ontology tree nodes. MostVis also
has a history window with undo and redo button where an
entry is logged every time an expansion or minimization of
the node-link tree occurs. We are exploring how a similar
mechanism could be added to our interface.
      </p>
      <p>MAPPING SENTENCES TO ONTOLOGY
Our summarization method relies on mapping the sentences
in a conversation to an ontology written in OWL/RDF (Web
Ontology Language/Resource Description Framework), a
widely used open-source standard develop tool compatible with
the architecture of the Semantic Web in particular.
Our ontology contains three core upper-level classes:
Participant, Dialog Act (DA) types and Entities. When
additional information is available about participant roles in a
given domain, Participant subclasses can be utilized. For
our AMI meeting scenarios the Participant class consisted
of four subclasses ProjectManager (PM), IndustrialDesigner
(ID), UserInterfaceExpert (UIE) and MarketingExpert (ME).
The DA-Type class, on the other hand, contains subclasses
decisions, actions, problems, positive subjective sentences,
and negative subjective sentences.1 The entities in a
conversation are noun phrases with mid-range document frequency.
Our ontology is populated with the instance data for a given
conversation that the user is attempting to browse and
summarize.</p>
      <p>
        Our definition of entities is similar to the definition of
concept as defined by Xie et al. [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ], where n-grams are weighted
by tf.idf scores, except that we use noun phrases rather than
any n-grams. We use mid-range document frequency instead
of idf as in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], where the entities occur in between 10% and
90% of the documents in the collection. We do not currently
attempt coreference resolution for entities; recent work has
investigated coreference resolution for multi-party dialogues
[
        <xref ref-type="bibr" rid="ref16 ref8">16, 8</xref>
        ], but the challenge of resolution on such noisy data is
highlighted by low accuracy (e.g. F-measure of 21.21)
compared with using well-formed text (e.g. monologues).
Using a number of supervised classifiers trained on labelled
decision sentences, action sentences etc. the sentences in
the conversation were mapped to our ontology. The
classifiers have been evaluated both on meeting and email data,
the AMI [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and BC3 [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ] corpus respectively, as mentioned
in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] and found to perform well on both sets of data. The
flexibility of our mapping approach is that it only relies on
generic conversational features and can therefore be applied
to a multi-modal conversation, for example a conversation
that spans both an email thread and a meeting. We used a
feature set related to generic conversational structure, which
include sentence length, sentence position in the
conversation and in the current turn, pause-style features, lexical
cohesion, centroid scores, and features that measure how terms
cluster between conversation participants and conversation
turns. Despite using generic features the classifiers achieve
similar results to [
        <xref ref-type="bibr" rid="ref11 ref20 ref21 ref22">11, 21, 20, 22</xref>
        ], that rely on
meetingspecific or email-specific features (e.g., prosody for
meetings). Details can be found in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        For AMI corpus, a particular conversation for a meeting
consists of utterances that have the following format:
&lt;Utterance rdf:about="#TS3012a.A.dialog-act.vkaraisk.14"&gt;
&lt;rdf:type rdf:resource="&amp;owl;Thing"/&gt;
&lt;hasSpeaker rdf:resource="#ProjectManager"/&gt;
&lt;hasDAType rdf:resource="#NegativeSubjective"/&gt;
&lt;begTime&gt;21.66&lt;/begTime&gt;
&lt;endTime&gt;22.74&lt;/endTime&gt;
&lt;/Utterance&gt;
The above utterance is a negative subjective statement or a
negative comment made by the ProjectManager at the
meeting. The beginning time of utterance is used to temporally
order the whole conversation and the unique identifier of the
Utterance object is used to match the utterance with the
actual sentence being said and thus any relevant entities.
1Our classifiers are designed for identifying five subclasses of the
DA-type class, namely decisions, actions, problems, positive
subjectives, and negative subjectives; but we could easily include
additional classifiers to identify other types of dialog acts according
to the information need.
DISPLAY DESIGN
Once the ontology is populated with the participants, DA
types and entities of a particular conversation, the transcript
of the conversation is displayed ordered temporally. The
design of the interface is intended to satisfy two key goals. The
first goal is to support the exploration of the conversation
through annotating the discourse with an ontology. This is
achieved by allowing the users to select subclasses from the
ontology that seem promising to fulfill their particular
information needs and by allowing them to inspect the sentences
that are associated to those subclasses in the context of the
whole transcript. The second goal is to support the
generation of focused summaries that cover only aspects of the
conversations which are especially relevant to the users. This is
achieved by allowing the users to select classes of sentences
that they find particularly informative and that should be
included in the summary (include verbatim for an extractive
summary vs. include their content for an abstractive one).
In this section we discuss in more detail how the
achievement of these two key goals is supported by our novel
display, shown in Figure 2. Our visual interface consists of
three integrated views, the Ontology View (right), the
Transcript View (middle) and the Summary View (bottom).
Contrast this with the simpler interface presented in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] (see Fig
1). Our interface does not feature audio-video data streams
in addition to transcripts as in Meeting Miner [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] or Ferret
[
        <xref ref-type="bibr" rid="ref28">28</xref>
        ] because we have designed it to explore and summarize
multi-modal conversations in general. The prototype was
developed using Java Swing components and Jena, an open
source Java framework that provides a programmatic
environment for building semantic web applications.
      </p>
      <p>
        The Ontology View
The ontology view provides a structured way for the users
to explore all the relevant concepts in the conversation and
their relations. It contains a tree hierarchy with core nodes
Speaker, DAType (Dialogue Act Type), and Entity.
Conceptually the top node in the ontology tree represents all the
utterances or sentences in the conversation, while any other
node represents a subset or subclass of those sentences that
satisfies a particular property. For instance, the node
ProjectManager (PM) represent all the sentences uttered by the
PM, while the node ActionItem represents all the utterances
that were classified as containing an action item. The
Entities core node, on the other hand, does not represent all the
noun phrases detected in the conversation but only the ones
deemed important on the basis of their frequency and the
ones that are associated with messages in the conversation.
As shown in Fig. 2, like in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], the nodes each have a check
box and a label. Additionally we have included a count
within parentheses beside the labels. For leaf nodes, the
count indicates how many sentences were mapped to this
node and imply its relevance for the summary; for non-leaf
nodes this is just the sum of all its descendant leaf node
count; a count is an implication of the node’s relevance.
For Speaker subtree nodes the sets are mutually exclusive
and these counts give a sense how dominant a role was in
this particular meeting. For Entity and DAType subtrees, the
sets can be overlapping and the counts at the non-leaf core
nodes indicate the extent of overlap. Our initial prototype
displays the entities in an alphabetical order but we could
use the counts to order the entities on the ontology tree as an
indicator to their relevance.
      </p>
      <p>The Transcript View
The transcript view is designed to allow the users to
inspect the whole conversation as well as the mapping of each
sentence into the ontology. This view has two columns
Transcript and Tags. The Transcript column displays the
whole conversation one sentence per row, while keywords
and icons for the nodes in the ontology to which each
sentence was mapped to are shown in the corresponding Tags
column (to the left of the Transcript column), in case of
selected nodes under the Speaker and DAType core nodes; or
highlighted in the Transcript column, in case of nodes
under Entity core node (refer to the Interaction Design Section
for a user scenario). We have decided to display the entities
highlighted in the transcript instead of mentioning them in
the Tags column so that the users could inspect them in their
actual context. Also, adding a number of long noun phrases
to the Tags column would have widened that particular
column space making it difficult for the users to inspect both
the Tags and Transcript columns at the same time.
The Transcript View is scrollable both vertically and
horizontally which can be used to inspect a sentence in its
context i.e. its position in the conversation. A sentence may
convey additional information in conjunction with its
surrounding sentences. For example, when users inspect the
sentence ‘That’s it, you just put it on the board.’ mentioning
the entity ‘board’ in its context, they may decide to include
the entity ‘pen’ for further investigation since the ‘it’ in the
sentence refers to the ‘pen’ that appeared in a preceding
sentence.</p>
      <p>
        The Summary View
The summary view is a text area where the candidate
summary of the conversation appears for user assessment. The
summary is based on sentences selected from the transcript
using the criteria set from the ontology tree and is generated
using either extraction or abstraction as in [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. The
summary view provides an easier way to assess the conversation
overview on a particular information need without scrolling
through the whole transcript. When the summary is
extractive, to support the users in interpreting the summary in the
context of the whole transcript, each sentence in the
summary view is prefixed with a keyword indicating the speaker
of the sentence. We are currently exploring how to provide
a similar support for abstractive summaries.
      </p>
      <p>INTERACTION DESIGN
The list of entities gives the users an idea of the
conversation content without requiring them to browse the whole
transcript. Furthermore, by selecting a few entities out of
the list the users can satisfy particular information needs on
the direction the conversation took regarding those
particular entities. For instance, a user may be interested in all
the comments made by the ProjectManager on the ‘board’
and whether these comments were positive or negative. To
achieve this goal, the user would select the node ‘board’
under the Entity sub-tree, the node ‘ProjectManager’ under
the Speaker core node and ‘PositiveSubjective’ and
‘NegativeSubjective’ nodes under the DA Type core node. As
shown in figure 2, this would display the keywords ‘PM’,
‘+’ and ‘-’ in the Tags column of sentences that map to each
of these nodes and would also highlight every occurrence of
the word ‘board’, providing the user scope for closer
inspection by scrolling through the transcript.</p>
      <p>When the transcript view is generated for a conversation, the
Tags column is initially empty and all the nodes on the
ontology tree in the ontology view are shown and are de-selected.
If for a particular conversation the ontology is too large, the
users can expand/minimize nodes they are/are-not interested
in, as in any standard outline based interface. Once the users
select a node (or de-selects an already selected node) on the
ontology tree, the keyword or icon associated with that node
appears in (or disappears from) the Tags column of all the
rows that contain sentences that can be mapped to that
particular node. Once the users have selected the nodes of
interest from the ontology tree, they can scroll through the
transcript view and select sentences that appear to be promising
for generating a focused summary. When they choose a
sentence, all sentences that have the exact same tag set
associated are detected and the summary view is updated with
the summary generated based on these sentences. These
sentences are included verbatim for an extractive summary,
while an abstractive summary will summarize their content.
The generated summary is also interactive, for the
extractive case, clicking on a sentence in the summary view
highlights it and also re-focuses the vertical scroll bar position
on the transcript view to show the context of that particular
sentence. For the abstractive case, we are still investigating
ways to provide a similar functionality, which needs to take
into account that there is no one-to-one mapping between
the sentences in the summary and the ones in the transcript.
CONCLUSION AND FUTURE WORK
This paper presents a visual interface that not only allows
users to explore a conversation using a mapping to an
ontology, but also allows them to interactively generate
focused summaries of human conversation. The classifiers for
the mapping phase are not dependent on features specific to
any particular mode of conversation which makes this
approach extensible to multi-modal conversations. We are
currently working to extend our interface to asynchronous
conversations like emails and blogs, which entails the additional
complication of having a non-linear conversational structure
(i.e., a graph). In the future, we plan to investigate
coreference resolution for the noun phrases in the conversation, this
would also deal with synonymy of entities.</p>
      <p>
        Our interface supports the generation of focused summaries
by allowing the users to select classes of sentences that they
find particularly informative and that should be included in
the summary. If these sentences are included verbatim, we
generate extractive summaries, whereas if the content of those
sentences is extracted and aggregated, we generated abstract
summaries. There is evidence that human abstractors at times
use sentences from the source documents nearly verbatim in
their own summaries, justifying this approach to some
extent [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. However, other studies also show that users
usually prefer concise abstracts and find them more coherent[
        <xref ref-type="bibr" rid="ref15 ref19 ref9">9,
15, 19</xref>
        ]. In our interface, we can generate both types of
summaries, so it represents an ideal environment in which
to explore the pros and cons of these two methods and the
possible benefits of their integration.
      </p>
      <p>To assist users to decide on the informativeness of a set of
sentences chosen according to a criteria set on the ontology
tree, in the future we would also provide users with a task
history. Depending on the size of the Entities subtree, it may
be prohibitively time-consuming for the users to recreate a
previously examined criterion by reselecting all of the
relevant nodes since the userw would have to recall and find
the exact nodes selected before and re-select them. A task
history may record such promising criteria so that users can
re-assess them later on using a single selection from this
history view.</p>
      <p>
        Our current prototype only shows a local view of the
conversation, with fewer than fifty sentences. We plan to provide
a second visualization that shows a global view of the entire
conversation and possibly of the entire corpus of
conversations (as in [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]). A possible approach could be to display a
textual collage like tag clouds or word clouds in the overview
window of the list of entities to give users a sense of the
content of the conversation or corpus transcript without
browsing. We could also show the representation of speaker
participation information as a vertical scrollable timeline as in
[
        <xref ref-type="bibr" rid="ref28">28</xref>
        ].
      </p>
      <p>Finally, before engaging in a second redesign exercise, we
plan to run a formative user evaluation of the interface using
objective task scores.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>M.-M. Bouamrane</surname>
            and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Laz</surname>
          </string-name>
          .
          <article-title>Navigating Multimodal Meeting Recordings with the Meeting Miner</article-title>
          .
          <source>In Proc. of FQAS</source>
          , Milan, Italy,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>G.</given-names>
            <surname>Carenini</surname>
          </string-name>
          and
          <string-name>
            <given-names>G.</given-names>
            <surname>Murray</surname>
          </string-name>
          .
          <article-title>Visual Structured Summaries of Human Conversations</article-title>
          .
          <source>In Proc. of IVITA</source>
          <year>2010</year>
          ,
          <article-title>HongKong</article-title>
          , China, pages
          <fpage>41</fpage>
          -
          <lpage>44</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>G.</given-names>
            <surname>Carenini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Ng</surname>
          </string-name>
          , and
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhou</surname>
          </string-name>
          .
          <article-title>Summarizing Email Conversations with Clue Words</article-title>
          .
          <source>In Proc. of ACM WWW</source>
          <year>2007</year>
          , Banff, Canada,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>J.</given-names>
            <surname>Carletta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ashby</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bourban</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Flynn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Guillemot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Hain</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kadlec</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Karaiskos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Kraaij</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kronenthal</surname>
          </string-name>
          , G. Lathoud,
          <string-name>
            <given-names>M.</given-names>
            <surname>Lincoln</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lisowska</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. McCowan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Post</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Reidsma</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Wellner. The AMI Meeting Corpus: A Pre-Announcement</surname>
          </string-name>
          .
          <source>In Proc. of MLMI</source>
          <year>2005</year>
          ,
          <article-title>Edinburgh</article-title>
          , UK, pages
          <fpage>28</fpage>
          -
          <lpage>39</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>K.</given-names>
            <surname>Church</surname>
          </string-name>
          and
          <string-name>
            <given-names>W.</given-names>
            <surname>Gale</surname>
          </string-name>
          .
          <article-title>Inverse Document Frequency IDF: A Measure of Deviation from Poisson</article-title>
          .
          <source>In Proc. of the Third Workshop on Very Large Corpora</source>
          , pages
          <fpage>121</fpage>
          -
          <lpage>130</lpage>
          ,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>R.</given-names>
            <surname>Dachselt</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Frisch</surname>
          </string-name>
          .
          <article-title>Mambo : A Facet-based Zoomable Music Browser</article-title>
          .
          <source>In Proc. of MUM</source>
          , Oulu, Finland,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>M.</given-names>
            <surname>Galley</surname>
          </string-name>
          .
          <article-title>A Skip-Chain Conditional Random Field for Ranking Meeting Utterances by Importance</article-title>
          .
          <source>In Proc. of EMNLP</source>
          <year>2006</year>
          , Sydney, Australia, pages
          <fpage>364</fpage>
          -
          <lpage>372</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>S.</given-names>
            <surname>Gupta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Niekrasz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Purver</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Jurafsky</surname>
          </string-name>
          . Resolving “
          <article-title>You” in Multi-Party Dialog</article-title>
          .
          <source>In Proc. of SIGdial</source>
          <year>2007</year>
          , Antwerp, Belgium,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>L.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Sanocki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gupta</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Grudin</surname>
          </string-name>
          .
          <article-title>Auto-summarization of audio-video presentations</article-title>
          .
          <source>In Proc. of ACM MULTIMEDIA '99</source>
          ,
          <string-name>
            <surname>Orlando</surname>
          </string-name>
          , FL, USA, pages
          <fpage>489</fpage>
          -
          <lpage>498</lpage>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>W. C. Hill</surname>
            ,
            <given-names>J. D.</given-names>
          </string-name>
          <string-name>
            <surname>Hollan</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Wroblewski</surname>
            , and
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>McCandless</surname>
          </string-name>
          .
          <article-title>Edit Wear and Read Wear</article-title>
          .
          <source>In Proc. of SIGCHI</source>
          , Monterey, California, USA,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. P.
          <string-name>
            <surname>-Y. Hsueh</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Kilgour</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Carletta</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Moore</surname>
            , and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Renals</surname>
          </string-name>
          .
          <article-title>Automatic Decision Detection in Meeting Speech</article-title>
          .
          <source>In Proc. of MLMI</source>
          <year>2007</year>
          , Brno, Czech Republic,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. P.-Y. Hsueh and
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Moore</surname>
          </string-name>
          .
          <article-title>Improving Meeting Summarization by Focusing on User Needs : A Task-Oriented Evaluation</article-title>
          .
          <source>In Proc. of IUI</source>
          , Florida, USA,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Indratmo</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Vassileva</surname>
            , and
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Gutwin</surname>
          </string-name>
          .
          <article-title>Exploring Blog Archives with Interactive Visualization</article-title>
          .
          <source>In Proc. of AVI</source>
          , Naples, Italy,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>J. Kupiec</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Pederson</surname>
            , and
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Chen</surname>
          </string-name>
          .
          <article-title>A Trainable Document Summarizer</article-title>
          .
          <source>In Proc. of the 18th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval</source>
          . Seattle, Washington, USA, pages
          <fpage>68</fpage>
          -
          <lpage>73</lpage>
          ,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>K. McKeown</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Hirschberg</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Galley</surname>
            , and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Maskey</surname>
          </string-name>
          . From Text to Speech Summarization.
          <source>In Proc. of ICASSP</source>
          <year>2005</year>
          , Philadelphia, USA, pages
          <fpage>997</fpage>
          -
          <lpage>1000</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>C.</given-names>
            <surname>Muller</surname>
          </string-name>
          . Resolving It,
          <article-title>This and That in Unrestricted Multi-Party Dialog</article-title>
          .
          <source>In Proc. of ACL</source>
          <year>2007</year>
          , Prague, Czech Republic,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. G. Murray and
          <string-name>
            <given-names>G.</given-names>
            <surname>Carenini</surname>
          </string-name>
          .
          <article-title>Interpretation and Transformation for Abstracting Conversations</article-title>
          . In North American ACL, Los Angeles, CA, USA,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. G. Murray, G. Carenini, and
          <string-name>
            <given-names>R.</given-names>
            <surname>Ng</surname>
          </string-name>
          .
          <article-title>Generating Abstracts of Meeting Conversations: A User Study</article-title>
          .
          <source>In Proc. of INLG</source>
          , Dublin, Ireland,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. G. Murray,
          <string-name>
            <given-names>T.</given-names>
            <surname>Kleinbauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Poller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Renals</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Becker</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Kilgour</surname>
          </string-name>
          .
          <article-title>Extrinsic Summarization Evaluation: A Decision Audit Task</article-title>
          .
          <source>In Proc. of MLMI</source>
          <year>2008</year>
          , Utrecht, the Netherlands,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20. G. Murray and
          <string-name>
            <surname>S. Renals.</surname>
          </string-name>
          <article-title>Detecting Action Items in Meetings</article-title>
          .
          <source>In Proc. of MLMI</source>
          <year>2008</year>
          , Utrecht, the Netherlands,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>M. Purver</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Dowding</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Niekrasz</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Ehlen</surname>
            , and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Noorbaloochi</surname>
          </string-name>
          .
          <article-title>Detecting and Summarizing Action Items in Multi-Party Dialogue</article-title>
          .
          <source>In Proc. of the 9th SIGdial Workshop on Discourse and Dialogue</source>
          , Antwerp, Belgium,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <given-names>S.</given-names>
            <surname>Raaijmakers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Truong</surname>
          </string-name>
          , and T. Wilson.
          <article-title>Multimodal Subjectivity Analysis of Multiparty Conversation</article-title>
          .
          <source>In Proc. of EMNLP</source>
          <year>2008</year>
          ,
          <article-title>Honolulu</article-title>
          ,
          <string-name>
            <surname>HI</surname>
          </string-name>
          , USA,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <given-names>O.</given-names>
            <surname>Rambow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Shrestha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chen</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Lauridsen</surname>
          </string-name>
          .
          <article-title>Summarizing Email Threads</article-title>
          .
          <source>In Proc. of HLT-NAACL</source>
          <year>2004</year>
          , Boston, USA,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>M. Sedlmair</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Bernhold</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Herrscher</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Boring</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <surname>A. Butz.</surname>
          </string-name>
          <article-title>MostVis: An Interactive Visualizing Supporting Automotive Engineers in MOST Catalog Exploration</article-title>
          .
          <source>In Proc. of InfoVis09</source>
          , New Jersey, USA,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <given-names>G.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Czerwinski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Meyers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Robbins</surname>
          </string-name>
          , G. Robertson, and
          <string-name>
            <given-names>D. S.</given-names>
            <surname>Tan</surname>
          </string-name>
          .
          <article-title>FacetMap: A Scalable Search and Browse Visualization</article-title>
          .
          <source>In Proc. of InfoVis</source>
          , Baltimore, Maryland, USA,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26. G. Tur,
          <string-name>
            <given-names>A.</given-names>
            <surname>Stolcke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Voss</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Peters</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
            Hakkani-Tr,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Dowding</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Favre</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Fernndez</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Frampton</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Frandsen</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Frederickson</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Graciarena</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Kintzing</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Leveque</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Mason</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Niekrasz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Purver</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Riedhammer</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Shriberg</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Tien</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Vergyri</surname>
            , and
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Yang</surname>
          </string-name>
          .
          <article-title>The CALO Meeting Assistant System</article-title>
          .
          <source>In IEEE Transaction on Audio, Speech and Language Processing</source>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>J. Ulrich</surname>
            ,
            <given-names>G.</given-names>
            Murray, and G.
          </string-name>
          <string-name>
            <surname>Carenini. A Publicly Available</surname>
          </string-name>
          <article-title>Annotated Corpus for Supervised Email Summarization</article-title>
          .
          <source>In Proc. of AAAI EMAIL-2008 Workshop</source>
          , Chicago, USA,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <given-names>P.</given-names>
            <surname>Wellner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Flynn</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Guillemot</surname>
          </string-name>
          .
          <article-title>Browsing Recorded Meetings with Ferret</article-title>
          .
          <source>In Proc. of MLMI</source>
          <year>2004</year>
          , Martigny, Switzerland, pages
          <fpage>12</fpage>
          -
          <lpage>21</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <given-names>S.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Favre</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
            Hakkani-Tu¨r, and
            <given-names>Y.</given-names>
          </string-name>
          <string-name>
            <surname>Liu</surname>
          </string-name>
          .
          <article-title>Leveraging Sentence Weights in a Concept-based Optimization Framework for Extractive Meeting Summarization</article-title>
          .
          <source>In Proc. of Interspeech</source>
          <year>2009</year>
          , Brighton, England,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>K.-P. Yee</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Swaringen</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>LI</surname>
            , and
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Hearst</surname>
          </string-name>
          .
          <article-title>Faceted Metadata for Image Search and Browsing</article-title>
          .
          <source>In Proc. of CHI</source>
          , Boston, USA,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <given-names>L.</given-names>
            <surname>Zhou</surname>
          </string-name>
          and
          <string-name>
            <given-names>E.</given-names>
            <surname>Hovy</surname>
          </string-name>
          . Digesting Virtual “
          <article-title>Geek” Culture: The Summarization of Technical Internet Relay Chats</article-title>
          .
          <source>In Proc. of ACL</source>
          <year>2005</year>
          , Ann Arbor, MI, USA,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhu</surname>
          </string-name>
          and
          <string-name>
            <given-names>G.</given-names>
            <surname>Penn</surname>
          </string-name>
          .
          <article-title>Summarization of Spontaneous Conversations</article-title>
          .
          <source>In Proc. of Interspeech</source>
          <year>2006</year>
          , Pittsburgh, USA, pages
          <fpage>1531</fpage>
          -
          <lpage>1534</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>