<!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>Experiencing Events through User-Generated Media</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Raphael Troncy</string-name>
          <email>raphael.troncy@eurecom.fr</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andre Fialho?</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lynda Hardman</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carsten Saatho</string-name>
          <email>saathoff@uni-koblenz.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>CWI</institution>
          ,
          <addr-line>Amsterdam</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>EURECOM</institution>
          ,
          <addr-line>Sophia Antipolis</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>WeST Institute</institution>
          ,
          <addr-line>Koblenz</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Large numbers of websites contain (human-readable) information about scheduled events, of which some may display media captured at these events. This information is, however, often incomplete and always locked into the sites. This prevents users from creating overviews of media associated with an event from multiple websites. We carried out exploratory user studies with potential end-users to guide the design of a web-based environment for supporting event-based services. Based on our results, our goal is to provide support for exploring and selecting events and associated media, and for discovering meaningful, surprising or entertaining connections between events, media and participants by consuming linked data. We assembled a large collection of event and associated media descriptions, which we interlinked with the Linked Open Data cloud. The dataset is obtained from three large public event directories (last.fm, eventful, upcoming) represented with the LODE ontology and from large media directories ( ickr, youtube) represented with the Media Ontology. We present the results from the user studies, the conversion, interlinking and publication of the data following the best practices of the Semantic Web community, and our initial application design.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>As with all developing technologies, it is di cult to identify novel user needs
that can be satis ed with emerging semantic web technologies. Large scale data
integration is often cited as an example where linked data technologies prove to
be useful. On the contrary, end-user applications that bene t from these
technologies in order to better support users tasks have yet to come. Hence, the
community is now putting a lot of e ort into developing end-user applications
that bene t from consuming linked data and end-user interfaces that go
beyond generic linked data browsers. We echo the opinion expressed in a recent
provocative statement: User Interfaces for Semantic Web: Do They Have to Be
Ugly? 4, and we also argue that uni ed interfaces for data access is a myth. In this
paper, we present a method to guide the design and implementation of a
particular system { an event-based environment for users to explore, annotate and
share media, in response to well-identi ed user needs: relive experiences based
on media and background knowledge and support decision making for attending
upcoming events, in the context of sparse data locked in various websites.</p>
      <p>
        Events are a natural way for referring to any observable occurrence grouping
persons, places, times and activities that can be described [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Events are also
observable experiences that are often documented by people through di erent
media (e.g. videos and photos). We explore this intrinsic connection between
media and experiences so that people can search and browse through content
using a familiar event perspective. Our goal is to design an application that
support users in interacting with events and discover meaningful, entertaining or
surprising relationships amongst them. Various websites such as eventful.com,
upcoming.org, last.fm/events and facebook.com/events to name a few, provide
already interfaces to some of these functionalities but these services have
sometimes overlap in terms of coverage of past and upcoming events and provide
each their own social networks features to support users in sharing and deciding
upon attending events. The information about the events, the social connections
and the representative media are therefore all spread and locked in amongst
these services providing limited event coverage and no interoperability of the
description. We advocate the use of linked data technologies to aggregate these
heterogeneous sources of information and we show in this paper how to model
and interlink the data.
      </p>
      <p>The work reported here uses an explorative user-centered design approach.
We rst perform a user study where users are asked about real-world tasks they
would like to carry out in order to extract functional and data requirements
(section 2). We then select precise tasks we wish to support and we carried out a
focus group study in order to ask users opinions and observe how they can realize
these scenario using speci c technologies that they are familiar with (section 3).
Lack of coverage for all event directories and frustration of being locked in a
particular site or social network being the recurrent issues, we propose to use
linked data technologies as a uni ed data model for integrating heterogeneous
information. We brie y describe how we represent description of events using
the LODE ontology and we detail the data scraping and interlinking process
together with a large SKOS taxonomy of event categories (Section 4). We present
our nal application and we provide interfaces based on this dataset to illustrate
the functionalities supported (Section 5). Finally, we give our conclusions and
outline future work in Section 6.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Exploratory User Studies</title>
      <p>
        We follow a user-centered design process done through interaction with potential
end-users at di erent stages of development. The following sections describe two
exploratory studies that assess user needs and identify behaviors while
discovering, exploring and sharing events with the support of user generated media.
Initially, we conducted a user survey and two focus-group sessions to
understand end-users' event-related experiences and to collect insights about existing
web-based technologies that support related activities [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
2.1
      </p>
      <sec id="sec-2-1">
        <title>Method</title>
        <p>The survey was completed by 28 participants (11 females) with a mean age of 27
(range 23-47). Participants were mostly students and researchers in broad
domain areas. The focus group discussions were conducted with two other groups
(10 and 25 participants) of students of web and information technology courses.
Results from these discussions were used to validate and re ne the survey
outputs. In both studies, 8 open questions were presented to the participants. The
rst half aimed at identifying participants' insights based on past experiences5.
Questions referred to how events were discovered and shared, the decision
making process, and about interesting relationships amongst events. The second part
collected insights regarding existing web technologies in the context of the
activities6. These questions explored the perceived bene ts and drawbacks of using
event directories and media, social networks, and a merger of these services.
2.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Results and Discussion</title>
        <p>Past experiences. According to participants, people's invitations and
recommendations are the main means for nding out about events. Traditional media
(e.g. posters, advertisements) also played a major role in identifying new events.
Search engines were said to be commonly used, speci cally when participants
knew what to look for. On-line social networks were another commonly reported
source, especially amongst students from the group discussions. Participants
used event directories, mailing lists, newsletters and forums less often.</p>
        <p>When deciding whether or not to attend to an event, participants assigned
importance to constraints such as distance (location), availability (time) and
budget (price). Social information about \who's joining" the event, and more
speci cally which friends will attend, also played an important role. The content
of the event itself (e.g. type, performer, topic, target audience), subjective factors
(e.g. fun, event atmosphere), and user opinions were also commonly mentioned.</p>
        <p>Participants shared their experience by sharing stories and taking pictures
and videos of attended events. Direct social interaction was the most
common and preferred choice for sharing information. Media directories (e.g. Flickr,
YouTube) and social networks (e.g. Facebook) were also commonly used.</p>
        <p>Participants reported relying on previously attended events as a means to
identify new interesting events (e.g. same venue, performer, category). Friends
attending other events, target audience and users with similar interests, were
other important identi ed relationships. Finally, future occurrences of repeated
events was also seen as a strong relationship.</p>
        <p>Existing technologies. Event directories were positively viewed for providing a
single source for information overview, allowing opportunistic discovery of events
by time, by category or by artist. Other positive features included social features,</p>
        <sec id="sec-2-2-1">
          <title>5 The survey is available at http://tinyurl.com/eventmedia-s1</title>
        </sec>
        <sec id="sec-2-2-2">
          <title>6 The survey is available at http://tinyurl.com/eventmedia-s2</title>
          <p>noti cation of upcoming events, and links to related services (e.g. tickets). Low
coverage of events was seen as a main drawback; others included information
overload, unreliability and incompleteness (e.g. lack of location map and videos).</p>
          <p>Participants recognized bene ts from enriching events through media
directories. According to participants, media facilitate reliving and sharing experiences.
Additionally, media give a better impression of the environment/atmosphere and
provide valuable information for decision support. As for enriching events with
social networking information, participants reported that the main bene ts are
communication and information sharing between users. More importantly, it
enhances the attendance information by allowing to identify social proximity (e.g.
friends participating) and event popularity. Live event information updates (e.g.
real-time tweets) was also seen as a positive feature. For both enhancements
(associated media and social information) the drawbacks concerned information
overload and privacy issues while sharing personal media.
3</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Scenario-based user study</title>
      <p>Based on the results of the exploratory user studies, we identi ed a set of
potential use-cases. However, since participants relied on past experiences, it is
debatable whether collected insights are representative of real user behaviors. In
order to account for this and to allow a better understanding of behaviors in a
well-de ned scenario, a second study was performed in order to identify
participants' strategies, information sources and behavior patterns while enacting four
prede ned scenarios:
1. Collect information about an event after receiving an invitation and decide
whether or not to attend the event.
2. Use the information about an attended event, as well as other people's
opinions (i.e. review, ratings) to identify similar events in the future.
3. Discover and decide about currently occurring events based on what other
friends are currently doing (i.e. life streams).
4. Upload and share media for an attended event and explore other people's
experiences through available media.</p>
      <p>Two sessions were conducted where participants were requested to complete
a set of scenarios, performing di erent tasks in order to achieve the presented
goals. Fifteen participants (3 females) took part in the study at two research
organizations. The mean age was 26 (range 23-49, SD=9.3). All participants used
internet on a daily basis and were acquainted with related on-line services.
Online social network, media directory and event directory usage was measured on
a 5pt Likert scale ranging from \never used" to \constantly used". Participants
reported that they sometimes used social networks (M=3.3, SD=1.3) and media
directories (M=3.1, SD=0.7), and never or rarely used event directories (M=1.3,
SD=0.5). During each session of around 1.5 hours, participants role-played the
four di erent scenarios while making use of internet access and a list of links to
well-known social networking services, media and event directories. Each
participant was requested to self-report his or her experience. After each scenario was
completed, participants shared their expectations, strategies, and outcomes of
their actions. In addition, collaborative a nity diagramming was conducted by
the groups to organize the outputs for each scenario. The a nity diagramming
was done using post-it notes with the self-reported actions. During the exercise,
participants collaboratively clustered the notes into di erent action sets on a
ip-chart, thus making the strategy and behavior patterns explicit.
3.1</p>
      <sec id="sec-3-1">
        <title>Observations</title>
        <p>While completing each scenario, participants used on average 5 di erent
information sources (most-used rst): search engine (Google), venue/event website,
media directories (e.g. YouTube, Flickr, Picassa), social networks (e.g. Facebook,
Twitter), event directories (Last.fm, local city event directories).
Seeking information. The majority of the participants started the scenarios
by searching for events using a search engine (e.g. Google). Participants used
general terms or information provided by the scenario, usually combining title,
venue, performer and other information, such as city or time, to constrain the
search. Results directed users to event directories or to speci c venues/events.
Some participants were acquainted with speci c events or venues and tried to
reach the website directly. Some participants also searched in social networking
services, limiting their strategies to nding events through friends, but had little
or no information about the speci c events presented in the scenarios. Other
participants used event directories (e.g. Eventful, Upcoming , Zevents) but were
mostly dissatis ed with results from the event directories due to low coverage for
the speci c scenarios. However, local directories seem to provide better results.
In many cases, participants ended up at speci c venue/event websites.
Regardless of the sources, participants usually performed several subsequent searches,
mainly on search engines to obtain further information (e.g. location on map,
images, videos, user comments). While searching for related events, participants
used event characteristics (e.g. type, genre, sub-genre, performers) as keywords.
Alternatively, few participants relied on related event videos on YouTube or
related event artists from Last.fm to identify related events.</p>
        <p>Exploring Information. For participants who were redirected to the event
website or were able to track the event on the venue website agenda, information
about the event in terms of date, description, and performers was readily
available as well as some images and videos providing a better illustration about the
event. These seem to be the most complete information sources. Some used
information from event directories which also provide factual data and few images
from the event or the event performers. The directories provide also information
about the event attendance as well as comments and reviews which was also
appreciated by participants. Social networks such as Facebook were the favorite
means for obtaining friends whereabouts, their event opinions and to see it they
were attending the investigated event. Another few participants said they would
rely on instant messengers or emails in order to contact their friends directly.
Social networking services (e.g. Twitter and Facebook) was also said to be the best
source of live information about the events. In most cases, however, participants
still searched for other related images and videos on a search engine or on media
directories (e.g. YouTube) in order to better convey the experience. Participants
said that images and speci cally videos allowed a better understanding of the
event's atmosphere and environment (e.g. party, disco, cozy).</p>
        <p>Sharing Information. Most participants chose to share their event
experiences through images on media directories such as Picasa and Flickr. The
directories were speci cally good for posting whole sets of pictures. These directories
are also the main source to nd more pictures about an event. Some participants
also referred to YouTube to post videos about attended events. Many
participants pointed out that they would use social networks such as Facebook to post
images and videos on their pro le or on the Facebook event page. Contrary to
image directories, media is selected more carefully when posted on Facebook.
The most interesting, representative or funny pictures and videos are posted.
Friends can then comment on these media and share their experiences. Few
participants preferred to post media directly on their personal web-sites or blogs.
Some participants rely more on face-to-face sharing of media where they can
point out speci c pictures and discuss them. Few others share some pictures
directly through emails and MMS messages.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Discussion</title>
        <p>After completing all scenarios, clustered actions were used as creative input for
semi-structured group discussions. During the discussion, participants addressed
their expectations, strategies, main challenges and recommendations for
exploring and sharing events. The results from these discussions are described below.</p>
        <p>Information is spread and decentralized. When exploring events, participants
reported that there were too many di erent information sources. They recognized
that in order to ful ll the scenarios, there was a need to access several di erent
on-line services. One participant reported I don't like always having to go from
one site to another to nd out things about the event. Therefore, participants
agreed it was easier to use a single search engine that has broader coverage of
di erent information sources. One participant reported There is so much
information that it's di cult to prevent the immediate reaction to go to Google.
However, if the participants knew where to nd the information, they would go
directly to that information source using bookmarks or known website addresses.
Speci c venue or event web sites were seen as the best source for information
overviews. The sources often provided all necessary integrated information,
including media. Social networks such as Facebook were also reported to integrate
available information (e.g. photos, attendance list, discussions) to some degree,
but not su ciently. Participants suggested integrating social networks with other
services. However, participants also agreed that an ideal solution should not just
be another information source. There should be some means of centralizing all
available information. This can be summarized through one participant's
comment: It would be nicer to have a mash-up with the most important information
from each website.</p>
        <p>Information seeking and decision making strategies. While searching for
interesting events, there was no agreement on the search strategy. However, most
participants reported that the most important information was location, time
(date), type of event and popularity. A common strategy was to start
constraining the factual properties of the event (e.g. type, location and date) in order
to lter the available information. Participants showed an interest in specifying
these constraints by de ning ranges (e.g. max price). Searching by title (if known)
and other information were amongst other options. Other few participants
suggested alternative methods for identifying events, such as mobile location-based
services to track nearby events. Participants also agreed that the strategies were
dependent on type of event (e.g. concerts, parties, art exhibitions). Furthermore,
social aspects such as people and friends who are attending could have priority
over any other available information. Therefore, starting to search by friends
was another potential starting point. One participant commented If your close
friends like it, it's more likely that you will enjoy it.</p>
        <p>Relationships and recommendations. Similarities among events that were
said to be interesting include: location, date, event type and genre. However,
participants agreed that the most valuable relationship was based on the
common interests of people who attend the event. Recommendations were also seen
as a potential feature, where users could receive interesting events based on
popularity and ratings, people with similar interests/behaviors, friends' attendance,
or on the user's past attendance, by keeping a user history.</p>
        <p>Participants agreed that the presentation of information about events should
be sorted (e.g. time, relevance, popularity) according to their needs
(customizable). While displaying large numbers of related media, these could be clustered
depending on the event type, media owner (e.g. friends) or visual similarity.
Another suggested option was to show only the most popular media or lter
the media that belong to known friends. Participants indicated that the most
important information is factual information (e.g. what-where-when) and that
any other relevant information should be one click away. Most participants
argued they would like to have an instant overview of the event through associated
media. Participants also agreed that while conducting the scenarios, associated
media was the best way to easily illustrate the whole experience. One participant
commented You can have an idea about how the event looks like and what kinds
of people go there. It's kind of like a preview. Excerpts of songs, for a musical
event (audio or video), would also be highly appreciated. Additional information
such as ratings for events, weather conditions, distance from current location,
travel information (public transportation) and accessibility are also said to be
very useful. Being able to see user attendance was mentioned. Additionally, user
pro le pictures can convey a better idea about the \type of people" or target
audience of the event.
We are aware of a number of limitations with this study. The events selected for
the scenarios may not have corresponded with users' interests. We feel, however,
that our results are su ciently valid for guiding the development of the
functionality of the application. Our results from the studies suggest the need for services
that combine information from di erent event directories, social networks and
media sharing platforms. Since information is spread and locked in di erent
services, users express the need for a single resource to explore to experience events.
Although this bene t is recognized for existing event directories, their lack of
event coverage and information completeness a ects the user experience.</p>
        <p>Users also pointed out the bene ts of merging di erent information sources.
Social factors are a strong component when identifying, deciding and sharing
experiences about events. Participants rely on other people not only to receive
invitations and recommendations about events, but also to decide whether or
not to attend. Social information obtained by attending an event (e.g. \who else
is going?") or by sharing experiences (comments, reviews and ratings) provide
valuable support for the decision making process. Shared interests amongst users
is also the main identi ed means for obtaining event recommendations. \A
picture is worth a thousand words" and associated media were also described as
the perfect means for representing events. Images and video provide a
powerful means for identifying several event characteristics, to convey the experience
and to provide decision support. While participants request more information
about the events, there is a common concern about information overload. This
issue suggests that interfaces should avoid cluttered information and provide
only timely and necessary information. Furthermore, there is a need to
support di erent visualizations and improved browsing options that depend on user
interests and constraints.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Data Scraping and Interlinking</title>
      <p>
        In this section, we detail how the data from events and media directories is
represented and interlinked. Overall, the dataset collected contains more than
30 million triples [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. We provide a dump at http://www.eurecom.fr/~troncy/ldtc2010/
and a SPARQL endpoint at http://data.linkedevents.org/sparql.
      </p>
      <p>
        We have described and thoroughly compared numerous event ontologies in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
which has lead to the development of the LODE ontology7, a minimal model that
encapsulates the most useful properties for describing events. The goal of this
ontology is to enable interoperable modeling of the \factual" aspects of events:
What happened, Where did it happen, When did it happen, and Who was
involved. LODE is not yet another \event" ontology per se. It has been designed
as an interlingua model that solves an interoperability problem by providing a
set of axioms expressing mappings between existing event ontologies such as MO,
CIDOC-CRM, DOLCE, SEM to name a few. The Ontology for Media Resource
      </p>
      <sec id="sec-4-1">
        <title>7 http://linkedevents.org/ontology/</title>
        <p>currently developed by W3C is a core vocabulary which covers basic metadata
properties to describe media resources8. It also contains a formal set of axioms
de ning mapping between di erent metadata formats for multimedia. We use
this ontology together with properties from SIOC, FOAF and Dublin Core to
convert into RDF Flickr photo and YouTube video descriptions.</p>
        <p>Figure 1 depicts the metadata attached to the event identi ed by 1380633
on last.fm according to the LODE ontology. More precisely, it indicates that an
event categorized as a Concert has been given on the 24th of January 2010
at 20:00 PM in the Henry Fonda Theater featuring the Radiohead rock band.
The link between the media and the event is realized through the lode:illustrate
property, while more information about the sioc:UserAccount can be attached
to his URI. Hence, we see that the video hosted on YouTube has for ma:creator
the user aghorrorag.</p>
        <p>
          We have populated these ontologies by scraping and semantifying data from
event directories. We have been able to convert the description of more than
1.7 million photos which are indexed by over 108.000 events (table 1). We
initially explored overlap in metadata between three websites ( ickr, upcoming and
last.fm) looking into explicit relationships between events and photos using
machine tags. Furthermore, event descriptions from eventful were extracted by a 3
years sampling ltered by events tagged with the \music" keyword in order to
maximize the likelihood of interlinking with the other event directories. Finally,
we extract associated event videos from YouTube employing various querying
strategies (e.g. event title, venue, performers) while using the date as a lter.
It is important to note that we did not scrap all data that was available but
8 http://www.w3.org/TR/mediaont-10/
only the data that was mentioned as useful during our user studies. We invoke
additional semantic web lookup services such as dbpedia, geonames and freebase
in order to enrich the descriptions of the agents and the locations. More details
about the dataset are available in [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. The linked data journey can be rich and
long. One of the challenges we want to address is how to visualize these enriched
interconnected datasets while still supporting simple user tasks such as searching
and browsing media collections.
Back-end Architecture The back-end of the system consists of a Sesame2 9
SPARQL endpoint, a distributed query engine, a RESTful API, and a web server.
All URIs minted in the dataset are dereferencable and are served as either static
RDF les serialized in N3 or as JSON by the RESTful API. We implemented
content negotiation in order to let clients decide about the desired representation.
Clients requesting a JSON representation are redirected to the RESTful API,
which is implemented using the Restlet library10 and runs within an OSGi
runtime environment. Within this environment, a local RDF repository is used that
is set up as a federator using a Distributed SPARQL implementation [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. Besides
serving JSON representations of resources available in the dataset, the RESTful
API also provides convenience methods exposed as additional resources, which
are not explicitly represented in the dataset. Examples for such functionalities
include search over the dataset using di erent parameters such as keyword, time,
location. We also allow dataset updates, for instance, by being able to specify
attendance information or link additional media to existing events from the
front-end.
        </p>
        <p>
          Discovering Events Users wish to discover events either through invitations
and recommendations, or by ltering available events according to their
interests and constraints. Therefore, the interface allows constraining di erent event
properties (e.g. time, place, category). Mechanisms for providing this desired
support include restricting a time period through a timeline slider control
input (Figure 2). Categories and location can be ltered using hierarchical faceted
metadata [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], allowing users to browse through di erent dimensions of the
collection. The hierarchical facets are presented according to the prede ned event
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>9 http://openrdf.org/ 10 http://www.restlet.org/</title>
        <p>
          categories in the SKOS taxonomy, and through an event's geo-location
information. These properties allow the combination of di erent event types and
locations while visually guiding the user through an interactive query re nement
process. Faceted browsing also avoids empty results by restricting the available
ltering options to display only non-empty results. Since users are likely to
revisit information they have viewed in the past [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], we will also support simple
history mechanisms, by saving a list of recently viewed events. To aid search,
input boxes with dynamic term suggestions (auto-completion) is used to provide
user feedback by suggesting a list of matching terms while typing.
Displaying Information After an event is selected, all associated information
is displayed. Media are presented to convey the event experience, along with
social information to provide better decision support. According to user
interests, social proximity should be emphasized while displaying event attendance
(e.g. friends attending). Other information that should be presented includes:
performers, topic, genre, price. While scraping the data, some events such as
popular music festivals were associated with more than 2,000 photos and videos.
In order to deal with this large number, pagination is used while ordering media
according to di erent contexts (e.g. by popularity, time, or social proximity).
Alternatively, pictures are clustered according to context or visual similarity,
and representative images are shown through Treemaps to present a varied
sample of associated media. To allow searching for events in a variety of contexts,
users also requested to be able to see events according to di erent views. We
explore these di erent views according to the basic event properties de ned in
the LODE ontology. What - Displays the most relevant associated media. A
treemap is used to represent di erent event sets, where size can convey di erent
properties (e.g. relevance, popularity)11. When - Shows the chronological
relations among events. A time axis is used to visualise the start-time and duration
of events. Where - Indicates where events occur geographically to orient the user
and convey distance. Maps are commonly used to visualize such information.
6
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusion and Future Work</title>
      <p>We described an event-based approach for users to explore, annotate and share
media. We conducted two user studies, where users were asked about real-world
tasks they would like to carry out. We observe and identify participants'
strategies, information sources and behavior patterns while enacting prede ned
scenarios. We used and consumed linked data technologies for integrating
information contained in event and media directories. We described the scraping and
interlinking process yielding a unique and dense dataset of more than 30
million triples. Finally, we present the architecture and the user interfaces of the
application available at http://eventmedia.cwi.nl/demo.
7</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>The authors would like to thank Fabien Duchateau (CWI), Hyowon Lee (DCU),
Bartosz Malocha (EURECOM) and Ansgar Scherp (WeST Institute) for fruitful
discussions on the infrastructure and the design of the EventMedia interfaces.
The research leading to this paper was supported by the European Commission
under contract FP7-216444, Petamedia Peer-to-peer Tagged Media.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>A.</given-names>
            <surname>Fialho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Troncy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hardman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Saatho</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Scherp</surname>
          </string-name>
          .
          <article-title>What's on this evening? Designing User Support for Event-based Annotation and Exploration of Media</article-title>
          . In 1st International Workshop on EVENTS -
          <article-title>Recognising and tracking events on the Web and in real life</article-title>
          , pages
          <volume>40</volume>
          {
          <fpage>54</fpage>
          , Athens, Greece,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>M.</given-names>
            <surname>Hearst</surname>
          </string-name>
          .
          <article-title>Search User Interfaces</article-title>
          . Cambridge University Press,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>S.</given-names>
            <surname>Schenk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Saatho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staab</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Scherp. SemaPlorer - Interactive Semantic</surname>
          </string-name>
          <article-title>Exploration of Data and Media based on a Federated Cloud Infrastructure</article-title>
          .
          <source>Journal of Web Semantics</source>
          ,
          <volume>7</volume>
          (
          <issue>4</issue>
          ):
          <volume>298</volume>
          {
          <fpage>304</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>R.</given-names>
            <surname>Shaw</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Troncy</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Hardman</surname>
          </string-name>
          . LODE:
          <article-title>Linking Open Descriptions Of Events</article-title>
          .
          <source>In 4th Asian Semantic Web Conference (ASWC'09)</source>
          , pages
          <fpage>153</fpage>
          {
          <fpage>167</fpage>
          , Shanghai, China,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>R.</given-names>
            <surname>Troncy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Malocha</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Fialho</surname>
          </string-name>
          .
          <article-title>Linking Events with Media</article-title>
          .
          <source>In 6th International Conference on Semantic Systems (I-SEMANTICS'10)</source>
          , Graz, Austria,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>11 See for example http://www.jinni.com or http://www.ted.com/talks.</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>