P. 1
David Vallet's Master Thesis

David Vallet's Master Thesis

4.0

|Views: 525|Likes:
Published by dvallet
Master Theshis on personalization and use of context on personalization techinques
Master Theshis on personalization and use of context on personalization techinques

More info:

Published by: dvallet on Feb 20, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/08/2014

pdf

text

original

Previously analyzed implementation-level representation of semantic runtime context is

defined as a set of concepts that have been involved, directly or indirectly, in the

interaction of a user u with the system during a retrieval session. Therefore, at each

point t in time, context can be represented as a vector C(u,t)∈[0,1]|O|

of concept

weights, where each x∈O is assigned a weight Cx(u,t)∈[0,1]. This context value may be

interpreted as the probability that x is relevant for the current semantic context.

Additionally, time is measured by the number of user requests within a session. Since

the fact that the context is relative to a user is clear, in the following we shall often omit

this variable and use C(t), or even C for short, as long as the meaning is clear.

In our approach, C(t) is built as a cumulative combination of the concepts involved in

successive user requests, in such a way that the importance of concepts fades away

with time. This simulates a drift of concepts over time, and a general approach towards

achieving this follows. This notion of context extraction is extracted from the implicit

feedback area [127], concretely our model is part of the wpq implicit feedback models,

as one that uses a time variable and gives more importance to items occurring close in

time [32].

Right after each user’s request, a request vector Req(t) ∈ CO is defined. This vector may

be:

Personalized Information Retrieval in Context Using Ontological Knowledge

40

The query concept-vector, if the request is a query.

A concept-vector containing the topmost relevant concepts in a document, if
the request is a “view document” request.

The average concept-vector corresponding to a set of documents marked as
relevant by the user, if the request is a relevance feedback step.

If the request is a “browse the documents under a category c” request, Req(t) is

the sum of the vector representation of the topic c (in the [0,1]|O|

concept

vector-space), plus the normalized sum of the metadata vectors of all the

content items belonging to this category.

As the next step, an initial context vector C(t) is defined by combining the newly

constructed request vector Req(t) from the previous step with the context C(t–1), where

the context weights computed in the previous step are automatically reduced by a

decay factor ξ, a real value in [0,1], where ξ may be the same for all x, or a function of

the concept or its state. Consequently, at a given time t, we update Cx(t) as

Cx(t) = ξ · Cx (t – 1) + (1 – ξ) · Reqx(t)

Equation 5. Runtime semantic context

The decay factor will define how many action units will be a concept considered, and

how fast a concept will will be “forgotten” by the system. This may seem similar to

pseudo-relevance feedback, but it is not used to reformulate the query, but to focus the

preference vector as shown next.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->