Re: Definition of adaptation policy

Hi,

Good point. I think that we are going to need to think in different kind 
of policies suitable for different delivery contexts:

+ Pagination policies
+ Layout policies
+ Rendering policies (i.e. the mapping between the abstract and concrete UI)
+ Content selection policies, i.e . how do you guide a content selection 
process in order to select the most appropiate content under certain 
circumstances.
+ Style policies i.e. how the look and feel of your application might 
change depending on different delivery contexts
+ Interaction policies i.e. how the user interface and the input methods 
might change depending on the available modes of interaction

Currently in the MyMobileWeb project we implement policies as a CSS 
properties and redefining CSSs for different delivery contexts. We do 
not use XSLT

Best Regards

Dave Raggett escribió:
> 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
>
>