3/18/2002AIM AB Review of WSRP/WSIA Adaptation Description Language, Past and Present Directions. Ravi Konuru, IBM

3/18/2002 Adaptation Language Ideas Web Applications, Producers, Consumers and User Agents Application Back End Services WSXL service ProducersConsumers (or “integrators”) Clients Legacy Web App

3/18/2002 Adaptation Language Ideas The Scope Users WSIA Service WSIA Runtime WSIA Application WSIA Runtime HTTP (SOAP) HTTP (HTML ) ConsumerProducers Travelers Check Application WSIA Service WSIA Runtime Stock Application HTTP (SOAP) WSIA Proxy WSIA Proxy Legacy Web App Business Logic Web Service

3/18/2002 Adaptation Language Ideas Adaptation Language Requirements R1. Reasonable evolution model: The methodology, the technical effort by a provider to make an existing web application into an adaptable WSIA service must be reasonable. R2. Low Entry Point wrt Computation and Scalability: The minimum computational and scalability demands that are placed on the provider must be reasonable. R3. Allow for Consumer-Customer Confidentiality: Consumer to adapt a provider ’ s output in a manner that is confidential between the consumer and the end-user. For example, it is possible for a consumer to insert additional markup into the output stream without provider having access to the inserted markup. R4. Allow for Provider support for adaptation: It is possible for a provider to provide support and perform the adaptations needed by the consumer so as to allow a low-entry consumer or for complex adaptations. R5. Choice of adaptation implementation models: A single consumer can use a combination of available provider operations and local execution to achieve a desired set of adaptations. R6. Adaptation Description is available statically for design-time use. R7. Adaptation constraints can be specified by a provider.

3/18/2002 Adaptation Language Ideas performAction createInstance( customization properties ) Example of Client  WSXL Service Interaction with Customization and Adaptation Aggregation Component (Consumer)Service Component (Producer) Creates customized instance Clicks Action getOutput IS S User Views WSIA Instance Allocate new Customized Instance Generate Markup, (opt: adaptation desc) Action Handling (opt: create Session) I I A I S A I A I IS A S I A Consumer markup adaptation Action Adaptation Local implementation or redirection of action to other Producer AIS P performAction

3/18/2002 Adaptation Language Ideas Rest of the Talk Part I: WSXL Adaptation Language in Position Paper Part II: New work in progress.

3/18/2002 Adaptation Language Ideas Part I: Adaptation Description Language Position paper version.

3/18/2002 Adaptation Language Ideas Adaptation Language: Position paper version Based on the core idea of adaptation points. An adaptation point is a point of observation or manipulation exported by a producer to enable consumer adaptation. Adaptation points can provide information regarding Content (e.g the price of a certain item) Look and feel (e.g font attribute for a certain table) Behaviour (e.g a handler for a click event) Related Adaptation points can be grouped under Adaptation groups. Adaptation group is the root of an adaptation description.

3/18/2002 Adaptation Language Ideas Adaptation Point An application-specific Adaptation Point name The kind of operation (insert, replace, lookup). Specifies the adaptation ’ s intended use. The names of pages/states, i.e., to the different component ’ s outputs, that it applies to. An extensible locator to the item[s] of interest in the output. For instance, xpath, xquery are used for XML documents. Note that a locator can point to multiple locations in document. An Adaptation Point category (XML, CSS, etc). Specifies the category of the item[s] of interest. The information specific to the application of an adaptation of that category (XML, CSS). Adaptation Generator mechanism for specifying provider support Tooling Info/Hints.

3/18/2002 Adaptation Language Ideas Example 1. Look and Feel Adaptations selector result detail error Change look and feel of FastMem pages font Adapt the size of the font used on this page

3/18/2002 Adaptation Language Ideas Example 2. Data Value Lookup and Replace integer

3/18/2002 Adaptation Language Ideas Example 3. Replace a presentation element ShortContactInfo LongContactInfo

3/18/2002 Adaptation Language Ideas Adaptation Generator AdaptationGenerators are operations implemented by provider Introduced to handle three kinds of situations: 1. For providers to provide assistance in creating markup for the aggregator for use in adaptation. 2. To retain control over markup fragments inserted/modified. 3. To sidestep the limitations of the constraint language. The operations can be provider specific. A provider implements these AdaptationGenerator operations and includes their names suitably in the adaptation description. Invoked by a client to perform presentation and data related transforms and use the resulting message in performing the adaptation.

3/18/2002 Adaptation Language Ideas Example 4. Consumer using Provider support. Provider implements an operation named "addColumnToTable" … addColumntoTable Signature obtained from provider ’ s WSDL, two part input message a) Portion/ID of original message sent down by the provider b) Consumer ’ s presentation and/or content adaptation information

3/18/2002 Adaptation Language Ideas Part II: Work in progress Unify the models and mechanisms for Customizations executed by the consumer Customizations executed by the provider. A single ADL that can be used for both. Extend ADL to support coordination support orchestration Other Specification requirements: Proportional to customization complexity. Extensible to additional output types.