<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Media Aggregation via Events</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Fausto</forename><surname>Giunchiglia</surname></persName>
							<email>fausto@disi.unitn.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Pierre</forename><surname>Andrews</surname></persName>
							<email>andrews@disi.unitn.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Gaia</forename><surname>Trecarichi</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ronald</forename><surname>Chenu-Abente</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Media Aggregation via Events</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">E1D7CB2E877B8AA2395443ABB2979B9A</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T03:35+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Events have been recognised as important metadata to fill the semantic gap between our experience of the world represented in media and its conceptualization. In this paper, we argue that, once event metadata can be extracted, there remains a gap between different users conceptualizations. We then show how a compositional event model can mitigate such a social semantic gap through higher level descriptions of events where an agreement can be reached. In turn, this enables semantic services which improve event-centric search and navigation of shared media.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>With the increase of information and media streams available to us, everyday's tasks such as searching and relating relevant data have become intractable. One of the recognised causes for this issue is the semantic gap existing between our conceptualizations of the world, usually expressed using language or other high level abstractions, and our experience of the world, whose most direct physical representation is kept in media. In fact, even if automatic image processing algorithms can help by extracting high level concepts from media (e.g., who is present in a photo), they still miss the general semantics of the experience memorized by media such as the context in which a photo was taken or what it means for the user (e.g., the feelings and impressions of what happened when a photo was taken). Such experiential aspect cannot yet be extracted automatically and thus a number of solutions and services are being proposed to tame the incoming streams of data. To this purpose, event models have been proposed to help in the extraction and indexing of event information within data streams.</p><p>However, once a high level representation of an event is extracted or manually provided in the local context of a single user, there is no guarantee that this conceptualization will be understood by other users. We believe that there is a second gap, the social semantic gap between a local user experience conceptualization and what other users might understand of this conceptualization.</p><p>In this paper, we propose a general event model that we believe helpful in aligning different local event representations and show how it can be applied to the issue of media management. In Section 2, we provide a motivating example for our event model. In Section 3, we introduce in more details the issue of social semantic gap, while in Sections 4, 5 and 6 we describe in more detail this new model. Section 7 shows how it can be applied to model experiences and media to help the sharing of such media with better metadata. Finally, Section 8 relates our work with state-of-the-art event models.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Motivating Example</head><p>Danda has just returned from a tour in the Italian region of Trentino with her friend <ref type="foot" target="#foot_0">1</ref> . She collected lots of material (e.g., digital photos, diaries, videos) and now wants to organise it digitally to revisit it later on and share her trip memories with her friends. With the current Web 2.0 technologies, she can rely on blogs, video sharing websites (e.g., YouTube) and online photo management software (e.g., Flickr, Virgilio Foto Album), to store and share the material. Since she likes writing, she opts to communicate the experience through her blog and thus dedicates some blog posts to describe the three days spent in Val di Non, the locality visited. In the first blog post titled "My journey diary -11 Aug 2008", she describes the things that happened during the first day of the trip: the journey from Rimini to Trento by train, the one from Trento to Cles by the local railway Trento-Malé, the nice chats she had with the owner of the B&amp;B during the journey from Cles to the B&amp;B located near Revó, a small village close to the Santa Giustina lake, and so forth. The second day is described in a second blog post providing detailed descriptions of the breakfast she had in the B&amp;B and of the itinerary followed to go to the Tovel lake. Finally, in two other blog posts, she describes the visits made to the Novella river park and the Tret waterfall and the concert of the Ramadas band attended during the third day. In all posts, images illustrate snippets of text to enhance the visual impact of the blog. However, the full gallery of pictures is maintained in a separate online photo management system which is pointed to by a link included in the blog post. An excerpt of the first blog post follows:</p><p>"At Trento we wait for another train, this time on a local railway, the Trento-Malé. Our last stop is Cles from where buses depart for various villages, including Revó; however, the kind owner of the B&amp;B waits for us there and gives us a lift by car..."</p><p>The way Danda discloses her trip experience allows her to fix her memory of the journey and to make friends and interested bloggers aware of it. It is important to note that Danda is ultimately interested in describing and sharing the events happened to her rather than just sharing a bunch of photos, these last being rather supporting material to give evidence of her experience and embellish the story. She describes the three-days trip by splitting it into days -or part of dayseach corresponding to few significant events, which, in this case, are mostly visits to natural locations. The events range from small-scale ones (e.g., the breakfast, the move from Trento to Cles) to more large-scale, composite ones (e.g., the whole trip, the visit to a natural location, the concert) and span several types (e.g., a visit, a move from one place to another, breakfast, walk, conversation, concert). Also, all their descriptions mention different entities such as locations (e.g., Trento, Cles, Tovel, Novella river park, Tret waterfall), time periods (e.g., 28th August 2008), people or group of people (e.g., trip companion, B&amp;B owner, Ramadas band), and others (e.g., "Trento-Malé").</p><p>If an user-oriented personal media management system existed that allowed for an easy way to describe complex events, Danda would be supported in reliving the "trip event" by recalling salient events at the desired level of details, the persons met, and the places she visited in a more active, experiential manner. Moreover, she would experience pre-or post-trip visits by knowing more about the locations (e.g., facts and media), some co-located events and related stories. The framework we envision supports the well-understood need for event-centric media management systems.</p><p>In addition, by having a structured description of the media and event metadata, the events described by Diana can be matched with other users' events and with global definitions of events. We believe, this will reduce the social semantic gap between local descriptions and global understanding of events.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">The Social Semantic Gap</head><p>There has been a long stream of research in media processing and media management to fill the semantic gap between what can be seen in a media (the person in a photo for instance) and what it actually represent as an experience for the person that created the media. This can be partly solved by adding event metadata to the media to help understand the context in which they were created. However, in many cases, this event information is created locally, either semi-automatically or manually, at a user level. The particular descriptions of the events at a local level, even if abstracting the content of the media, can still be different from their shared global conceptualization. As shown in Fig. <ref type="figure" target="#fig_0">1</ref>, two different users might have a different high level description of a media, and thus there is still a gap between the different personal users' representations of their experiences.</p><p>In professional applications, like news media management for instance, there is a top-down agreement on the existing events (e.g., football championship, political conflicts) and thus the gap between the meaning of the events represented in the media and the ones described in the final products (e.g., newspaper articles) composed with these media is kept under control. For instance, everyone shares the understanding of what the "New Year Celebration" is and what experience the media used in the news for that event might represent. However, in the personal application sphere, any of the user's personal experiences can be transformed in an event and there is thus no widespread agreement about events and what they might represent for each single user. A user can create an event about her "Family Holiday" and understand the experiences that are represented in the media for this event, but, outside of her local context, such experiences and events are not meaningful anymore. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>. Media and Social Semantic Gap</head><p>There can still be a social agreement between users that sit between the Global and Local contexts when the event is shared by a small group of participants. For instance, all the people attending a "Friends' night-out" event will understand the experiences in the media attached to this event, but this understanding will be lost to anyone outside of this group. Thus the events that can be extracted -or provided manually by the user -for the personal user's media are built bottom-up and are difficult to share: there is still a large social semantic gap between the local descriptions and their perception by the community.</p><p>We believe that the main cause of such a social semantic gap is due to the lack of aggregable metadata for these media. This makes it difficult to align single event descriptions from different users. We propose to solve this issue by modeling the events structural aspect <ref type="bibr" target="#b0">[1]</ref> and provide a compositional event model where fine grained events can be composed into higher level events in order to provide a middle ground between top-down event agreement and bottom-up event creation. In fact, if the media are stored in a rooted structure of events, it will be easier to match between diverse local events into a global consensus. For instance, if a set of media is associated to a personal "Toast" event, it is impossible to know if this is a toast during a normal dinner, during a graduation ceremony or at a wedding reception. If this event is provided in the context of subsuming events, as illustrated in Fig. <ref type="figure" target="#fig_2">2</ref>, it is then easier to know its semantics.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Entities</head><p>In our example, we can first notice that Danda refers to a number of "objects" in the real world, such as the places she visited or the people she met. There is a need to represent all these entities and their metadata into a model for managing the media relevant to the events she is describing. <ref type="bibr" target="#b1">[2]</ref> proposes a unique entity space to store such resources and we follow a similar entity centric model to  provide a uniform representation of objects in the real and virtual world. In our model, an entity En is described by its metadata and associated services:</p><formula xml:id="formula_0">En =&lt; id, type, Attr, Rel, S &gt;</formula><p>Where: 1. id, is a unique identifier (e.g., an URI); 2. type, is the type of entity, that is, the category to which it belongs to (e.g., the entity "Danda" is of type Person ); 3. Attr, is a set of attributes composed of pairs attr =&lt; attr name, attr value &gt; describing the properties (e.g., "date of birth") of that particular entity; 4. Rel, is a set of relational attributes composed of pairs rel =&lt; rel name, rel value &gt; describing the entity's relations (e.g., "friendOf") with other entities; 5. S, is a set of services that can be leveraged on that specific entity; for example, a service "send email" can be enabled on the Person entity type (etype).</p><p>An important aspect of our model is that both attributes and relationships can be further defined by meta-attributes. For example, attributes like "job position" or relations such as "friendOf" are provided with metadata of their own, for example to describe the time period when these are valid or the circumstances (i.e., the events) that made them true.</p><p>Another interesting aspect is the lattice of etypes that is encoded in the type property of the entity. The specific type (e.g., Person , Location, Event ) to which the entity belongs to is used to infer its possible attributes and services. Moreover, the hierarchy defined by the lattice allows to easily define new derived etypes by just inheriting the metadata and available services of parent etypes. For example, the new etype Author inherits both attributes (e.g., "name", "date of birth") and services (e.g., "send email") from the etype Person but extends them with more specific ones (e.g., "affiliation", "get h-index").</p><p>In our running example, we can identify a number of entities in Danda's recollection that can be represented in our model and used for future retrieval and reasoning: Danda participates in a "concert", which can be represented by an Event entity; "the owner of the B&amp;B" is a Person entity; and specific Location entities are described, such as the "Trento" or the "Novella river park".</p><p>The following sections describe the less trivial entities used to construct a workable model of the events in Danda's blog post. The data structures discussed hereafter can be modeled as a set of attributes, relations and meta-attributes as formalised in the general Entity model but we provide a higher-level view for clearer reading.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Events</head><p>Events, unlike facts, are closely linked to their spatio-temporal collocation and, also, to the things constituting their subject (e.g., a sparrow in the event "a sparrow falls"). In addition, unlike objects, they have clear temporal boundaries but fuzzy spatial boundaries and they have a time-span <ref type="bibr" target="#b2">[3]</ref>. Moreover, they are usually provided by descriptions and they may be composed of sub-events which are temporally, spatially and causally connected <ref type="bibr" target="#b3">[4]</ref>.</p><p>In our model, we assume that "local" events are created by users and their structuring and descriptions are thus subjective. An event entity Ev is modeled as follows:</p><p>Ev =&lt; evid, t, LEv, Cx &gt;</p><p>Where the elements of the tuple are:</p><p>evid, the unique identifier of an event; t, the temporal collocation of an event, i.e., the time interval described by the event; it can be either a specific time interval marked off by the initial and final instants -e.g., "2009:01:14:10:00" to represent the 14th January 2009 at 10am -or a generic period of time where the temporal delimitations are not specified; also, the information on the date can be incomplete (e.g, "2009:01:::" ), or relative (e.g., "the day before Christmas"), and the time interval may not be continuous as, for instance, it would happen for a "Champions League" event. -LEv represents a set of linked events and is described in more details in the following section. -Cx, the event context, this being regarded as a distinguishing feature of event entities. As demonstrated in <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b5">6]</ref>, this context is useful for localised reasoning. The event context is represented as:</p><formula xml:id="formula_2">Cx =&lt; l, type, P c &gt;<label>(2)</label></formula><p>Where:</p><p>• l, defines the spatial collocation of an event. It identifies a "geographical entity" such as a geopolitical entity, a natural body (e.g., mountain, river, lake), or a man-made infrastructure (e.g., building, stretch of road). For example, consider our running example where Danda moved around the north of Italy, the location of this "transfer" event can be modeled by defining two geographical (point) locations (Rimini and Trento) that form the stretch of train track between Rimini and Trento. Note that, although the spatial collocation could be objectively defined, the participant's perception of it, that is represented in the context, is itself subjective, e.g, in terms of the actual extension of the location itself ("Trento" vs. "Trentino Region").</p><p>• type, is the type of event (e.g., conference, trip, visit, concert);</p><p>• P c, the event's participants is a set of relations to other entities. The corresponding entity values could belong to Person , Organization as well as to non-agentive etypes. Each relation to these participating entities is annotated with meta-attributes describing aspects of each entity which are only relevant in the current event's context. This includes the role of the entity in such an event, i.e., the modality of its participation in the event: for instance, a person can be a professor in a graduation event but is then a mother in the event describing the birthday of her daughter. Our vision of role is in line with the one given in <ref type="bibr" target="#b6">[7]</ref>, where one of the key features of a role is that of being linked to the notion of context -the event's context in our model. In addition, an entity participating to a given event could be described by properties valid only within the event context: for example, a temporal attribute such as "jacketColour" is only attached to the relation between a particular event and the entity. Note that, since we regard events as subjectively perceived entities, the above mentioned properties are meant to be objective (e.g., "jacket colour") as well as subjective (e.g., "personality"). As for the attributes, relations defining the metadata of an event's participants can also be relevant only to the event's context; for instance, relations such as "girlfriendOf" or "near".</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Event Compositionality</head><p>Danda's trip has several events that can be identified and captured through the previously given event definition. For example, the transfer from Rimini to Trento can be represented as:</p><p>T ransf er(Rimini, Trento) =&lt; evid01, "11/08/2008 on the early morning", &lt; "Railroad between Rimini and Trento", "train transfer", {Danda, Danda's friend} &gt;, ∅ &gt; while the transfer from Trento to Revó can be represented as:</p><p>T ransf er(Trento, Revó) =&lt; evid02, "11/08/2008 on the late morning", &lt; "Railroad between Trento and Revó", "train transfer", {Danda, Danda's friend} &gt;, ∅ &gt; These two events can be aggregated to define a more general Departure event representing the journey that would include both Transfer(Rimini,Trento) and Transfer(Trento,Revó):</p><p>Departure =&lt; evid03, "11/08/2008 morning", &lt; "Railroad between Rimini and Revó", "train transfer", {Danda, Danda's friend} &gt;, {evid01, evid02} &gt;</p><p>The LEv from the event Departure contains references to the events it is aggregating. The running example, as a whole, can be represented as a single complex entity Trip as illustrated in Fig. <ref type="figure" target="#fig_4">3</ref>.  Note that, in Fig. <ref type="figure" target="#fig_4">3</ref>, the event that represents the whole Trip, is subdivided in Departure, Stay and Return (which refer to the going journey, the stay period and the return journey respectively). Furthermore, each of these sub-events is, in turn, subdivided in other sub-events. This tree-like compositional structure is enabled by the use of the LEv component from the event definition in <ref type="bibr" target="#b0">(1)</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Trip</head><p>As explained before, LEv represents a set of linked events that are parts of the event to which that LEv belongs. However, to keep LEv as useful as possible for its complex event modeling purposes, the following restrictions are applied to it:</p><p>Restrictions on time t, the time duration defined for a complex entity CEv, must subsume the time duration of all of its sub-events pointed by LEv.</p><p>That is, if we have a function time(Ev) → t:</p><p>Given CEv =&lt; evid, t, Cx, LEv &gt;, ∀e ∈ LEv, time(e) t</p><p>By enforcing the previous restriction, all the individual time periods involved in the children events, are guaranteed to be subsumed in the time period of the parent complex event. This enables the representation of a complex event, like the one from our running example, in a timeline as shown in Fig. <ref type="figure" target="#fig_5">4</ref>. Note how in Fig. <ref type="figure" target="#fig_5">4</ref> all events comply with this rule. For example, the event Stay spans from the first to the third day and is within this period that its children events (Breakfast, Visit(Tovel), Visit(Novella) and Concert) take place. Furthermore, note that the whole time period of Stay is not entirely covered by sub-events (e.g., a small period of time exists between the end of the event Visit(Novella) and the start of the event Concert). These blanks correspond to unspecified events in Danda's trip such as, for example, the transfer between visits where she had no memorable experiences. Restriction on context the context Cx defined for the complex entity CEv must subsume the context metadata of all of its sub-events pointed by LEv.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Day1</head><p>That is, given ( <ref type="formula" target="#formula_1">1</ref>) and ( <ref type="formula" target="#formula_2">2</ref>), if we have the functions:</p><formula xml:id="formula_3">location(Cs) → l location(Ev) → location(Cx) participants(Cx) → P c participants(Ev) → participants(Cx)</formula><p>Given CEv =&lt; evid, t, LEv &gt;, Cx ∀e ∈ LEv, location(e) location(Cx) ∀e ∈ LEv, participants(e) ⊂ participants(Cx) By enforcing the previous restriction, all the geographic locations from the children events are guaranteed to be subsumed by the parent's location and all the participants from the sub-events are guaranteed to be included in their parent's set of participants. From our previous examples, it is clear that the location for the event Transfer(Rimini,Trento) is the railroad between the cities Rimini and Trento; furthermore, the location for the event Transfer(Trento,Revó) is the railroad between the cities Trento and Revó. Applying the location subsumption restriction, the location for the parent event Departure would be the train road between Rimini and Revó or more generally the entity for North of Italy (both of which subsume the locations from the sub-events). Likewise, the participants from Breakfast and Visit(Tovel) would also be included in the set of participants of its parent event Stay. Restriction on linked events an event cannot be included in LEv if doing so would cause the creation of a loop in the events structure. Let connection( Start, End) be a function that returns a sequence of events that, through their LEv components, define a directed path from the Start event to the End event (or ∅ if no such sequence exists). Then, the restriction can be expressed as:</p><formula xml:id="formula_4">CEv =&lt; evid, t, LEv, Cx &gt;, connection(CEv, CEv) = ∅</formula><p>This restriction is introduced to avoid the conceptual problems that would arise from an event being its own predecessor, directly or through other intermediate events.</p><p>The composition of events presented in this section has the following advantages:</p><p>-Avoid repetition of information: if there is a particular information that applies to all of the children of a complex event, instead of repeating the content on each of the sub-events, this information can be included directly at the event that is aggregating them. For example, thanks to this, it is not necessary to describe the weather in both the Transfer(Rimini,Trento) and the Transfer(Trento,Revó) events. If the weather did not change between these two events, the details of the weather can be included in their aggregating event Departure and, through compositionality, this information will apply to all of its children. -Capture information emerging from the aggregation: there may exist information that emerges from the composition itself and is not part of any of its individual sub-components. For example, Danda could describe the Concert event as being "long and tiring" but each of its sub-events may not have these properties individually. The "long and tiring" description would then only apply to the aggregation of these individual events into the Concert event.</p><p>-Capture information from unspecified sub-events: as seen in Fig. <ref type="figure" target="#fig_5">4</ref>, there may exist some blanks between events at high granularity levels. A lower granularity or parent event can then be used to capture information belonging to these blanks: for example, suppose Danda wanted to add a photo she took right after having her breakfast on the 2nd Day (Breakfast event) but before her visit to Tovel (Visit(Tovel) event); instead of adding a new event only for that photo, she could just include it in the Stay event.</p><p>In the following section we show an example of how this structured metadata of the events and the media that can be attached to them can be used to fill the semantic gap.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Event-Centric Media Management</head><p>In the previous sections, we presented a general event model where an event is independent from media. In fact, an event can exist totally independently from media in many applications. However, in this paper we are interested in how such an event model can be used to move from a media-centric management to a different metaphor where events are of importance for organizing media, which is the goal of a number of projects such as GLOCAL<ref type="foot" target="#foot_1">2</ref> , PRONTO<ref type="foot" target="#foot_2">3</ref> and EventMedia<ref type="foot" target="#foot_3">4</ref> . This is supported by <ref type="bibr" target="#b0">[1]</ref> that prompts for a common event model for media management. Our approach is to separate clearly the event metadata and the experiential aspect of this event, which depends on the user describing the event and the intended audience. Thus, we introduce a new entity in our model to store a particular description of an experience as the relation between an event and the media describing it:</p><formula xml:id="formula_5">Exp =&lt; Ev, M &gt;</formula><p>where Ev is a relation to the event in question and M is a set of relations to media describing the user's experience of this event.</p><p>In this context, the creation and structuring into complex events proves useful when a "story" about that event's experience has to be told. For example, in our example, Danda goes into the higher granularity events for the part of the story that her audience will favor. Conversely, she also chose to stay at a lower level of details when describing events that might be of less importance for that particular audience. However, for her own use when searching for media or when telling stories to other audiences about her experience, she is still interested in keeping as most details as possible in the events structure and metadata. A second application of this granular description of events in media management is the support provided when sharing an experience with a community (i.e., going from a local context to a shared or global context as discussed in Section 3). If we consider the "concert" event in our running example, more than one user will have attended the concert and annotated media of this concert with subjective event information; we could thus have the two event sub-structures shown in Fig. <ref type="figure">5</ref>. The two users have a different experience of the concert and have represented it as a set of different sub-events. If only the lower level of granularity was available, it would be difficult to say that the media describing the "Singer's Speech" and the "Great Song" are related. However, by providing information about the "concert" higher level event, general metadata is made available to help match between users local events as the subjective description of the time (t1 and t1 ) and location (l1 and l1 ) are more likely to overlap. The media of both users can be related by matching as much events as possible in a top-down -general to specific -fashion to reduce the social semantic gap. In particular, the sub-structure of events is slightly different, but by comparing the metadata of each event, the events "Opening Band" and "The Vandals", as well as "Main Band" and "The Ramadas", can be matched for instance with an ontology matching algorithm <ref type="bibr" target="#b7">[8]</ref>. In addition, once the matching is done, the management system can propose to the User 1 to add the "Break" sub-event to her own event structure and thus organise her local media in a more refined manner. After that, the media can be reclassified automatically within the sub-event, for instance with the get-specific algorithm <ref type="bibr" target="#b8">[9]</ref>. Thus, the users will be able to share, search and navigate new media of the events they have experienced more easily.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8">Related Work</head><p>Research fields spanning from Semantic Web <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b1">2]</ref> to Information Extraction <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b11">12]</ref> to Digital Libraries <ref type="bibr" target="#b12">[13]</ref> have recognised the key role played by the entities and their linking relationships.</p><p>In <ref type="bibr" target="#b9">[10]</ref>, entities are seen as atomic objects of reference and reasoning for Semantic Web applications which are described by a general conceptual model and categorized into types derived from a user-study. This work is part of the OKKAM project<ref type="foot" target="#foot_4">5</ref> , which proposes a framework where entities are assigned with a globally unique identifier to ease data integration and the development of innovative "entity-centric" applications <ref type="bibr" target="#b1">[2]</ref>. Categories for entities are also defined in <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b11">12]</ref>, together with guidelines for the accomplishment of named entity recognition and relation extraction tasks. The issue of linking together different kinds of entities in the Digital Library domain is addressed by Buckland <ref type="bibr" target="#b12">[13]</ref>, who advocates the need for a metadata infrastructure able to interconnect place-name gazetteers, biographical dictionaries, time period and subject indexes.</p><p>Furthermore, the concept of the "Web of Things<ref type="foot" target="#foot_5">6</ref> " (see <ref type="bibr" target="#b13">[14]</ref>) has recently emerged and efforts such as the Linking Open Data Initiative 7 entered the scene to address its principles. The role played by linked data for supporting users in tasks beyond the simple fact-finding and question answering (e.g., finding connections among people, places and events) is analyzed by looking at specific prototypes in <ref type="bibr" target="#b14">[15]</ref>.</p><p>In regards to the conceptual representation of events, research work exists on generic models as well as models tailored to domain-specific events (e.g., journalistic, historical, cultural-heritage, multimedia events): the generic E-model <ref type="bibr" target="#b15">[16]</ref> is extended to enable "event-centric" rather than "media-centric" media management systems <ref type="bibr" target="#b16">[17]</ref>; on the same line, the Eventory media repository <ref type="bibr" target="#b17">[18]</ref>, the MediAE ther system <ref type="bibr" target="#b18">[19]</ref> and a multimodal event browsing tool <ref type="bibr" target="#b19">[20]</ref> are proposed. The F Event Model <ref type="bibr" target="#b20">[21]</ref> proposes a formal model that, together with standard properties, supports mereological, causal, correlation relationships and interpretations of arbitrary events. The Event Ontology<ref type="foot" target="#foot_7">8</ref> , developed as part of a music ontology framework, supports music events (e.g., compositions, recordings, performances) but is not tied to such domain. With a journalistic perspective, EventML<ref type="foot" target="#foot_8">9</ref> provides an XML schema for exchanging news events among news agencies. The CIDOC ontology <ref type="bibr" target="#b21">[22]</ref> and the CultureSampo approach (see <ref type="bibr" target="#b22">[23]</ref>) aims to solve interoperability issues between metadata standards for heritage resources. In <ref type="bibr" target="#b23">[24]</ref>, most of the above-mentioned models are compared and an event ontology is proposed to fulfill the vision of a Linked Data Event Model 10 . The model is purposely kept minimal to capture the well-understood "when", "where", "what" and "who" facets of historical non-composite events; aspects defined as more interpretative dimensions are excluded. In this respect, our model differs from others since user-driven contextual metadata make events as always being subjective entities. Furthermore, by means of the experience entity we define relationships between events and media. This is also allowed in Eventory <ref type="bibr" target="#b17">[18]</ref> where such relationships are made explicit through ad-hoc interfaces for events, media and connection creation; however, we foresee a system where these types of relationships are deduced from the way the user describes her experience rather than being explicitly created.</p><p>For what specifically concerns the event's structural relationships -i.e., their compositionality -Rafatirad et al. <ref type="bibr" target="#b24">[25]</ref> design "subevent-of" relationships forming directed acyclic graphs over events and implement composition operators allowing to aggregate the spatial and temporal attributes of composite events from atomic events for which these attributes are known; Singh et al. <ref type="bibr" target="#b25">[26]</ref> regard the information needed to model compound events as semi-structured (dynamic) data and hence use XML to manage them: for example, a "group meeting" event is divided into compound events (e.g., "Introduction", "Presentation", "Discussion") and simple events (e.g., "ask question", "answer question"). The XML schema used to describe a compound event includes an "how" element which model its process, i.e., the simple events composing it. A hierarchical model to represent events at different granularities has been recently proposed in the domain of multimedia observation systems <ref type="bibr" target="#b26">[27]</ref>; here, "transient" events are detected from sensors datastreams and clustered into "atomic" events, these last being in turn composed into "compound" event. The model is however application-specific and aimed at reducing the semantic gap rather than what we defined as social semantic gap. On the same line, van Hage et al. <ref type="bibr" target="#b27">[28]</ref> present the Simple Event Model (SEM), applied in a Maritime Safety and Security use case to deduce simple behaviour events from sensor data. The model provides a minimal set of classes describing all the event's aspects, and add the notion of roles and the possibility to associate types to these classes thus to maintain the compatibility with external resources.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9">Conclusion</head><p>In this paper we present a general Event model to store the key metadata of an event. In particular, our model allows for the storage of complex subjective information relevant to the event's context.</p><p>We then show how such general model can be applied to the media management issue by introducing the experience entity that links an event with the media representing the user's experience of such an event. We believe that by clearly separating the event model from the experiential metadata of the event, this metadata is easier to use in heterogeneous applications.</p><p>In addition, by proposing a compositional model to represent the structural aspect of events, we allow for an easier alignment between users' personal descriptions of events and thus bridge the "social semantic gap" between different local representations of shared experiences.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1</head><label>1</label><figDesc>Fig. 1. Media and Social Semantic Gap</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Wedding Event Organisation</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. Event Structure for the Danda's trip</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Fig. 4 .</head><label>4</label><figDesc>Fig.4. Running example as a timeline.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>2 User 1 Fig. 5 .</head><label>215</label><figDesc>Fig. 5. Two Local Structures for the Same Concert Event</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Our running example is based on a real "blog" story found at: http://dandaworld. blogspot.com/2008/09/appunti-di-viaggio-my-journey-diary-11.html.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">http://www.glocal-project.eu/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">http://www.ict-pronto.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">http://eventmedia.cwi.nl/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">http://fp7.okkam.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">http://ercim-news.ercim.eu/content/view/343/536/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">http://linkeddata.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_7">http://motools.sf.net/event</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_8">http://iptc.org/</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgement</head><p>The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement n248984 GLOCAL: Event-based Retrieval of Networked Media.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Toward a common event model for multimedia applications</title>
		<author>
			<persName><forename type="first">U</forename><surname>Westermann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Jain</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE MultiMedia</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="page" from="19" to="29" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Entity name system: The backbone of an open and scalable web of data</title>
		<author>
			<persName><forename type="first">P</forename><surname>Bouquet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Stoermer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Niederee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mana</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of IEEE-ICSC</title>
				<meeting>of IEEE-ICSC</meeting>
		<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="554" to="561" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Casati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Varzi</surname></persName>
		</author>
		<title level="m">Events. Stanford Encyclopedia of Philosophy</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Events as shadowy entities</title>
		<author>
			<persName><forename type="first">U</forename><surname>Scheffler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Konstanzer Berichte: Logik und Wissenschaftstheorie</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<date type="published" when="1992">1992</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
		<title level="m">Contextual reasoning. Epistemologia 16(I Linguaggi e le Macchine</title>
				<imprint>
			<date type="published" when="1993">1993</date>
			<biblScope unit="page" from="345" to="364" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Local Models Semantics, or Contextual Reasoning = Locality + Compatibility</title>
		<author>
			<persName><forename type="first">C</forename><surname>Ghidini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence</title>
		<imprint>
			<biblScope unit="volume">127</biblScope>
			<biblScope unit="page" from="221" to="259" />
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Social roles and their descriptions</title>
		<author>
			<persName><forename type="first">C</forename><surname>Masolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Vieu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Bottazzi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Catenacci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Ferrario</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gangemi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of Knowledge Representation Workshop</title>
				<meeting>of Knowledge Representation Workshop</meeting>
		<imprint>
			<publisher>AAAI Press</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="267" to="277" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Semantic matching: algorithms and implementation</title>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Yatskevich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">JoDS, IX</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Formalizing the get-specific document classification algorithm</title>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Zaihrayeu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Kharkevich</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ECDL</title>
		<imprint>
			<biblScope unit="page" from="26" to="37" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Towards a general entity representation model</title>
		<author>
			<persName><forename type="first">B</forename><surname>Bazzanella</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Chaudhry</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Palpanas</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">SWAP</title>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Automatic content extraction english annotation guidelines for entities</title>
		<idno>6.6 2008.06.13</idno>
		<imprint>
			<date type="published" when="2008">2008</date>
			<publisher>Linguistic Data Consortium</publisher>
		</imprint>
	</monogr>
	<note type="report_type">Technical report</note>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">Automatic content extraction english annotation guidelines for relations</title>
		<idno>2008.04.28</idno>
		<imprint>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">6</biblScope>
			<biblScope unit="page">2</biblScope>
		</imprint>
		<respStmt>
			<orgName>Linguistic Data Consortium</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Technical report</note>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Description and search: metadata as infrastructure</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">K</forename><surname>Buckland</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Brazilian Journal of Information Science</title>
		<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Linked data -the story so far</title>
		<author>
			<persName><forename type="first">C</forename><surname>Bizer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Heath</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Berners-Lee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IJSWIS, Special Issue on Linked Data</title>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Interactive information access on the web of data</title>
		<author>
			<persName><forename type="first">L</forename><surname>Hardman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">V</forename><surname>Ossenbruggen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Troncy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Amin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Hildebrand</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">WebSci&apos;09</title>
				<imprint>
			<publisher>Society On-Line</publisher>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">E -a generic event model for event-centric multimedia data management in echronicle applications</title>
		<author>
			<persName><forename type="first">U</forename><surname>Westermann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Jain</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICDEW, IEEE Computer Society</title>
				<imprint>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page">106</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">Event-centric media management</title>
		<author>
			<persName><forename type="first">A</forename><surname>Scherp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Agaram</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Jain</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
			<publisher>SPIE</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Eventory -an event based media repository</title>
		<author>
			<persName><forename type="first">X</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Mamadgi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Thekdi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kelliher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Sundaram</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Semantic Computing. IEEE</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Medither: an event space for context-aware multimedia experiences</title>
		<author>
			<persName><forename type="first">S</forename><surname>Boll</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Westermann</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ACM SIGMM workshop on Experiential telepresence</title>
				<imprint>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="21" to="30" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Networked multimedia event exploration</title>
		<author>
			<persName><forename type="first">P</forename><surname>Appan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Sundaram</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ACM Multimedia</title>
				<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="40" to="47" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">F-a model of events based on the foundational ontology dolce+dns ultralight</title>
		<author>
			<persName><forename type="first">A</forename><surname>Scherp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Franz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Saathoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">K-CAP&apos;</title>
		<imprint>
			<biblScope unit="volume">09</biblScope>
			<biblScope unit="page" from="137" to="144" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">The cidoc conceptual reference model -a new standard for knowledge sharing</title>
		<author>
			<persName><forename type="first">M</forename><surname>Doerr</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Ore</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Stead</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Conceptual modeling</title>
		<imprint>
			<biblScope unit="page" from="51" to="56" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">An event-based approach for semantic metadata interoperability</title>
		<author>
			<persName><forename type="first">T</forename><surname>Ruotsalo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Hyvnen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ISWC</title>
				<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="407" to="420" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">Lode: Linking open descriptions of events</title>
		<author>
			<persName><forename type="first">R</forename><surname>Shaw</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Troncy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Hardman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ASWC</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">Event composition operators: Eco</title>
		<author>
			<persName><forename type="first">S</forename><surname>Rafatirad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gupta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Jain</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">EiMM&apos;09</title>
				<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="65" to="72" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Event-based modeling and processing of digital media</title>
		<author>
			<persName><forename type="first">R</forename><surname>Singh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Pack</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Jain</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CVDB&apos;04</title>
				<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">A hierarchical model for representation of events in multimedia observation systems</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">K</forename><surname>Atrey</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">EiMM&apos;09</title>
				<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="57" to="64" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<analytic>
		<title level="a" type="main">Combining ship trajectories and semantics with the simple event model (sem)</title>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">R</forename><surname>Van Hage</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Malaisé</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>De Vries</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Schreiber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Van Someren</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">EiMM&apos;09</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
