Content repurposing is the reorganizing of data for presentation on different display hardware (Singh, 2004). It has been particularly important recently with the growth of handheld devices such as “personal digital assistants” (PDAs), sophisticated telephones, and other small specialized devices. Unfortunately, such devices pose serious problems for multimedia delivery. With their small screens (240 by 320 for a basic Palm PDA), one cannot display much information (like most of a Web page); with their low bandwidths, one cannot display video and audio transmissions from a server (“streaming”) with much quality; and with their small storage capabilities, large media files cannot be stored for later playback. Furthermore, new devices and old ones with new characteristics have been appearing at a high rate, so software vendors are having difficulty keeping pace. So some real-time, systematic, and automated planning could be helpful in figuring how to show desired data, especially multimedia, on a broad range of devices.
The World Wide Web is the de facto standard for providing easily accessible information to people. So it is desirable to use it and its language HTML as a basis for display for small handheld devices. This would enable people to look up ratings of products while shopping, check routes while driving, and perform knowledge-intensive jobs while walking. HTML is, in fact, device-independent: It requires the display device and its Web browser software to make decisions about how to display its information within guidelines. But HTML alone does not provide enough information to devices to ensure much user-friendliness of the resulting display: It does not often tell the browser where to break lines or which graphics to keep colocated. Display problems are exacerbated when screen sizes, screen shapes, audio capabilities, or video capabilities are significantly different. “Microbrowser” markup languages like WML, S-HTML, and HDML, that are based on HTML but designed to better serve the needs of small devices, help, but only solve some of the problems.
Content repurposing is a general term for reformatting information for different displays. It occurs frequently with “content management” of an organization’s publications (Boiko, 2002) where “content” or information is broken into pieces and entered in a “repository” to be used for different publications. However, a repository is not cost-effective unless the information is reused many times, something not generally true for Web pages. Content repurposing for small devices also involves real-time decisions about priorities. For these reasons, the repository approach is not often used with small devices.
Content repurposing can also be either server-side (a server supplies repurposed information for the client device) or client-side (the device itself decides what to display and how). Server-side repurposing saves work for the device, which is important for primitive devices, and can adjust to fluctuations in network bandwidth (Lyu, Yen, Yau, & Sze, 2003), but requires added complexity in the server and significant time delays in getting information to the server. Devices can have designated “proxy” servers for their needs. Client-side repurposing, on the other hand, can respond quickly to changing user needs. Its disadvantages are the additional processing burden on an already-slow device, and higher bandwidth demands since information is not eliminated until after it reaches the device. The limitations of small devices require most audio and video repurposing to be server-side.