Content Transformation Landscape 1.0 (original) (raw)

By presenting requests as though they came from a different device, Content Transformation prevents mobile aware sites from detecting the actual mobile devices behind the request. As a result, mobile aware sites whose purpose is to provide mobile compatible pages or mobile compatible content like ring-tones or Java applications are unable to operate correctly. Such sites require information about the actual device.

5. Origin servers and proxies must be able to identify the actual identity of components of the delivery context, including (other) proxies and browsers.

When mobile aware sites send content to devices, they often choose to deliver very specific variations on their content tailored exactly for the device. Any attempt by a content transformation proxy to change the content may very well destroy or in any case decrease the value of the content. For example, a site which delivers ring tones or wallpaper which it tailors exactly to devices' characteristics may be rendered useless if the audio format is changed, or less valuable if the color depth of an image is reduced to something below that which the device is capable of rendering.

6. Origin servers must be able to prohibit any kind of transformation of its content.

7. Origin servers must be able to advertise author preferences.

Some Web sites cater for both desktop browsers and mobile devices, especially when the site recognizes that the device has a browser that is capable of providing a 'full screen' presentation mode. In these cases the user of the mobile device may be prevented from exercising their choice of presentation and may be unable to access either the site's mobile or desktop presentation in its original form.

8. Browsers must be able to identify and advertise user interface modalities.

9. Components must be able to solicit and advertise user choice.

10. Origin servers must be able to identify and advertise different representations they may have available.