by two main reasons: (1) Having a multiple window
layout helps in task in which more than one entity is
needed, like in the case of comparisons or relations
management. (2) Being able to minimize windows,
the user can implicitly keep track of its actions, or
can put in pause a task and continue with another
one. The will allow to build a section-less system.
As stated in the previous paragraph, the UKC-1 is
divided into regions, each one assigned to a
particular nature of given results, or to a kind of
those. This approach has been demonstrated, by the
analysis, to be distracting for the users. Indeed they
usually have been losing the context when switching
from one to another, in order to retrieve a given
results. Other three main points that have
contributed to the redesign of the user interface:
Consistency of the representations: assign to
each entity involved in the system a unique way
of visualizing it, in order to maintain the
consistency of the entities in different sections or
scenarios of the application.
Modularity of the interface: the system should
adapt itself to what are the user's needs. By being
able to modularize it, it would be possible for the
user to customize it, in order to better fit his
needs. It would also allow to fit particular
scenarios of interaction by configuring it.
Achievement of graphical methods for
knowledge interaction: a part from the current
interface, based on textual components like
tables, snippets, tooltips and buttons, a second
method of interaction would be based on shapes
and colors, thus graphics. This is needed in a
multilingual context like the one in which the
UKC is set.
The new web client pursues the co-existence of two
different kinds of interactions, textual and graphical
on the same content pane, however in this paper
only the textual one is discussed.
The Textual User Interface was designed to
resemble the current implementation of the UKC UI,
proposing methods of interaction based on text input
and forms. The TUI overall architecture (Figure-7)
is composed of two different managers:
Window Manager: this module is responsible of
the creating and handling the different windows
present in the interface. By using a modal
windows based system, the users might interact
with multiple entities at times, shown in different
windows, each one customizable by the manager,
on the base of the user needs. For example,
displaying multiple results at once, or comparing
two similar elements.
Perspective Manager: this component is used to
provide transformation in data shown. The
perspective is used to translate an entity between
the four different available perspectives: natural
language, formal language, E-Types and
domains. The change of perspective is then made
dynamic and applicable to each result (namely
window) separately, such that the user will be
aware of how a piece of knowledge changes in
each point of view. Furthermore this will prevent
the user to lose the context in which he is
currently working. An example of change of
perspective is given by the natural and formal
language windows. In the first one, the concept is
shown in relation with the synsets that lexicalize
it in one or more given languages, while in the
formal perspective (realized in the corresponding
window) the same concept is shown in relation
with other concepts (language independent).
UKC Web API Interface: this module manages
the communications between the front-end web
client (running on the browser) and the data
source available through a JSON API.
Figure 7: UKC-2 Overall Architecture.
Other two main points in the new interface are the
usage of a window system and the usage of colors to
guide the user. The window choice is motivated by
the will to provide the capability to perform multiple
operations at time on the same dashboard, or in
general, operations that involve multiple entities,
like comparisons. Another point that can be elicited
from Figure-8 above is the use of colors to indicate
messages and sections. Each window, by being
associated to a kind (natural, formal or eType) is
displayed with a different color in the header. In this
way the interface can implicitly guide the user
through its sections without using labels.
Furthermore, each window kind, in the new
interface, represents a perspective. A perspective is a
type of view over the data, and can be transformed
from one to another. By doing this, the user does not
lose the context while changing from a section to
another.
In the new interface, colors are also used to
AnInteractivePlatformforMultilingualLinguisticResourceEnrichment
203