Difference between revisions of "Architectures of Adaptive Hypermedia Systems"
From PAWS Lab
(→Topics) |
(→Topics) |
||
| Line 15: | Line 15: | ||
== Topics == | == Topics == | ||
| − | To include | + | To include (address, be aware, or relate to) |
* CMS and AS: striking the right balance while separating the two, ways to implement "hooks"/callbacks on CMS for connecting to AS | * 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 | * metadata for content: self-aware content (knows own metadata) vs. agnostic content | ||
Revision as of 17:52, 9 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
Most recent first
- Framework/infrastructure issues in [distributed/component-based] adaptive hypermedia systems (Michael)
- Infrastructure Issues In Adaptive Hypermedia Systems - IIIAHS - cool abbreviation :) logo ideas
- Architectures and Approaches for Personalization and Adaptation (Eelco) - not just architectures, but also approaches to personalization
- Architectures of [distributed] [component-based] personalized/user-adaptive systems (Peter)
- Architectures of Adaptive Hypermedia Systems - too restrictive?
Related Work
- Scalability Issues in AIED Workshop at AIED 2009, Brighton, United Kingdom
- DAH’09: International Workshop on Dynamic and Adaptive Hypertext: Generic Frameworks, Approaches
and Techniques
Topics
To include (address, be aware, or relate to)
- 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 - AS: one-to-many and many-to-one
- mapping/conversion/exchange of UMs
- cross-system modeling
- cross-domain generalization
- standardizing UM representation
- user interface considerations of AS
- manifested UI (changing the UI) vs. hidden
- scopes of most effective applicability of the two
- framework/architecture/infrastructure implementation
- ubiquity of infrastructure (extravert approach, third-party services) vs. utility (tradeoffs of introvert approach)
- infrastructure "penetration" thresholds
- existence of standards
- applicability scopes of 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?
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)
