ably” keeping the topic of conversation around love
until he overtly states that his madness is caused by
her rejected love. We say “presumably” because this
plan fails, because Hamlet refuses the returned gifts
(and we do not know how it could have continued);
so, Ophelia re–plans to explicitly introduce the topic
of the conversation (Hamlet’s madness). On the other
hand, Hamlet’s plan is convince Ophelia that the court
is corrupted and then advise her to go to a nunnery.
Also Hamlet’s plan fails because Hamlet realizes that
someone, probably Polonius, is hidden behind some
curtain in the room and, so, he re-plans to put at test
Ophelia’s honesty before going back to his previous
plan of advising her a nunnery. As we know, this does
not happen, and Hamlet gives up his plan definitely.
Each high–level plan roots a plan hierarchy. The
larger the hierarchy, the longer the span of the hier-
archy onto the sequence; the higher and longer the
number of hierarchies, the more present the charac-
ter in the drama. In case two plan hierarchies, of two
different characters, hinge on the same sequence por-
tion (sometimes even spanning the same incidents)
we have a dramatic conflict, usually solved with the
success of one character and the failure of the other.
For example, the climax of the “nunnery” scene is
when Hamlet, who wants to ascertain Ophelia’s hon-
esty, asks her a rhetorical question (“Where is your
father?”), knowing the right answer (that he is in the
room), hoping that she replies honestly, and Ophelia
lies (“At home, my Lord.”), trading honesty for loy-
alty to her father. This conflict should be visualized,
to help the drama analysis.
The whole approach works by matching the ac-
tions reported in the plans with the incidents in the
sequence; in this way, each plan spans some portion
of the sequence through the alignment of actions in
the plan with actions in the sequence. However, we
can notice that each plan also introduces precondition
and effect states, to border the actions or the subplans
(which recursively are implemented through actions)
on the left and the right, respectively. The incidents
of the sequence are viewed as operators that carry
on the story development from one state to the next
one; states are projected from the plan structure onto
the sequence, augmenting the representation connect-
ing the motivations (goals and plans intended by the
characters) to the actions actually carried out. So, if
we want to visualize the story advancements through
the states that hold during the drama development, we
augment the sequence with states, as extra elements in
the sequence. Finally, it happens that some incidents
in the timeline are not the result of a planned delib-
eration of some character or the hierarchies of plans
are incomplete with respect to the sequence: in both
these cases, the visualization should mark such mis-
alignments between the hierarchies and the sequence.
3 RELATED WORK
Sequences and hierarchies have been receiving many
solutions in the visualization literature (Heer et al.,
2010) (Liu et al., 2014), with specific metaphors for
time (Aigner et al., 2011) and trees (Schulz, 2011).
The case of multiple trees spanning the same set of
basic elements (usually the leaves of a tree) has been
the object of several approaches of information visu-
alization (see the survey in (Graham and Kennedy,
2010) on single and multiple trees). Some work (Card
et al., 2006) has also addressed the problem of stitch-
ing together hierarchical structure and time into one
visualization space, in order to help an analyst under-
stand how very large hierarchies change through time;
the goal is to enable the analyst to detect patterns of
relationships. However, this approach addresses the
evolution of a hierarchy in time rather than what hier-
archies span within some timeline.
The visualization of story relations has at-
tracted the attention of visual artists and amateurs
to provide unique maps for orientation. This
is particularly useful for stories with intricate
plots that are not immediate to grasp (see, e.g.,
the visualization of two Nolan’s films Memento,
2000, http://visual.ly/memento-scene-timeline,
visited December 2014, and Inception, 2010,
http://visual.ly/inception-timeline-visualisation, vis-
ited December 2014), but also to trace the overall
involvement of characters, visualized as horizontal
chronological lines that converge and diverge, il-
lustrating their mutual interactions as well as their
relationship in time with places and/or collective
events (see, e.g., the movie narrative charts at
http://store.xkcd.com/collections/posters/products/
movie-narrative-charts-poster, visited December
2014). The latter visual design was then automatized
through some algorithmic approaches in (Tanahashi
and Ma, 2012) and (Liu et al., 2013), with issues of
symmetry and compactness, and consequent impact
on readability of features with respect to the manual
version. Liu et al.’s work has also introduced the
issue of hierarchic information on places, which has
some loose connection with the hierarchic structures
visualized in our approach. Again, a multi-level sto-
ryline visualization method is undertaken by (Chen
et al., 2012), which organizes and synthesizes some
representative information, that includes locations,
objects, and characters, to produce a bi–dimensional
layout for movie summaries. The automatic op-
IVAPP2015-InternationalConferenceonInformationVisualizationTheoryandApplications
166