<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>P084 - ISTA 2006 - Information Systems Technolopgy and its Applications</title>
<link href="http://dl.gi.de/handle/20.500.12116/24180" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/24180</id>
<updated>2026-07-23T11:14:40Z</updated>
<dc:date>2026-07-23T11:14:40Z</dc:date>
<entry>
<title>A JXTA-based music information retrieval system</title>
<link href="http://dl.gi.de/handle/20.500.12116/24196" rel="alternate"/>
<author>
<name>Jung, Hyosook</name>
</author>
<author>
<name>Park, Seongbin</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24196</id>
<updated>2019-08-12T12:49:20Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">A JXTA-based music information retrieval system
Jung, Hyosook; Park, Seongbin
Karagiannis, Dimitris; Mayr, Heinrich C.
In this paper, we present a JXTA-based system for contents-based music information retrieval. The system finds matching melodies from a set of XML documents that encode music contents. The XML documents are stored in a native XML database and XPath query language is used to extract the information about the structure of music data. The matching algorithm utilizes the geometric hashing technique  [Wo97] by analyzing geometric properties of both XML documents and music contents. The system preprocesses extracted music contents and stores the information about melody patterns in a relational database. When a user sends a query about a melody, it searches melody patterns that have similar geometric properties as the query melody.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Use of tailored process models to support ERP end-users</title>
<link href="http://dl.gi.de/handle/20.500.12116/24197" rel="alternate"/>
<author>
<name>Kristiansen, Renate</name>
</author>
<author>
<name>Gulla, Jon Alte</name>
</author>
<author>
<name>Trætteberg, Hallvard</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24197</id>
<updated>2019-08-12T12:49:20Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">Use of tailored process models to support ERP end-users
Kristiansen, Renate; Gulla, Jon Alte; Trætteberg, Hallvard
Karagiannis, Dimitris; Mayr, Heinrich C.
Modeling is essential for the success of any ERP project and early in the project a considerable amount of time and money is invested in designing and redesigning business processes. However, the models developed in this period, do not take the leap from the developers' desktops, and generally offers no support for the end-user while performing daily work. The construction of the user interface of an ERP system reflects the organizations functional areas, making the functional aspect predominant. The process aspect in a user's work is lost, and the user gets no conceptualization on how his contributions fit into the overall business processes. In this paper we suggest that tailored views of the process models developed early in the ERP project should be made available to the end-users while working with the ERP system. We show examples on models developed during an ERP implementation project at a Norwegian manufacturing company, and show how these can be tailored according to an end user's role, the current context and what instance she finds herself in.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Fragments for composing collaborative systems</title>
<link href="http://dl.gi.de/handle/20.500.12116/24195" rel="alternate"/>
<author>
<name>Hawryszkiewycz, I. T.</name>
</author>
<author>
<name>Henderson-Sellers, B.</name>
</author>
<author>
<name>Tran, N.</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24195</id>
<updated>2019-08-12T12:49:20Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">Fragments for composing collaborative systems
Hawryszkiewycz, I. T.; Henderson-Sellers, B.; Tran, N.
Karagiannis, Dimitris; Mayr, Heinrich C.
Collaborative systems are characterized by groups or communities jointly working to accomplish some organizational goal. Members of the communities must coordinate their efforts to ensure that such goals are met. Development of collaborative systems can be facilitated by identifying common aspects of such coordination and by constructing product method fragments that can be composed into working systems. This paper uses a metamodel to provide a basis for such fragments, describing the metamodel and defining typical fragments.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>A generic ontology of rational negotiation</title>
<link href="http://dl.gi.de/handle/20.500.12116/24192" rel="alternate"/>
<author>
<name>Ermolayev, Vadim</name>
</author>
<author>
<name>Keberle, Natalya</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24192</id>
<updated>2019-08-12T12:49:19Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">A generic ontology of rational negotiation
Ermolayev, Vadim; Keberle, Natalya
Karagiannis, Dimitris; Mayr, Heinrich C.
The paper presents the generic conceptual framework for modeling rational negotiation processes. The central piece of the presented work is the upper-level negotiation ontology. This ontology is designed to be capable to model the arbitrary types of negotiation dialogues by providing the upper-level namespace for that. The models of the specific negotiation types refine this namespace by providing the instances of its concepts, applying additional restrictions on the properties, possibly adding new subclasses and properties. The approach to model negotiations with the Generic Negotiation Ontology (GNO) is initially evaluated by applying to contracting negotiation type. The choice of the negotiation type for the evaluation is suggested by the fact that contracting negotiations are the typical encounters among the agents taking part in the simulation of a Dynamic Engineering Design Process (DEDP). This modeling activity is performed in the frame of our PSI project1.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
</feed>
