<!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>A Framework for Flexible User Pro le Mashups</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Fabian Abel</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dominikus Heckmann</string-name>
          <email>heckmann@dfki.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eelco Herder</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jan Hidders</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Geert-Jan Houben</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniel Krause</string-name>
          <email>krauseg@l3s.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Erwin Leonardi</string-name>
          <email>e.leonardig@tudelft.nl</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kees van der Slujis</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DFKI GmbH</institution>
          ,
          <addr-line>Saarbrucken</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Computer Science, Eindhoven University of Technology</institution>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>L3S Research Center, Leibniz University Hannover</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Web Information Systems</institution>
          ,
          <addr-line>TU Delft</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2009</year>
      </pub-date>
      <fpage>22</fpage>
      <lpage>26</lpage>
      <abstract>
        <p>Exploiting the rich traces of users' Web interaction promises to enable cross-application user modeling techniques, which is in particular interesting for applications that have a small user population or that are used infrequently. In this paper we present a framework for the e ective interchange of user pro les. In addition to derivation rules for user pro le reasoning, the framework employs exible mash-ups of RSS-based user data streams for combining heterogeneous user data in a Web 2.0 environment.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        With the increased use of search engines, e-commerce systems and social
networking sites { with famous examples such as Amazon, Facebook, Flickr,
Delicious and Google { user modeling and Web personalization has evolved from a
rather marginal activity to a mature technology that is exposed to the majority
of Web users on a daily basis. Most techniques are based on collaborative
ltering and social network analysis [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. What they have in common is that they are
rather straightforward and depend on a su ciently large number of users that
regularly interact with the system [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>Apart from the major players in the eld, many systems cannot boast on
a large user base. These systems vary from startups to well-established sites
that serve a specialized audience. As an example, e-learning systems inherently
have a limited audience, in particular if the system is speci cally used by one
institution. For these stakeholders, it would be bene cial to have user pro le
information from other applications. Recent research suggests that, if carefully
designed and tested, heterogeneous types of data can be used for reliably
classifying users [3, ?]. Other motivations for cross-application user modeling include the
synchronization of recommendations and user interaction between applications
and better support of user migration.</p>
      <p>
        Obviously, the idea of cross-application user modeling is not new. In the
1990s several generic user modeling servers have been developed, to be used by
a wide range of applications (for example [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). One of the major reasons that
this approach has never been successful is that these servers were centralized,
making use of prede ned structures. By contrast, user models di er signi cantly
between applications, depending on the adaptation goals, the context of use,
privacy concerns, the design philosophy and many other factors.
      </p>
      <p>New trends from the Web 2.0 as well as the related work, as will be discussed
in Section 2, motivate an infrastructure for cross-application user modeling. This
infrastructure, which we introduce in Section 3, is heavily inspired by social
networking approaches and is based on the assumption that adaptive systems (or
rather the system administrators) themselves are the ones who know best what
the system needs. The infrastructure relies on the brokerage of user models, with
system administrators searching, discussing, adopting, rating and recommending
third parties' user models. Section 4 outlines how to use the framework to reason
on distributed user pro les and demonstrates how user pro les can be mashed-up
by combining RSS feeds in so-called user pipes.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Background and Related Work</title>
      <p>
        As described in Tim O'Reilly's Web 2.0 design patterns [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], small sites with
a small user population and speci c demands make up the bulk of the Web
2.0 domain. Whereas the exchange of login credentials is already facilitated by
initiatives such as OpenID1, still in most cases users need to build their user
pro les from scratch for every application. A recent trend is the combination
of functionality from multiple Web 2.0 applications in so-called mashups. For
mashups, the ability to share user pro les is particularly essential for a better
integration and cooperation between the single applications.
      </p>
      <p>
        For the exchange and interpretation of user pro le data, common semantics
user pro le statements are needed [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Possible formats for user pro les include
the General User Model Ontology (GUMO) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] or Friend of a Friend (FOAF) [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
However, as we have seen in the introduction of this paper, these kinds of
prede ned and static user pro le ontologies do not su ciently cater for the diverse
needs of applications. Therefore, we argue that these types of shared models
should rather be built bottom-up, starting from successful implementations in
speci c systems [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        As a further development, we can see a shift from author-prede ned
adaptation rules to collaborative ltering techniques and the use of Web 2.0 interaction
mechanisms [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. With a huge pool of data, many candidate user groups to
compare the user with, and several methods at hand, it becomes even more important
to experiment with and optimize the conceptual adaptation decisions [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        In essence, there are two ways to ensure interoperability between two adaptive
systems and their user models. The rst approach involves a lingua franca, an
agreement between all parties on a common representation and semantics [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
As described in the introduction, this is the philosophy underlying the generic
user model server approach, used by CUMULATE [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] or PersonIs [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Given
the wide variety in system objectives and the associated user models, generic
      </p>
      <sec id="sec-2-1">
        <title>1 http://openid.net/</title>
        <p>user model servers have never gained wide acceptance. An alternative approach,
which is more exible, involves conversion between the di erent systems' user
models.</p>
        <p>
          Conversion allows for exible and extensible user models, and for systems to
join into a platform. Moreover, in contrast to a xed lingua franca approach,
conversion is suitable for `open-world user modeling', which is not restricted to
one speci c set of systems [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. This exibility comes at a price, though. In
addition to possibly losing information in the conversion process, it might be that
models are simple incompatible (in the sense that there is no suitable mapping)
or that mappings are incomplete (information required in one model is not
available in the other). Given that there are suitable mappings, the observations in
the di erent systems may lead to contradictions [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. Several methods for
conict detection and resolution are conceivable, among others reliability weighting
and majority voting - again, which method to use, may be a subjective design
decision.
        </p>
        <p>
          As pointed out by [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ], computer-based representation of provenance data
is crucial for users who want to analyze, reason, and decide whether or not
they trust electronic data. In the article, the generic concept of p-statements
is explained: each statement should contain a track record of the input data,
the processing and a description of the output data. With this information,
a derivation record can be built for analysis purposes. The DCMI Metadata
Terms [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] is a collection of properties and classes together with vocabulary
and syntax encoding schemes that can be applied to describe the provenance of
data as well. The DCMI terms allow to describe metadata of things, such as the
creator, time of creation, copyright and modi cations.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>A Framework for User Modeling 2.0</title>
      <p>Results from the preceding section provide support for the exchange of user
models between applications. From the related work we have seen that incorporating
user pro le information from other contexts is not a straightforward process,
though. The poor take-up of the generic user modeling servers, developed in the
1990s, suggests that a centralized approach, with prede ned ontologies, does not
cater the needs of the multitude of adaptive systems, which are very
heterogeneous in nature.</p>
      <p>Based on the above, we designed a framework that facilitates the
brokerage of user pro le information and user model representations. This framework,
which we call the Grapple User Modeling Framework (GUMF), is designed to
meet the following requirements. First, various types of systems should be able
to connect to the framework. Further, the framework should provide a exible
user model format that allows for new types of statements and derivation rules.
Su cient metadata should be given to indicate its origin, contents and
validity. The browsing and searching of user data or model extensions, provided by
the connected systems, should be supported by rating mechanisms. As several
systems may provide competing models of, for example, user interests, and as
the quality of these models can vary signi cantly it is important that a system</p>
      <p>Add-On</p>
      <p>Functionality
Adaptive System 1</p>
      <p>Adaptive System 2</p>
      <p>Core
Ontology</p>
      <p>Universal
Reasoners</p>
      <p>Event</p>
      <p>Loggers
UM 1</p>
      <p>User Modeling Broker
manage
explore</p>
      <p>providdaeta
UM 2
ery ta
qu da
Third-Party UM</p>
      <p>UM 3</p>
      <p>Registered Systems
Available UM Data
Ontology Extensions</p>
      <p>User Events</p>
      <p>UM Editors
Browsing,
Rating
administrator (i.e. a user of the framework) can take a motivated decision which
alternative is most suitable for his personalization purposes.</p>
      <p>The core element of the framework can be considered a broker, which provides
the means for other systems to share and make use of their user data. In this
section we provide an overview of the elements that are needed for setting up
this framework.</p>
      <sec id="sec-3-1">
        <title>3.1 Architecture</title>
        <p>In Figure 1, a generic overview of the GUMF architecture is depicted. The
central element of the framework is the Grapple User Modeling Broker (GUMB),
which manages the communication between the connected systems. The broker
keeps track of the registered systems, the available user model data and
ontology extensions. Further, it keeps a centralized repository of user events. The
framework provides Web-based administrative interfaces for managing the
system con guration and for exploring the available user data streams, reasoning
mechanisms and ontology extensions. The target audience of these interfaces
consists of the administrators and programmers of client (adaptive) systems, in
order to nd and incorporate suitable user data streams and to o er their own
data streams. For most mapping, merging and reasoning tasks, administrators
can utilize generic reasoning plugins (cf. Section 4) and hence generate user
prole data in a format that perfectly t their applications' needs. For more speci c
reasoning tasks, administrator can create own reasoning plugins an provide them
to the GUMF community. Once con gured, the client systems can exchange user
data without human intervention. The provision of data takes place in the form
of statements, of which the structure is explained in more detail in Section 3.2.</p>
        <p>The querying of user data { summarized in statements { is realized through
three alternative interfaces. The RESTful interface provides a light-weight
querying approach for retrieving statements that match a certain simple pattern. A
more elaborate interface is provided by a SOAP interface, which is more exible,
property description</p>
        <p>ID The globally unique ID of the statement.</p>
        <p>In the current version of the UM ontology we di erentiate between gc:Statement,
type which is a basic user pro le statement, and gc:Observation, which is a
specialization of gc:Statement and models a (user) observation made in some application.
subject The entity (usually the user) the statement is about.</p>
        <p>Refers to a property (of a domain ontology) that either characterizes the subject
predicate (e.g. foaf:interest or k:hasKnowledge) or describes some action the subject has
performed (e.g. nop:hasBookmarked or nop:hasClicked).
object The value of the predicate (e.g. \ItalianFood" or dbpedia:semantic web).
created Speci es when the statement was created.
creator Refers to the entity that created the statement. In case of a gc:Observation it
identi es the entity that reported the observation.
temporal Allows to de ne temporal constraints on the validity of the statement.
evidence If a statement was produced by a reasoning process then evidence can be used to
show how the statement was deduced.</p>
        <p>rating The rating of a statement indicates the level of trust in the statement.
at the cost of a more complicated syntax and communication costs. A third
interface allows applications to subscribe to an RSS-based data stream that matches
a query, to be noti ed upon changes. The latter interface is particularly useful
for event-driven personalization mechanisms, which depend on events in other</p>
        <p>
          The GUMF architecture is inspired by the Personal Reader Framework [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ],
with as main enhancements the extensible user modeling ontology format,
exible query interfaces and a community-based way of sharing and ranking user
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>User Modeling Ontology</title>
        <p>
          The Grapple User Modeling Ontology speci es the lingua franca for exchanging
user pro le information and user observations in a User Modeling 2.0
infrastructure. It follows the approach of the General User Model Ontology [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] (GUMO)
and UserRDF [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ], as it is built upon the notion of rei ed subject-predicate-object
statements. The subject models the entity (usually the user) that the statement
is about. The predicate refers to a property that either characterizes the subject
(e.g. foaf:interest or k:hasKnowledge ) or describes some action the subject has
performed (e.g. nop:hasBookmarked or nop:hasClicked ). The object contains the
corresponding value (e.g. \ItalianFood" or dbpedia:semantic web). Each
statement has a globally unique ID and is enriched with metadata (see Table 1), such
as the creation date or details about the provenance of the statement.
gc = http://www.grapple-project.org/grapple-core/
foaf = http://xmlns.com/foaf/0.1/
gc:Statement {
gc:id: gc:statement-peter-2009-01-01-3234190;
gc:user: http://www.peter.de/foaf.rdf#me;
gc:predicate: foaf:interest;
gc:object: http://en.wikipedia.org/wiki/Italy;
}
        </p>
        <p>
          In the example above, the subject (gc:user), predicate, and object refer to
entities that are not part of the Grapple Core ontology. gc:user identi es the user
Peter by referring to his FOAF pro le, which is a separate document located
at "http://www.peter.de/foaf.rdf". The value of the predicate is "foaf:interest".,
which is a property de ned in the FOAF ontology [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. To nd out about the
actual meaning of "foaf:interest", one has to look up the FOAF ontology2:
&lt;rdf:Property rdf:about="http://xmlns.com/foaf/0.1/interest"
vs:term_status="testing"
rdfs:label="interest"
rdfs:comment="A page about a topic of interest to this person."&gt;
&lt;rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/&gt;
&lt;rdfs:domain rdf:resource="http://xmlns.com/foaf/0.1/Person"/&gt;
&lt;rdfs:range rdf:resource="http://xmlns.com/foaf/0.1/Document"/&gt;
&lt;rdfs:isDefinedBy rdf:resource="http://xmlns.com/foaf/0.1/"/&gt;
&lt;/rdf:Property&gt;
        </p>
        <p>The de nition of "foaf:interest" gives us the actual meaning of the Grapple
statement. The comment describes the semantics of the predicate, to be read by
people that want to use the property. Making use of the de nitions of the domain
and range, we can deduce that "http://www.peter.de/foaf.rdf#me" is of the type
"foaf:Person", that "http://en.wikipedia.org/wiki/Italy" is a "foaf:Document"
and that the predicate "foaf:interest" re ects `A page about a topic of interest
to this person'.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>User Pro le Reasoning</title>
      <p>The Grapple User Modeling Framework allows to dynamically utilize reasoning
plugins to enable user pro le reasoning. In this section we present two generic
solutions that can be utilized directly by the GUMF client applications: (1) a
rather classical rule-based approach and (2) a novel approach, which we call
User Pipes, that allows user pro le reasoning by mashing up di erent user
prole data streams. However, client administrators can also create own reasoning
plugins and share them with the community. A user interface within the client
administrator backend allows to search for and publish own reasoning plugins.
4.1</p>
      <sec id="sec-4-1">
        <title>Reasoning Plugins</title>
        <p>Reasoning plugins are software components that can be integrated into the
Grapple User Modeling Framework (GUMF). In general, they deduce new information
about a user based on existing user pro le data or based on some observations.
Reasoning plugins can come in di erent avors. For example, a plugin might
gather and align user data from di erent social networking services in order to
create a more comprehensive user pro le.</p>
        <p>The rst generic reasoning plugin is rule-based and applies derivation rules,
which can be de ned and adjusted by client applications. These derivation rules
enable GUMF to generate new Grapple statements. Rules allow to express simple
2 More precisely, the ontology that is identi ed via foaf = http://xmlns.com/foaf/0.1/
types of inference in terms of premise-conclusion rules that derive new statements
from the existence of other statements. These rules can, for example, (i) infer
statements that embody new knowledge, (ii) they can be used to map between
di erent ontologies or (iii) they describe how to solve problems where
statements or rules con ict with each other. A simple derivation rule that infers new
knowledge about a user might express the following: If a user has bookmarked
a website that has topic t then the user is interested in t. Such a rule can, for
example, simply be formulated as a SPARQL query:
PREFIX foaf: &lt;http://xmlns.com/foaf/0.1/&gt;
PREFIX gc: &lt;http://www.grapple-project.org/grapple-core/&gt;
PREFIX gnop: &lt;http://www.grapple-project.org/nop/&gt;
CONSTRUCT { gc:derivedStatement
gc:derivedStatement
gc:derivedStatement
gc:user ?user .
gc:predicate foaf:interest .</p>
        <p>gc:object ?topic }
WHERE {
?originalStatement
?originalStatement
?originalStatement
?document
gc:user ?user
gc:predicate gnop:hasBookmarked .
gc:object ?document .</p>
        <p>foaf:topic ?topic . }</p>
        <p>A mapping rule could simply map one value to another value or it can
compose a new value from other values or decompose one value in di erent separate
values. Con ict resolution rules can be used to de ne preferences among di erent
types of statements or preferences among di erent rules.
4.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>User Pipes</title>
        <p>In addition to the rule-based approach described in the section above, GUMF
enables deduction of user pro les also by mashing up di erent (user pro le)
data streams in RDF or RSS-format by utilizing Semantic Web Pipes3 or Yahoo
Pipes4. In this chapter, we focus on the processing of RSS data by utilizing
Yahoo pipes as this enables the usage of a huge amount of structured data on
the web. Di erent RSS streams are syndicated to so-called User Pipes.</p>
        <p>How this works is shown by our GUMF demonstrator5. A speci c pro le
stream searchedFor of the user fabian can be retrieved by requesting
/user/fabian/predicate/searchedFor. An extract of the data stream is given as follows.
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;rdf:RDF ...&gt;
&lt;channel rdf:about="http://semweb.kbs.uni-hannover.de:8082/grapple-umf/user/fabian"&gt;
&lt;title&gt;GUMF data stream matching the query 'user = fabian'&lt;/title&gt;
&lt;link&gt;http://semweb.kbs.uni-hannover.de:8082/grapple-umf/user/fabian&lt;/link&gt;
&lt;items&gt;
&lt;rdf:Seq&gt;
&lt;rdf:li rdf:resource="http://semweb.kbs.uni-hannover.de:8082/grapple-umf/62715"/&gt;
&lt;rdf:li rdf:resource="http://semweb.kbs.uni-hannover.de:8082/grapple-umf/63526"/&gt;
...</p>
        <p>&lt;/rdf:Seq&gt;
&lt;/items&gt;
&lt;/channel&gt;</p>
        <sec id="sec-4-2-1">
          <title>3 http://pipes.deri.org/ 4 http://pipes.yahoo.com 5 Available at http://semweb.kbs.uni-hannover.de:8082/grapple-umf/</title>
          <p>This data stream can be combined with other data streams to deduce new
user pro le information. For example, it can be combined with information from
the feed /user/fabian/predicate/interest to deduce whether the user's interests
and search activities are thematically similar or it can even be mashed up with
other RSS feeds from the Web.</p>
          <p>To demonstrate how meaningful streams can be created by embedding pro le
data from social networking sites, we created a simple user pipe6 that combines
the search activity stream listed above with the latest bookmarks that the user
created at Delicious7. Figure 2 shows the editor view of the user pipe. The given
user pipe detects those keywords that a user applied for both search and tagging
of his latest bookmarks, which is expressed via the following YQL query.
SELECT title, link, description, subject, predicate, object FROM rss WHERE url in
6 Available at http://pipes.yahoo.com/userpipes/gumf showcase
7 http://feeds.delicious.com/v2/rss/fabianabel
('http://semweb.kbs.uni-hannover.de:8082/grapple-umf/user/fabian/predicate/searchedFor')
AND object in
(select category from rss where url in ('http://feeds.delicious.com/v2/rss/fabianabel') )</p>
          <p>The result of the YQL query is then passed to a component that tries to map
the detected keywords to Wikipedia articles that further explain the concepts
that are referred by the keywords. In the last stage, an Item Builder component is
used to generate new Grapple statements. Similar to the example in Section 3.2,
the above item makes use of the FOAF vocabulary (foaf:interest ) to express
that the user is interested in http://en.wikipedia.org/wiki/Trento (cf. bottom of
Fig. 2):
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
...
&lt;item rdf:about="http://www.grapple-project.org/umf/1215715049-14264674241239174361456"&gt;
&lt;title&gt;http://en.wikipedia.org/wiki/Trento&lt;/title&gt;
&lt;gc:subject&gt;http://fabian.myopenid.com&lt;/gc:subject&gt;
&lt;gc:predicate&gt;http://xmlns.com/foaf/0.1/interest&lt;/gc:predicate&gt;
&lt;gc:object&gt;http://en.wikipedia.org/wiki/Trento&lt;/gc:object&gt;
&lt;gc:creator&gt;http://pipes.yahoo.com/userpipes/gumf_showcase&lt;/gc:creator&gt;
&lt;/item&gt;
...</p>
          <p>The bene t of the user pipe approach is that user pipes result in user pro le
streams that can again be used by other pro le reasoners, which allows for exible
and extensible user pro le reasoning. For publicly available data streams it is
also possible to directly use the Yahoo Pipe editor, which provides an easy
dragand-drop user interface to process, combine, and perform various operations on
data streams. This means that not only programmers or experts familiar with
SPARQL or rule-based languages are enabled to create pro le reasoners, but
also leisure user as they can create such reasoners (user pipes) visually.</p>
          <p>
            The critical point of this approach is the immensely huge amount of RSS
data on the Web that could slow down the processing of a pipe. Therefore, we
are going to explore caching strategies (e.g. the precompute pipes regulary and
deliever the cached results) as proposed in [
            <xref ref-type="bibr" rid="ref13">13</xref>
            ] and will conduct performance
measures as well.
5
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusions and Future Work</title>
      <p>In this paper we motivated and introduced a framework for cross-application
user modeling. Based on several pieces of earlier work, the framework provides
a domain-independent, decentralized approach for combining several user
models. In a collaborative manner, the connected systems can create, share, select,
mashup, adopt and rate their user models, supported by a basic infrastructure
that includes search and browse facilities, editors and universal reasoning
mechanisms.</p>
      <p>Although the framework provides the basic infrastructure for cross-application
modeling, its success depends on the take-up by a critical mass and the
availability of the necessary tools. In the GRAPPLE project, we are currently integrating
the framework, to be used by a number of di erent e-learning systems. By
evaluation and experimentation, we expect to nd additional requirements and success
factors for building an ecology of adaptive systems that exchange parts of their
user models.
Acknowledgements The work presented in this paper has been sponsored by
the EU FP7 STREP Project GRAPPLE.</p>
    </sec>
    <sec id="sec-6">
      <title>References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Frias-Martinez</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Magoulas</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Macredie</surname>
          </string-name>
          , R.:
          <article-title>Modeling human behavior in user-adaptive systems: Recent advances using soft computing techniques</article-title>
          .
          <source>Expert Systems with Applications</source>
          <volume>29</volume>
          (
          <year>2005</year>
          )
          <volume>320</volume>
          {
          <fpage>229</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bilenko</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>White</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Mining the search trails of sur ng crowds: Identifying relevant websites from user activity</article-title>
          .
          <source>In: Proc. WWW2008</source>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Korth</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plumbaum</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>A framework for ubiquitous user modeling</article-title>
          .
          <source>In: Proc. Information Reuse and Integration</source>
          <year>2007</year>
          . (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Kobsa</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koenemann</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pohl</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Personalized hypermedia presentation techniques for improving customer relationships</article-title>
          .
          <source>The Knowledge Engineering Review</source>
          <volume>16</volume>
          (
          <issue>2</issue>
          ) (
          <year>2001</year>
          )
          <volume>111</volume>
          {
          <fpage>155</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Oreilly</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>What is web 2.0: Design patterns and business models for the next generation of software</article-title>
          .
          <source>Social Science Research Network Working Paper Series</source>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ankolekar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , Krotzscha,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Trana</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Vrandecic</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          :
          <article-title>The two cultures: Mashing up web 2.0 and the semantic web</article-title>
          .
          <source>In: Web Semantics: Science, Services and Agents on the World Wide Web</source>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Heckmann</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schwartz</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brandherm</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmitz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>von</surname>
            <given-names>WilamowitzMoellendor</given-names>
          </string-name>
          , M.:
          <article-title>Gumo - the general user model ontology</article-title>
          .
          <source>In: Proc. of the 10th Int. Conf. on User Modeling</source>
          , Edinburgh, UK (
          <year>2005</year>
          )
          <volume>428</volume>
          {
          <fpage>432</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Brickley</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <source>FOAF Vocabulary Speci cation 0</source>
          .91.
          <string-name>
            <surname>Namespace</surname>
            <given-names>document</given-names>
          </string-name>
          ,
          <source>FOAF Project (November</source>
          <year>2007</year>
          ) http://xmlns.com/foaf/0.1/.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Paramythis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Loidl-Reisinger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Adaptive learning environments and e-learning standards</article-title>
          .
          <source>Electronic J. of e-Learning</source>
          <volume>2</volume>
          (
          <issue>2</issue>
          ) (
          <year>2004</year>
          )
          <article-title>Paper 11</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Chatti</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jarke</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The future of e-learning: a shift to knowledge networking and social software</article-title>
          .
          <source>Int. J. Knowledge and Learning</source>
          <volume>3</volume>
          (
          <issue>4</issue>
          /5) (
          <year>2007</year>
          )
          <volume>404</volume>
          {
          <fpage>420</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Nielsen</surname>
          </string-name>
          , J.:
          <article-title>Personalization is over-rated</article-title>
          .
          <source>Alertbox (October</source>
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Stewart</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Celik</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cristea</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ashman</surname>
          </string-name>
          , H.:
          <article-title>Interoperability between aeh user models</article-title>
          .
          <source>In: Proc. APS</source>
          <year>2006</year>
          .
          <article-title>(</article-title>
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Yudelson</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brusilovsky</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zadorozhny</surname>
          </string-name>
          , V.:
          <article-title>A user modeling server for contemporary adaptive hypermedia: An evaluation of the push approach to evidence propagation</article-title>
          .
          <source>In: 11th International Conference on User Modeling</source>
          . (
          <year>2007</year>
          )
          <volume>27</volume>
          {
          <fpage>36</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Assad</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carmichael</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kay</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kummerfeld</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Personisad: Distributed, active, scrutable model framework for context-aware services</article-title>
          . (
          <year>2007</year>
          )
          <volume>55</volume>
          {
          <fpage>72</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Aroyo</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dolog</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Houben</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kravcik</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Naeve</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nilsson</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Interoperability in pesonalized adaptive learning</article-title>
          .
          <source>J. Educational Technology &amp; Society</source>
          <volume>9</volume>
          (
          <issue>2</issue>
          ) (
          <year>2006</year>
          )
          <volume>4</volume>
          {
          <fpage>18</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Moreau</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Groth</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vazques-Salceda</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ibbotson</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jiang</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Munroe</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rana</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schreiber</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tan</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varga</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>The provenance of electronic data</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>51</volume>
          (
          <issue>4</issue>
          ) (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>DCMI</given-names>
            <surname>Usage</surname>
          </string-name>
          <article-title>Board: DCMI Metadata Terms</article-title>
          . DCMI Recommendation, Dublin Core Metadata Initiative (
          <year>January 2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Henze</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krause</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Personalized access to web services in the semantic web</article-title>
          .
          <source>In: SWUI 2006 - 3rd International Semantic Web User Interaction Workshop</source>
          , Athens, Georgia, USA (nov
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Abel</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Henze</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krause</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plapper</surname>
            ,
            <given-names>D.:</given-names>
          </string-name>
          <article-title>User modeling and user pro le exchange for semantic web applications</article-title>
          .
          <source>In: 16th Workshop on Adaptivity and User Modeling in Interactive Systems</source>
          , Wuerzburg, Germany. (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>