Difference between revisions of "Architectures of Adaptive Hypermedia Systems"
From PAWS Lab
(→Participants AKA Co-organizers) |
(→Vocabulary) |
||
| Line 33: | Line 33: | ||
== Vocabulary == | == Vocabulary == | ||
| − | + | * content management system (CMS), aka Web CMS (WCMS) - users' entry point, the portal, the content aggregator | |
| − | + | * user model (UM), aka user modeling server/service (UMS) | |
| − | + | * adaptation service (AS), aka personalization service (PService), aka adaptive functionality (AF) | |
| − | + | * content, aka materials, aka resources | |
| − | + | * [domain] vocabulary, aka [domain] ontology - [structured] set of concepts, describing items of content | |
| − | + | * [content] metadata - [weighted] list of domain concepts describing content item | |
== Host conference(s) == | == Host conference(s) == | ||
Revision as of 14:51, 4 August 2009
This page is a tentative home for an anticipated workshop on Architectures of Adaptive Hypermedia Systems. Its main purpose is to maintain awareness of the workshop organization process.
Contents
Choosing The Right Name And Focus
- Architectures of Adaptive Hypermedia Systems - too restrictive?
- Architectures of [distributed] [component-based] personalized/user-adaptive systems (Peter)
- Architectures and Approaches for Personalization and Adaptation (Eelco) - not just architectures, but also approaches to personalization
Participants AKA Co-organizers
- Abel, Fabian (University of Hannover)
- de Bra, Paul (Technical University of Eindhoven)
- Brusilovsky, Peter (University of Pittsburgh)
- Conlan, Owen (Trinity College Dublin)
- Davis, Hugh (University of Southampton)
- Henze, Nicola (University of Hannover) - pending agreement
- Herder, Eelco (University of Hannover)
- O'Keeffe, Ian (Trinity College Dublin)
- Knutov, Evgeny (Technical University of Eindhoven)
- Koidl, Kevin (Trinity College Dublin)
- Wade, Vincent (Trinity College Dublin)
- Yudelson, Michael (University of Pittsburgh)
(and maybe more)
Topics
To include
- CMS and AS: striking the right balance while separating the two, ways to implement "hooks"/callbacks on CMS for connecting to AS
- metadata for content: self-aware content (knows own metadata) vs. agnostic content
- UM backend of AS: question of common denominator between several UMS (mapping, conversion; bottom-up and top-down; cross domain generalization of UM), standardizing UM representation, UM exchange
- user interface considerations of AS: intrusive (changing the UI) vs. hidden, scopes of their most effective applicability
- AS: framework/architecture orientated vs. third party / cross-platform, scopes of applicability of these two approaches
- case studies and lessons learned
Not to include
- yet-another-[pseudo-]architecture
Vocabulary
- content management system (CMS), aka Web CMS (WCMS) - users' entry point, the portal, the content aggregator
- user model (UM), aka user modeling server/service (UMS)
- adaptation service (AS), aka personalization service (PService), aka adaptive functionality (AF)
- content, aka materials, aka resources
- [domain] vocabulary, aka [domain] ontology - [structured] set of concepts, describing items of content
- [content] metadata - [weighted] list of domain concepts describing content item
Host conference(s)
UMAP 2010?
