|
|
|
W3C Workshop on Metadata for Content Adaptation |
|
Dublin, 12.-13.10.2004 |
|
|
|
Gerald Hübsch and Thomas Springer |
|
Dresden University of Technology |
|
{huebsch,springet}@rn.inf.tu-dresden.de |
|
|
|
|
|
|
|
Adaptation is a promising solution to overcome
the increasing differences in requirements imposed by mobile device
technology |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Today’s adaptation approaches focus on
User-Interface-level and Widget-level adaptation and support single
modalities |
|
|
|
|
|
Single Source Authoring uses generic dialog
descriptions and applies dedicated adaptation algorithms parameterised by
context information to generate device-specific content representations |
|
|
|
|
Semantic and Syntactic Dialog Adaptation (UI
& Widget Level Adaptation) |
|
|
|
|
XML-based device independent markup language for
Single Source Authoring of web content and web application UIs |
|
Inline meta-information governs adaptation
Separation of structure, content and presentation |
|
Inheritance concept for content reuse |
|
Language concepts support semantic and syntactic
adaptation |
|
Support for dynamic content and interaction with
application logic (MVC) |
|
Modular adaptation pipeline implements
adaptation algorithms |
|
|
|
|
|
|
|
|
DDL Adaptation Engine Architecture (Simplified) |
|
|
|
|
|
Details on DDL Context Profiles |
|
|
|
Profile representation: well-formed XML document |
|
Utilized by Selective Content and Dialog
Pagination Algorithms |
|
Basic context profile content: |
|
Client markup language type |
|
Client display (dimensions and type) |
|
Maximum transferable dialog size in Byte (WAP
WSP-SDU, client memory) |
|
Device class according to device classification
schema |
|
Profile allows for application-specific
extensions |
|
Server-side context processing: Profile is added
to HTTP request by ClientRecognizer runtime component |
|
|
|
|
Semantic Annotations for Selective Content in
DDL |
|
|
|
Selective Content: inserting or removing dialog components
to optimize dialog presentation and complexity w.r.t. the context in which
the dialog is accessed |
|
Selective Content in DDL is implemented by
context queries over DDL Context Profiles |
|
Elements with fulfilled query condition are left
in the dialog, otherwise they are removed |
|
A test attribute is used to attach context
queries to DDL Part or Property elements |
|
|
|
|
|
|
|
|
|
Details on DDL Context Queries |
|
|
|
DDL context queries are formulated in XPath |
|
Query types: |
|
Simple queries (only one context parameter) |
|
Complex queries (join results of several simple
queries) |
|
XPath provides a powerful and flexible way to
formulate complex queries over XML structures |
|
Numeric and String comparison operators provided
by XPath directly operate on parameter values in the Context Profile |
|
Boolean operators supported by XPath are
utilized to formulate complex queries |
|
|
|
|
|
|
|
DDL Pagination |
|
|
|
Approach to meet size and usability constraints
imposed by the target platform and the network protocol through
semi-automatic dialog splitting |
|
Dialogs must not be arbitrarily paginated:
Language elements to express semantic relationships of dialog elements
needed |
|
|
|
DDL provides alternative language concepts for |
|
Logical element grouping: DDL Atoms and
Molecules |
|
Language element: atom property for DDL Parts |
|
Predefining split points: DDL Static Pagination |
|
Language element: fragment element + level
attribute |
|
|
|
|
|
Atoms and Molecules Approach: DDL Syntax |
|
|
|
|
|
|
|
|
Example: Atoms and Molecules Pagination |
|
|
|
|
|
|
|
|
Example: Atoms and Molecules Pagination |
|
|
|
|
|
|
|
|
Example: Atoms and Molecules Pagination |
|
|
|
|
|
|
|
|
|
Predefined Splitting Points |
|
|
|
|
|
|