BEA WebLogic User Manual page 59

To address this, the transformation process is divided into two distinct phases:
•
Transformation to target mark-up: (for example, transforming mmXHTML into WML 1.2) as
described in earlier sections. This process is completely rule-based and requires no input from
content developers.
•
Application of layout and styling preferences: This process empowers content developers to
create stencils describing how the output will be arranged on each of the different classes of
devices. The following graphic presents the concept graphically.
The 2 Phases of Content Transformation
After the first "transformation" phase, the content has been distilled to suit the target device. Also
notice in this simple example that formatting directives such as bold and italic have been removed
from the WML output. After the second "layout and style" phase, the content has been
restructured to suit the size and shape of the device. Typically, PDA content is arranged
sequentially, WAP content is arranged as a set of menu items (or links) and PC content is
presented very similarly to the original mark-up. During this second phase, WebLogic Mobility
Server also performs the application of cascading style sheets for devices that cannot support
style sheets locally. Style sheets are discussed in greater detail in the section "Working with Style
Sheets."
In normal circumstances, a content developer will only develop two distinct layouts for the web
application; one for targeting content for PDAs and one for menu-driven devices such as WAP
phones.
Part IV Presentation of Mobile Content
BEA WebLogic Mobility Server User Guide - 55