elektronickÃ¡ verzia publikÃ¡cie - FIIT STU - SlovenskÃ¡ technickÃ¡ ...

More documents

Recommendations

Info

218 Selected Studies on Software and Information Systems Examples of user models represented by ontologies GUMO. General User Model Ontology (GUMO) [29] is an effort to build commonly accepted user model ontology. GUMO ontology is developed within Ubiquitous User Modeling 3 project, which had a significant impact on ontology design. Authors were focused on building relatively broad taxonomy of classes representing concepts of actual user’s context (e.g., actual movement, emotional state). Model provides classes for capturing static user characteristics (name etc.) and characteristics such as interests or goals. However, ontology does not prescribe properties of individual classes nor relations between them. Authors did not employ any conditions and restrictions provided by OWL language. GUMO has a potential to become a top-level (upper) ontology in the field of user modeling, serving as a point of term unification. Individual specialized ontologies could define mapping of their own classes to classes of GUMO ontology. gumo:Person.110003 ubis:identifier = 110003 ubis:website = http://ubisworld.org/show.php?subject=11... ubis:image = http://u2m.org/UbisWorld/img/man-small.g... gumo:UserModelAuxiliary.600020 Any* gumo:HasProperty.600100 Instance* gumo:BasicUserDimensions.7002 gumo:HasInterest.600110 Any* gumo:HasKnowledge.600120 Any* gumo:HasPlan.600130 Any* gumo:HasProperty.600100* gumo:BasicUserDimensions.700002 isa isa isa isa gumo:ContactInformation.700008 gumo:AbilityAndProficiency.700011 gumo:Motion.700018 gumo:EmotionalState.700014 isa isa isa isa gumo:FullName.800414 gumo:FamilyName.800412 gumo:AbilityToSee.801002 gumo:AbilityToSmell.801004 Figure 8-1. Visualization of selected parts of GUMO ontology. Basic concept Person is connected to a broad classification of basic user dimensions. User model in NAZOU project. Several tools responsible for acquisition, organisation and presentation of knowledge from heterogeneous sources (e.g., the Web) are developed within NAZOU project 4 . Its presentation layer is based on ontological representation of domain data (job offers) as well as user model. The model is divided into two parts: domain independent and domain specific. Each part defines various types of user characteristics, which contain respectively either generic information about a user or information related to domain content (interests on properties, values of various attributes of job offer). Each characteristic has a timestamp, holds a number of 3 Ubiquitous User Modeling, http://www.u2m.org/ 4 NAZOU project, http://nazou.fiit.stuba.sk/
User Modeling for Personalized Web-Based Systems 219 its updates and a source which contributed the characteristic to the model. Each characteristic contributes to certain user’s goal with certain relevance. Because characteristics stored in a model are only estimations of real user features based on analysis of user’s behavior [6], each characteristic has a confidence, informing about quality of the estimation. Complete description of the model can be found at http://nazou.fiit.stuba.sk. User model in OntoAIMS system. Ontology-based Adaptive Information Management System (OntoAIMS) provides environment for navigation in and searching for information. This environment recommends its users (students) the most suitable tasks and helps them in exploration of the domain [23]. System represents the typical example of employment of ontologies representing a domain as well as user model. User model, created and maintained by a specialized component OWL-OLM, is forming a layer on the top of a domain model and adds user’s perspective to it. This approach is suitable in this case, as the information space defined in domain model (OS Linux course) is closed and static enough. User model is built using an interactive dialogue with a user and contains information about each individual concept like number of concept’s usage, number of correct usages, number of times user declared concept as understood etc. The model is consequently used to recommend content. Conclusions on User Model Representation Ontology is clearly the most promising alternative to represent user model. The basic ide of ontological modeling is very similar to the way how human think about things in the world. This allows for inclusion of domain experts into to the process of domain and user model creation. OWL language is expressive enough to capture even complex relationships present in reality. Ontologies are the basis for inference mechanisms, which could not only verify model consistency, but are also able to use conditions, restrictions and rules to infer new relationships and knowledge. Advantage of ontologies is its shareability, supported by mapping means provided by OWL. Disadvantage of ontology based representation is currently the lack of tools and technologies, (editors, mappers, repositories etc.) in the production-grade quality, which would provide the same efficiency of work as it is with relational databases and XML-based technologies. 8.2 User Characteristics When designing adaptive web-based system (and its user modeling part) we need to consider which features of users will be used for adaptation and thus should be modeled. Five most popular and useful features are [15]: knowledge, interests, goals and tasks, background and individual traits. Knowledge is used mainly in adaptive educational systems, which keep track of user’s knowledge of the domain as a whole as well as of smaller fragments. Interests (keyword or concept-based) are becoming important as volume of information space increases and new information-oriented systems (encyclopedias etc.) are being developed. Goals and tasks represents the immediate purpose for a user’s work within an adaptive system [15]. It can be a learning goal or immediate information need.
Page 1:
Edícia výskumných textov informa
Page 4 and 5:
Štúdie vybraných tém programov
Page 6 and 7:
vi Štúdie vybraných tém program
Page 8 and 9:
viii Štúdie vybraných tém progr
Page 11 and 12:
OBSAH DIEL I: SOFTVÉROVÉ PARADIGM
Page 13:
Obsah xiii 9.3 Human-Computer Relat
Page 17 and 18:
1 NÁVRHOVÉ VZORY Nikoleta Habudov
Page 19 and 20:
Návrhové vzory 5 Z 23 vzorov sú
Page 21 and 22:
Návrhové vzory 7 Použitie Uniká
Page 23 and 24:
Návrhové vzory 9 Príklad z reál
Page 25 and 26:
Návrhové vzory 11 − Konkrétna
Page 27 and 28:
Návrhové vzory 13 public MMU crea
Page 29 and 30:
Návrhové vzory 15 F’/R’ B Obr
Page 31 and 32:
Návrhové vzory 17 Zvláštny výz
Page 33 and 34:
Návrhové vzory 19 So vzorom Rukov
Page 35 and 36:
Návrhové vzory 21 Problémy môž
Page 37 and 38:
Návrhové vzory 23 používané, s
Page 39 and 40:
Návrhové vzory 25 Vzor Farebné s
Page 41 and 42:
Návrhové vzory 27 Obrázok 1-16.
Page 43 and 44:
Návrhové vzory 29 Vytváranie a e
Page 45 and 46:
Návrhové vzory 31 tmavšie miesta
Page 47 and 48:
Návrhové vzory 33 kom (tzv. avata
Page 49:
Návrhové vzory 35 [18] Schmidt, D
Page 52 and 53:
38 Štúdie vybraných tém program
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
100 Štúdie vybraných tém progra
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 129 and 130:
4 RÁMCE Ivan Kišac, Marián Šimk
Page 131 and 132:
Rámce 117 − Rámec ierna skrinka
Page 133 and 134:
Rámce 119 Výhody a nevýhody rám
Page 135 and 136:
Rámce 121 žívateské vstupy z kl
Page 137 and 138:
Rámce 123 Obrázok 4-5. Ukážka r
Page 139 and 140:
Rámce 125 ziách tohto vývojovéh
Page 141:
Rámce 127 Manažment transakcií.
Page 145 and 146:
ZNOVUPOUŽITIE NÁVRHOVÝCH VZOROV
Page 147 and 148:
Znovupoužitie návrhových vzorov
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179:
Page 182 and 183: 168 Selected Studies on Software an
Page 215 and 216: 7 SPRÍSTUPŇOVANIE INFORMÁCIÍ PO
Page 217 and 218: Sprístupňovanie informácií pomo
Page 227: Sprístupňovanie informácií pomo
Page 282 and 283:
268 Selected Studies on Software an
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 345:
EDÍCIA VÝSKUMNÝCH TEXTOV INFORMA
show all

elektronickÃ¡ verzia publikÃ¡cie - FIIT STU - SlovenskÃ¡ technickÃ¡ ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?