Re: Definition of adaptation policy

On a different point, I was wondering about adaptation policies for 
mapping from the abstract UI layer to the concrete UI layer.

One idea that I believe Rhys floated was to extend DIAL with new 
markup for concrete UI constructs, e.g. panels, radio buttons, 
tabbed controls, sliders and the like.

Authoring at such a level would still be a nuisance as you would 
have to deal with the mixing of different levels of abstraction. It 
would therefore seem like a good idea to explore how adaptation 
policies can map between levels of abstraction in a way that 
simplifies the author's task by keeping the layers separated.

XSLT offers one such route e.g. when combined with the XPath access 
functions for the delivery context. Have you explored using XSLT as 
a means to translate between levels of abstraction, and if so could 
you please offer us comments on your experience?

I am also interested in going beyond XPath's simple declarative 
event handlers to a richer description of application behavior that 
takes into account an explicit model of application tasks. SCXML 
seems very promising, and I am looking for reports on work on 
using XML for dialogue modeling as part of layered descriptions of 
UI.

p.s. this is all stuff we need to cover in the wiki.

Cheers,

  Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett

Received on Monday, 8 October 2007 17:06:57 UTC