Difference between revisions of "Architectures of Adaptive Hypermedia Systems"

From PAWS Lab
Jump to: navigation, search
(Choosing The Right Name And Focus)
(Choosing The Right Name And Focus)
Line 6: Line 6:
 
* Architectures and Approaches for Personalization and Adaptation (Eelco) - not just architectures, but also approaches to personalization
 
* Architectures and Approaches for Personalization and Adaptation (Eelco) - not just architectures, but also approaches to personalization
 
* Framework/infrastructure issues in [distributed/component-based] adaptive hypermedia systems (Michael)
 
* Framework/infrastructure issues in [distributed/component-based] adaptive hypermedia systems (Michael)
** Infrastructure Issues In Adaptive Hypermedia Systems - IIIAHS - cool abbreviation :)
+
** Infrastructure Issues In Adaptive Hypermedia Systems - IIIAHS - cool abbreviation :) [http://adapt2.sis.pitt.edu/wiki/Image:Iiiahs_ws_logo_ideas.png logo ideas]
  
 
== Participants AKA Co-organizers ==
 
== Participants AKA Co-organizers ==

Revision as of 15:10, 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.

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
  • Framework/infrastructure issues in [distributed/component-based] adaptive hypermedia systems (Michael)
    • Infrastructure Issues In Adaptive Hypermedia Systems - IIIAHS - cool abbreviation :) logo ideas

Participants AKA Co-organizers

(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?

Contacts

Michael Yudelson