Inproceedings365: Unterschied zwischen den Versionen
K (Added from ontology) |
K (Wikipedia python library) |
||
| (2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| Zeile 2: | Zeile 2: | ||
|ErsterAutorNachname=Stojanovic | |ErsterAutorNachname=Stojanovic | ||
|ErsterAutorVorname=Nenad | |ErsterAutorVorname=Nenad | ||
| + | }} | ||
| + | {{Publikation Author | ||
| + | |Rank=3 | ||
| + | |Author=Ljiljana Stojanovic | ||
}} | }} | ||
{{Publikation Author | {{Publikation Author | ||
|Rank=2 | |Rank=2 | ||
|Author=Jorge Gonzalez | |Author=Jorge Gonzalez | ||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{Inproceedings | {{Inproceedings | ||
| Zeile 24: | Zeile 24: | ||
|VG Wort-Seiten= | |VG Wort-Seiten= | ||
|Projekt=SemIPort, | |Projekt=SemIPort, | ||
| − | |Forschungsgruppe= | + | |Forschungsgruppe=Wissensmanagement |
}} | }} | ||
{{Forschungsgebiet Auswahl | {{Forschungsgebiet Auswahl | ||
| Zeile 30: | Zeile 30: | ||
}} | }} | ||
{{Forschungsgebiet Auswahl | {{Forschungsgebiet Auswahl | ||
| − | |Forschungsgebiet= | + | |Forschungsgebiet=Ontology Engineering |
}} | }} | ||
{{Forschungsgebiet Auswahl | {{Forschungsgebiet Auswahl | ||
| − | |Forschungsgebiet= | + | |Forschungsgebiet=Semantic Web |
}} | }} | ||
Aktuelle Version vom 16. Oktober 2009, 17:30 Uhr
ONTOLOGER - a System for Usage-driven Management of Ontology-based Information Portals
ONTOLOGER - a System for Usage-driven Management of Ontology-based Information Portals
Published: 2003
Oktober
Buchtitel: KCAP 2003
Seiten: 172-179
Verlag: ACM
Referierte Veröffentlichung
BibTeX
Kurzfassung
In this paper we present the conceptual architecture of ONTOLOGER, a system for usage-driven management of querying for information in ontology-based information portals. The system is based on the analysis of users' activities that are acquired in the so-called semantic log file, which contains information about the content of a visited page as well. These analyses are used for managing (i) the underlying ontology, (ii) querying mechanism and (iii) the content of the information repository, in order to ensure that (a) the structure of the vocabulary reflects the needs of users, (b) the highly-relevant results can be found by users although they make short queries and read only top-ranked results and (c) the information repository contains (only) resources users are interested in. The focus of the paper is on improving querying (retrieval) mechanism based on the usage data. We present a case study, which shows how a portal can benefit from implementing presented management system.
Ontology Engineering, Semantic Web, Ontologiebasierte Wissensmanagementsysteme