Skyline Queries
| dc.contributor.author | Hose, Katja | |
| dc.date.accessioned | 2018-01-10T13:20:52Z | |
| dc.date.available | 2018-01-10T13:20:52Z | |
| dc.date.issued | 2016 | |
| dc.description.abstract | Many applications face the problem that users are overwhelmed by the large amount of available data. In some cases an objective ranking function can be used to order data items by their relevance – similar to the top 10 results displayed by a Web search engine. Other applications, however, aim at considering more diverse preferences and multiple criteria to help users find good results. Such applications can benefit from skyline queries.The best known example use case for a skyline query is a hotel booking scenario where users are looking for hotels. Assume many hotels are available and the user wants to find one based on two criteria: distance to the beach and price per night. Further assume that the user is unable to say which of these criteria is more important. So, we need to look for hotels representing a good combination of both criteria. The skyline consists of all hotels that represent a “good” combinations of both criteria. For each of the other hotels, there is always at least one hotel in the skyline that is better with respect to the two criteria. So, being presented the skyline, the user gets an overview of the available hotels and can make the final decision with respect to her personal preferences for the two criteria. No matter how the user will eventually weigh her personal preferences, she will find her favorite hotel in the skyline.This article gives a short introduction to skyline queries, their main characteristics, and basic ways of processing them. | |
| dc.identifier.pissn | 1610-1995 | |
| dc.identifier.uri | https://dl.gi.de/handle/20.500.12116/11787 | |
| dc.publisher | Springer | |
| dc.relation.ispartof | Datenbank-Spektrum: Vol. 16, No. 3 | |
| dc.relation.ispartofseries | Datenbank-Spektrum | |
| dc.title | Skyline Queries | |
| dc.type | Text/Journal Article | |
| gi.citation.endPage | 251 | |
| gi.citation.startPage | 247 |