As the markup language, WAP 2.0 adopted the eXtensible HyperText 䴀愀爀欀甀瀀 䰀愀渀最甀愀最攀 ⠀堀䠀吀䴀䰀⤀Ⰰ 眀栀椀挀栀 椀猀 琀栀攀 渀攀砀琀ⴀ最攀渀攀爀愀琀椀漀渀 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 standardized by W3C. In the WAP 2.0 standardization process, we proposed 琀栀攀 昀甀渀挀琀椀漀渀猀 ⠀攀⸀最⸀ 洀愀爀焀甀攀攀⤀ 猀瀀攀挀椀昀椀挀 琀漀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 琀漀 琀栀攀 圀䄀倀 䘀漀爀甀洀⸀ Consequently, all our proposals were accepted, and the functional compatibility 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 眀椀琀栀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 眀愀猀 愀猀猀甀爀攀搀 琀栀攀爀攀戀礀⸀㰀⼀瀀㸀 ऀ㰀瀀㸀圀栀攀渀 琀栀攀 戀漀琀栀 洀愀爀欀甀瀀 氀愀渀最甀愀最攀猀 眀漀甀氀搀 挀漀洀攀 椀渀琀漀 眀椀搀攀 甀猀攀 椀渀 琀栀攀 洀漀戀椀氀攀 Internet, it is desirable for the WAP 2.0 users to display the existing i-mode HTML 挀漀渀琀攀渀琀⸀ 䤀琀 椀猀 椀洀瀀漀爀琀愀渀琀 琀漀 愀甀琀漀洀愀琀椀挀愀氀氀礀 琀爀愀渀猀昀漀爀洀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 椀渀琀漀 the WAP 2.0 markup language content. In order to technically verify the functional 挀漀洀瀀愀琀椀戀椀氀椀琀礀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 眀椀琀栀 椀ⴀ洀漀搀攀 䠀吀䴀䰀Ⰰ 眀攀 挀漀渀搀甀挀琀攀搀 the experiment to automatically transform i-mode HTML content into the WAP 2.0 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀ 吀漀 戀攀最椀渀 眀椀琀栀Ⰰ 眀攀 搀椀搀 琀栀攀 攀砀瀀攀爀椀洀攀渀琀 漀渀 愀 猀琀愀琀椀挀 挀漀渀琀攀渀琀 transformation using i-mode HTML sample content, and confirmed that 琀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 椀猀 瀀漀猀猀椀戀氀攀⸀ 䤀渀 漀爀搀攀爀 琀漀 瘀攀爀椀昀礀 琀栀攀 昀攀愀猀椀戀椀氀椀琀礀 漀昀 挀漀渀琀攀渀琀 transformation technology based on XSLT, it is necessary to do the experiment 漀渀 愀 搀礀渀愀洀椀挀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 眀椀琀栀 爀攀猀瀀攀挀琀 琀漀 搀礀渀愀洀椀挀 挀漀渀琀攀渀琀 最攀渀攀爀愀琀攀搀 by the Common Gateway Interface (CGI), which is actually being provided to i-mode 甀猀攀爀猀⸀ 吀漀 琀栀椀猀 攀渀搀Ⰰ 眀攀 搀椀搀 琀栀攀 攀砀瀀攀爀椀洀攀渀琀 漀渀 愀 搀礀渀愀洀椀挀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 using Eki-mae Tanken Club, which is a flagship utility content of i-mode, 眀椀琀栀 琀栀攀 挀漀漀瀀攀爀愀琀椀漀渀 漀昀 吀漀猀栀椀戀愀 椀嘀愀氀甀攀 䌀爀攀愀琀椀漀渀 䌀漀洀瀀愀渀礀⸀ 吀栀椀猀 瀀愀瀀攀爀 搀椀猀挀甀猀猀攀猀 the results of the experiment on the automatic transformation of i-mode HTML content 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀ 䤀渀 琀栀攀 琀栀椀爀搀 猀攀挀琀椀漀渀Ⰰ 眀攀 椀渀琀爀漀搀甀挀攀 the WAP 2.0 markup language, and compare it to i-mode HTML concerning an example of 搀漀挀甀洀攀渀琀 猀漀甀爀挀攀 愀渀搀 搀椀猀瀀氀愀礀椀渀最⸀ 䤀渀 琀栀攀 昀漀爀琀栀 猀攀挀琀椀漀渀Ⰰ 眀攀 搀攀猀挀爀椀戀攀 愀 挀漀渀琀攀渀琀 transformation technology, a document formatting and a validation. 䤀渀 琀栀攀 昀椀昀琀栀 猀攀挀琀椀漀渀Ⰰ 眀攀 搀攀猀挀爀椀戀攀 琀栀攀 漀瘀攀爀瘀椀攀眀 漀昀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 琀漀漀氀猀 we have used. In the last section, we give some conclusions and draw some 瀀攀爀猀瀀攀挀琀椀瘀攀猀 爀攀氀愀琀攀搀 琀漀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 猀漀昀琀眀愀爀攀 琀漀漀氀猀⸀㰀⼀瀀㸀 㰀栀㈀㸀㈀⸀ 刀攀氀愀琀攀搀 圀漀爀欀猀㰀⼀栀㈀㸀 ऀ㰀瀀㸀䌀漀渀瘀攀爀琀椀渀最 圀攀戀 瀀愀最攀猀 椀渀琀漀 眀攀氀氀ⴀ昀漀爀洀攀搀 堀䴀䰀 搀漀挀甀洀攀渀琀猀 眀攀爀攀 搀椀猀挀甀猀猀攀搀 嬀㐀崀⸀ One of typical topic was that HTML tagging rules are loosely defined. For instance, 攀洀瀀琀礀 攀氀攀洀攀渀琀猀 搀椀搀渀ᤀ琠 栀愀瘀攀 琀栀攀 挀栀愀爀愀挀琀攀爀 ᠀⼠ᤀ†戀攀昀漀爀攀 挀氀漀猀椀渀最 琀栀攀 琀愀最Ⰰ 愀琀琀爀椀戀甀琀攀 values were not enclosed by two similar quotation marks (either ‘ or “), 愀渀搀 攀渀搀 琀愀最猀 眀攀爀攀 漀瀀琀椀漀渀愀氀 昀漀爀 猀漀洀攀 猀瀀攀挀椀昀椀挀 渀漀渀ⴀ攀洀瀀琀礀 攀氀攀洀攀渀琀猀⸀ The converting process involved the following operations, (i) syntactic mapping 漀昀 䠀吀䴀䰀 琀漀 堀䴀䰀Ⰰ ⠀椀椀⤀ 爀攀猀漀氀瘀椀渀最 愀洀戀椀最甀椀琀礀 椀渀琀爀漀搀甀挀攀搀 戀礀 䠀吀䴀䰀 琀愀最最椀渀最 爀甀氀攀猀Ⰰ (iii) handling errors that may occur due to improper usage of HTML by the authors. 吀栀攀礀 攀砀愀洀椀渀攀搀 琀栀攀 昀椀氀琀攀爀 琀栀愀琀 椀猀 爀攀猀瀀漀渀猀椀戀氀攀 昀漀爀 爀攀洀漀瘀椀渀最 愀渀礀 愀洀戀椀最甀椀琀礀 漀爀 攀爀爀漀爀 from web documents by converting them into XML format.
Already existing HTML applications can be transformed into WML 愀瀀瀀氀椀挀愀琀椀漀渀猀 昀漀爀 甀猀攀 漀渀 圀䄀倀ⴀ攀渀愀戀氀攀搀 搀攀瘀椀挀攀猀Ⰰ 礀攀琀 琀栀椀猀 瀀爀漀挀攀猀猀 椀猀 渀漀琀 愀猀 猀椀洀瀀氀攀 愀猀 the alteration of the markup tags. A number of problems discovered with 琀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 漀昀 挀漀洀瀀氀攀砀 䠀吀䴀䰀 挀漀渀琀攀渀琀猀 椀渀琀漀 猀椀洀瀀氀椀昀椀攀搀 圀䴀䰀 挀漀渀琀攀渀琀猀⸀ The major problems of displaying tabulated data, hyperlinks, navigational aids, 愀渀搀 甀猀攀爀 椀渀瀀甀琀 愀爀攀 搀椀猀挀甀猀猀攀搀Ⰰ 眀椀琀栀 瀀漀猀猀椀戀氀攀 猀漀氀甀琀椀漀渀猀 瀀爀攀猀攀渀琀攀搀 嬀㔀崀⸀ The other project studied the relevance of numerals and keywords for removing 甀渀椀洀瀀漀爀琀愀渀琀 漀爀 洀攀愀渀椀渀最氀攀猀猀 挀漀渀琀攀渀琀猀⸀ 吀栀攀 漀爀椀最椀渀愀氀 挀漀渀琀攀渀琀猀 眀椀氀氀 戀攀 爀攀搀甀挀攀搀 and reorganized to fit the size of mobile phone screens, thus reducing the 挀漀洀洀甀渀椀挀愀琀椀漀渀 挀漀猀琀 愀渀搀 攀渀栀愀渀挀椀渀最 爀攀愀搀愀戀椀氀椀琀礀 嬀㘀崀⸀ 吀栀攀猀攀 瀀爀漀戀氀攀洀猀 眀漀甀氀搀 戀攀 攀渀挀漀甀渀琀攀爀攀搀 if a HTML content that was fit for a relatively larger size screen of PCs transformed 椀渀琀漀 愀 圀䴀䰀 挀漀渀琀攀渀琀 琀栀愀琀 眀愀猀 昀椀琀 昀漀爀 猀洀愀氀氀攀爀 猀椀稀攀 猀挀爀攀攀渀 漀昀 洀漀戀椀氀攀 搀攀瘀椀挀攀猀⸀ We discussed the transformation between i-mode HTML into WAP 2.0 markup language. 吀栀攀爀攀昀漀爀攀Ⰰ 眀攀 愀猀猀甀洀攀搀 琀栀愀琀 琀栀攀 猀挀爀攀攀渀 猀椀稀攀 漀昀 琀栀攀 甀猀攀爀猀 琀攀爀洀椀渀愀氀 搀攀瘀椀挀攀 椀猀 猀愀洀攀 before and after the transformation.
3. i-mode HTML and The WAP 2.0 Markup Language
The markup language of WAP 2.0 can roughly be divided into the following 琀栀爀攀攀 瀀愀爀琀猀⸀㰀⼀瀀㸀 㰀栀㌀㸀㌀⸀ 堀䠀吀䴀䰀 䴀漀戀椀氀攀 倀爀漀昀椀氀攀㰀⼀栀㌀㸀 ऀ㰀瀀㸀吀栀椀猀 椀猀 戀愀猀攀搀 漀渀 堀䠀吀䴀䰀 䈀愀猀椀挀 嬀㜀崀 猀琀愀渀搀愀爀搀椀稀攀搀 戀礀 圀㌀䌀 愀猀 琀栀攀 猀甀戀猀攀琀 漀昀 XHTML 1.1. In addition to XHTML Basic, XHTML Mobile Profile includes some functions 猀甀挀栀 愀猀 琀栀攀 栀爀 琀愀最 ⠀琀栀攀 栀漀爀椀稀漀渀琀愀氀 氀椀渀攀 琀栀愀琀 搀攀氀椀洀椀琀猀 挀漀渀琀攀渀琀⤀Ⰰ 眀栀椀挀栀 椀猀 眀椀搀攀氀礀 used in i-mode HTML content.
3.2 WAP CSS
WAP CSS defines the subset for mobile terminals of the Cascading Style 匀栀攀攀琀 氀攀瘀攀氀 ㈀ ⠀䌀匀匀㈀⤀ 嬀㠀崀Ⰰ 眀栀椀挀栀 椀猀 愀 圀㌀䌀 猀琀愀渀搀愀爀搀 昀漀爀 搀攀昀椀渀椀渀最 琀栀攀 昀漀渀琀Ⰰ 挀漀氀漀爀 愀渀搀 other styles of content. Moreover, it adds functions widely used in i-mode, 猀甀挀栀 愀猀 琀栀攀 洀愀爀焀甀攀攀 ⠀栀漀爀椀稀漀渀琀愀氀 猀挀爀漀氀氀⤀Ⰰ 愀挀挀攀猀猀 欀攀礀 ⠀猀攀氀攀挀琀椀漀渀 漀昀 氀椀渀欀 戀礀 欀攀礀 攀渀琀爀礀⤀ and input mode (automatic switching of Japanese Front End Processor (FEP)). 䘀椀最甀爀攀 猀栀漀眀猀 琀栀攀 爀攀氀愀琀椀漀渀猀 愀洀漀渀最 椀ⴀ洀漀搀攀 䠀吀䴀䰀Ⰰ 堀䠀吀䴀䰀 䴀漀戀椀氀攀 倀爀漀昀椀氀攀 愀渀搀 爀攀氀愀琀攀搀 specifications. As shown in Figure 1, XHTML 1.0 is the redefinition of HTML 4.01 戀礀 甀猀椀渀最 堀䴀䰀Ⰰ 愀渀搀 堀䠀吀䴀䰀 ⸀ 琀栀攀 洀漀搀甀氀愀爀椀稀愀琀椀漀渀 漀昀 堀䠀吀䴀䰀 ⸀ ⸀㰀⼀瀀㸀 ऀ㰀瀀㸀吀栀攀 欀攀礀 挀栀愀爀愀挀琀攀爀椀猀琀椀挀猀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 椀渀 挀漀洀瀀愀爀椀猀漀渀 to i-mode HTML are described below.
1) High Extensibility
The WAP 2.0 markup language can easily be combined with other XML languages, 愀渀搀 挀愀渀 昀氀攀砀椀戀氀礀 愀挀挀漀洀洀漀搀愀琀攀 昀甀琀甀爀攀 攀砀琀攀渀猀椀漀渀猀⸀ 䘀漀爀 攀砀愀洀瀀氀攀Ⰰ 椀昀 椀琀 椀猀 挀漀洀戀椀渀攀搀 眀椀琀栀 XML Signature [9], which is an electronic signature technology for XML standardized by W3C, 椀琀 椀猀 瀀漀猀猀椀戀氀攀 琀漀 愀瀀瀀攀渀搀 愀渀 攀氀攀挀琀爀漀渀椀挀 猀椀最渀愀琀甀爀攀 琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀㰀⼀瀀㸀 㰀栀㐀㸀㈀⤀ 匀琀爀椀挀琀氀礀ⴀ搀攀昀椀渀攀搀 䜀爀愀洀洀愀爀㰀⼀栀㐀㸀 ऀ㰀瀀㸀䄀猀 琀栀攀 最爀愀洀洀愀爀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 椀猀 猀琀爀椀挀琀氀礀 搀攀昀椀渀攀搀 挀漀洀瀀愀爀攀搀 to i-mode HTML, it is easier to develop a WAP 2.0 browser, compared with i-mode HTML browser. 伀渀 琀栀攀 漀琀栀攀爀 栀愀渀搀Ⰰ 挀漀渀琀攀渀琀 搀攀瘀攀氀漀瀀攀爀猀 愀爀攀 爀攀焀甀椀爀攀搀 琀漀 栀愀瘀攀 瀀爀攀挀椀猀攀 挀漀渀琀攀渀琀 挀爀攀愀琀椀漀渀 猀欀椀氀氀猀⸀㰀⼀瀀㸀 㰀栀㐀㸀㌀⤀ 匀攀瀀愀爀愀琀椀漀渀 漀昀 䐀漀挀甀洀攀渀琀 匀琀爀甀挀琀甀爀攀 愀渀搀 匀琀礀氀攀 倀爀攀猀攀渀琀愀琀椀漀渀㰀⼀栀㐀㸀 ऀ㰀瀀㸀吀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 搀攀昀椀渀攀猀 琀栀攀 搀漀挀甀洀攀渀琀 猀琀爀甀挀琀甀爀攀 愀渀搀 琀栀攀 猀琀礀氀攀 presentation separately. For the style presentation, it defines WAP CSS based on CSS2. 䈀礀 甀猀椀渀最 圀䄀倀 䌀匀匀Ⰰ 椀琀 椀猀 瀀漀猀猀椀戀氀攀 琀漀 猀瀀攀挀椀昀礀 琀栀攀 搀漀挀甀洀攀渀琀 猀琀礀氀攀 洀漀爀攀 昀氀攀砀椀戀氀礀 琀栀愀渀 䠀吀䴀䰀⸀㰀⼀瀀㸀 ऀ㰀瀀㸀䘀椀最甀爀攀 ㈀ⴀ 愀渀搀 䘀椀最甀爀攀 ㈀ⴀ㈀ 猀栀漀眀 愀渀 攀砀愀洀瀀氀攀 漀昀 搀漀挀甀洀攀渀琀 猀漀甀爀挀攀 眀爀椀琀琀攀渀 椀渀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 and the WAP 2.0 markup language respectively. Figure 3 illustrates how the content is actually 搀椀猀瀀氀愀礀攀搀⸀ 䄀氀琀栀漀甀最栀 琀栀攀 挀漀渀琀攀渀琀 漀渀 琀栀攀 猀挀爀攀攀渀 愀瀀瀀攀愀爀猀 琀栀攀 猀愀洀攀 ⠀䘀椀最甀爀攀 ㌀⤀Ⰰ 琀栀攀 搀攀猀挀爀椀瀀琀椀漀渀猀 of the content are much different (Figure 2-1, Figure 2-2).
Therefore, it is necessary to transform content written in the WAP 2.0 markup 氀愀渀最甀愀最攀 椀渀琀漀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 猀漀 琀栀愀琀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀 挀愀渀 戀攀 搀椀猀瀀氀愀礀攀搀 accurately in browsers those support only i-mode HTML, that are already deployed in the market. 匀椀洀椀氀愀爀氀礀Ⰰ 椀琀 椀猀 攀猀猀攀渀琀椀愀氀 琀漀 琀爀愀渀猀昀漀爀洀 挀漀渀琀攀渀琀 眀爀椀琀琀攀渀 椀渀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 language so that it can be accurately displayed in browsers that support only the WAP 2.0 markup 氀愀渀最甀愀最攀⸀ 䤀渀 漀爀搀攀爀 琀漀 洀攀攀琀 琀栀攀猀攀 爀攀焀甀椀爀攀洀攀渀琀猀Ⰰ 眀攀 猀琀甀搀椀攀搀 琀栀攀 堀匀䰀吀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 technology that would enable the automatic transformation between i-mode HTML content 愀渀搀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀㰀⼀瀀㸀 㰀搀椀瘀 挀氀愀猀猀㴀∀椀洀愀最攀∀㸀
Figure 2-1. Example of i-mode HTML.
㰀⼀搀椀瘀㸀 㰀搀椀瘀 挀氀愀猀猀㴀∀椀洀愀最攀∀㸀
Figure 3. Example of Display of i-mode HTML and WAP 2.0 Markup Language.
㰀⼀搀椀瘀㸀 㰀栀㌀㸀㌀⸀㌀ 圀䄀倀 攀砀琀攀渀猀椀漀渀猀㰀⼀栀㌀㸀 ऀ㰀瀀㸀圀䄀倀 攀砀琀攀渀猀椀漀渀猀 愀爀攀 甀渀椀焀甀攀 昀攀愀琀甀爀攀猀 猀瀀攀挀椀昀椀攀搀 椀渀 圀䄀倀 琀漀 洀愀椀渀琀愀椀渀 戀愀挀欀眀愀爀搀 挀漀洀瀀愀琀椀戀椀氀椀琀礀 with WML 1.x. It consists of the wml:card element on the Structure Module, the Events Module and 琀栀攀 䌀漀渀琀攀砀琀 ☀愀洀瀀㬀 一愀瘀椀最愀琀椀漀渀 䴀漀搀甀氀攀⸀ 吀栀攀 眀洀氀㨀挀愀爀搀 攀氀攀洀攀渀琀 猀瀀攀挀椀昀椀攀猀 愀 昀爀愀最洀攀渀琀 漀昀 琀栀攀 搀漀挀甀洀攀渀琀 戀漀搀礀⸀ Each wml:card element represents an individual presentation and/or interaction with the user. 吀栀攀 䔀瘀攀渀琀猀 䴀漀搀甀氀攀 椀猀 挀愀瀀愀戀氀攀 漀昀 最攀渀攀爀愀琀椀渀最 攀瘀攀渀琀猀 眀栀攀渀 琀栀攀 甀猀攀爀 椀渀琀攀爀愀挀琀猀 眀椀琀栀 猀攀瘀攀爀愀氀 圀䴀䰀 攀氀攀洀攀渀琀猀 or upon timer expiration. The Context & Navigation Module specifies the User Agent Behaviour, 琀栀攀 搀攀昀椀渀椀琀椀漀渀猀 漀昀 愀 猀漀甀爀挀攀 愀渀挀栀漀爀 昀漀爀 愀 栀礀瀀攀爀氀椀渀欀Ⰰ 琀栀攀 愀猀猀椀最渀洀攀渀琀猀 漀昀 愀渀 愀挀挀攀猀猀 欀攀礀 愀渀搀 琀栀攀 generation of a task, sending a HTTP method, etc. This paper didn’t use the WAP extensions 戀攀挀愀甀猀攀 漀昀 椀琀猀 椀渀挀漀洀瀀愀琀椀戀椀氀椀琀礀 眀椀琀栀 琀栀攀 椀ⴀ洀漀搀攀 䠀吀䴀䰀⸀㰀⼀瀀㸀 㰀栀㈀㸀㐀⸀ 䌀漀渀琀攀渀琀 吀爀愀渀猀昀漀爀洀愀琀椀漀渀 吀攀挀栀渀漀氀漀最礀㰀⼀栀㈀㸀 ऀ㰀瀀㸀䌀漀渀琀攀渀琀 眀爀椀琀琀攀渀 椀渀 䠀吀䴀䰀 愀渀搀 堀䠀吀䴀䰀 挀愀渀 戀攀 瀀爀攀猀攀渀琀攀搀 椀渀 琀攀爀洀猀 漀昀 琀栀攀 瀀愀爀攀渀琀ⴀ挀栀椀氀搀 爀攀氀愀琀椀漀渀猀栀椀瀀 between tags, and can be modeled based on a tree structure as a whole. Accordingly, by considering 猀甀挀栀 愀 挀漀渀琀攀渀琀 猀琀爀甀挀琀甀爀攀Ⰰ 椀琀 椀猀 瀀漀猀猀椀戀氀攀 琀漀 攀砀攀挀甀琀攀 愀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 攀昀昀椀挀椀攀渀琀氀礀⸀ We focused on the eXtensible Stylesheet Language Transformations (XSLT) [10] as a content transformation 琀攀挀栀渀漀氀漀最礀Ⰰ 戀攀挀愀甀猀攀 椀琀 挀漀渀猀椀搀攀爀猀 琀栀攀 挀漀渀琀攀渀琀 猀琀爀甀挀琀甀爀攀 眀栀攀渀 琀爀愀渀猀昀漀爀洀椀渀最 堀䴀䰀 挀漀渀琀攀渀琀⸀ XSLT was originally a part of eXtensible Stylesheet Language (XSL), which is a stylesheet specification 琀栀愀琀 漀昀昀攀爀猀 昀甀渀挀琀椀漀渀猀 猀椀洀椀氀愀爀 琀漀 䌀匀匀⸀ 䄀猀 椀琀猀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 昀甀渀挀琀椀漀渀 椀猀 栀椀最栀氀礀 瘀攀爀猀愀琀椀氀攀 and extremely powerful, it was defined as an independent specification, as XSLT. 圀攀 愀搀漀瀀琀攀搀 堀匀䰀吀 愀猀 琀栀攀 琀攀挀栀渀漀氀漀最礀 漀昀 琀爀愀渀猀昀漀爀洀椀渀最 椀ⴀ洀漀搀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 愀渀搀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 content for these reasons.4.1 XSLT
Figure 4 shows an example of the XSLT stylesheet used when transforming i-mode HTML content 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀吀栀椀猀 攀砀愀洀瀀氀攀 猀栀漀眀猀 栀漀眀 琀栀攀 爀漀漀琀 琀愀最Ⰰ 琀栀攀 琀椀琀氀攀 琀愀最 愀渀搀 the font tag in i-mode HTML content are transformed into the WAP 2.0 markup language content. 吀栀攀 堀匀䰀吀 猀琀礀氀攀猀栀攀攀琀 椀猀 甀猀攀搀 琀漀 搀攀猀椀最渀愀琀攀 琀栀攀 瀀愀爀琀 漀昀 堀䴀䰀 挀漀渀琀攀渀琀猀 琀漀 戀攀 琀爀愀渀猀昀漀爀洀攀搀 甀猀椀渀最 琀栀攀 洀愀琀挀栀 attribute of the template tag, and specify the actual changes, which is described within the template tag.
Figure 4. Example of XSLT Stylesheet.
㰀⼀搀椀瘀㸀 4.2 Document Formatting and Validation
As explained above, due to the loosely defined grammar of HTML, many browsers are capable of 搀椀猀瀀氀愀礀椀渀最 琀栀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 攀瘀攀渀 椀昀 椀琀猀 猀礀渀琀愀砀 椀猀 愀洀戀椀最甀漀甀猀 ⠀攀⸀最⸀ 氀愀挀欀 漀昀 攀渀搀 琀愀最⤀⸀ 䠀漀眀攀瘀攀爀Ⰰ 䠀吀䴀䰀 挀漀渀琀攀渀琀 needs to be written in grammatically correct form, because its content structure is strictly parsed 眀栀攀渀 琀爀愀渀猀昀漀爀洀椀渀最 琀栀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 甀猀椀渀最 堀匀䰀吀⸀ 䘀漀爀 攀砀愀洀瀀氀攀Ⰰ 琀栀攀 愀琀琀爀椀戀甀琀攀 洀甀猀琀 戀攀 攀渀挀氀漀猀攀搀 戀礀 搀漀甀戀氀攀 or single quotation marks as shown in Figure 2-2 (b), and the parent-child relationship between the tags 洀甀猀琀 戀攀 瀀爀漀瀀攀爀氀礀 搀攀猀挀爀椀戀攀搀 愀猀 猀栀漀眀渀 椀渀 䘀椀最甀爀攀 ㈀ⴀ㈀ ⠀攀⤀⸀ 吀栀攀 琀愀猀欀 漀昀 挀漀爀爀攀挀琀椀渀最 琀栀攀 最爀愀洀洀愀琀椀挀愀氀 攀爀爀漀爀 of content in such a manner is called formatting, and HTML content that has been corrected through formatting 椀猀 爀攀昀攀爀爀攀搀 琀漀 愀猀 眀攀氀氀ⴀ昀漀爀洀攀搀 挀漀渀琀攀渀琀⸀ 吀栀攀 挀漀爀爀攀挀琀椀漀渀 漀昀 猀椀洀瀀氀攀 最爀愀洀洀愀琀椀挀愀氀 攀爀爀漀爀猀Ⰰ 猀甀挀栀 愀猀 愀搀搀椀渀最 愀 洀椀猀猀椀渀最 攀渀搀 琀愀最Ⰰ must be performed at this stage. XHTML content does not require document formatting because it is written 愀挀挀漀爀搀椀渀最 琀漀 椀琀猀 猀琀爀椀挀琀氀礀 搀攀昀椀渀攀搀 最爀愀洀洀愀爀⸀㰀⼀瀀㸀 ऀ㰀瀀㸀吀栀攀 搀攀昀椀渀椀琀椀漀渀 漀昀 琀栀攀 最爀愀洀洀愀爀 漀昀 琀栀攀 挀漀渀琀攀渀琀Ⰰ 猀甀挀栀 愀猀 琀栀攀 栀椀攀爀愀爀挀栀礀 愀洀漀渀最 攀氀攀洀攀渀琀猀 愀渀搀 琀栀攀 琀礀瀀攀 of attributes in the content, is referred to as Document Type Definition (DTD), whereas the task of checking 琀栀攀 最爀愀洀洀愀爀 愀猀 琀漀 眀栀攀琀栀攀爀 琀栀攀 挀漀渀琀攀渀琀 椀猀 眀爀椀琀琀攀渀 椀渀 挀漀洀瀀氀椀愀渀挀攀 眀椀琀栀 琀栀攀 搀攀昀椀渀椀琀椀漀渀 漀昀 䐀吀䐀 椀猀 挀愀氀氀攀搀 瘀愀氀椀搀愀琀椀漀渀⸀㰀⼀瀀㸀 ऀ㰀瀀㸀嘀愀氀椀搀愀琀椀漀渀 猀栀漀甀氀搀 戀攀 瀀攀爀昀漀爀洀攀搀 椀渀 漀爀搀攀爀 琀漀 愀猀挀攀爀琀愀椀渀 琀栀愀琀 琀栀攀 挀漀渀琀攀渀琀 爀攀猀甀氀琀椀渀最 昀爀漀洀 愀甀琀漀洀愀琀椀挀 content transformation has no grammatical errors.
5. Overview of Content Transformation Tools
Since the WAP 2.0 markup language was specified to be functionally compatible with the i-mode HTML, 椀琀 椀猀 琀栀攀漀爀攀琀椀挀愀氀氀礀 瀀漀猀猀椀戀氀攀 琀漀 琀爀愀渀猀昀漀爀洀 攀砀椀猀琀椀渀最 椀ⴀ洀漀搀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀ However, it is important to prepare software tools necessary for content transformation and verification, 琀漀 攀渀挀漀甀爀愀最攀 甀猀攀爀猀 愀渀搀 挀漀渀琀攀渀琀 瀀爀漀瘀椀搀攀爀猀 琀漀 洀椀最爀愀琀攀 椀渀琀漀 渀攀眀 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 攀渀瘀椀爀漀渀洀攀渀琀猀 猀甀挀栀 愀猀 琀栀攀 圀䄀倀 ㈀⸀ markup language content transformation technology is the key technology for such migration. 䤀琀 椀猀 攀砀琀爀攀洀攀氀礀 甀猀攀昀甀氀 昀漀爀 瀀爀攀瀀愀爀椀渀最 挀漀渀琀攀渀琀 最攀渀攀爀愀琀椀漀渀 愀渀搀 瘀攀爀椀昀椀挀愀琀椀漀渀 攀渀瘀椀爀漀渀洀攀渀琀猀 昀漀爀 愀 渀攀眀 洀愀爀欀甀瀀 氀愀渀最甀愀最攀Ⰰ based on the existing content development environment. The prototype software environment is described below, 眀栀椀挀栀 椀猀 搀攀瘀攀氀漀瀀攀搀 琀漀 瘀攀爀椀昀礀 琀栀攀 昀攀愀猀椀戀椀氀椀琀礀 漀昀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 甀猀椀渀最 堀匀䰀吀⸀㰀⼀瀀㸀 ऀ㰀瀀㸀匀椀渀挀攀 琀栀攀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 瀀爀漀琀漀琀礀瀀攀 猀漀昀琀眀愀爀攀 眀愀猀 搀攀瘀攀氀漀瀀攀搀 昀漀爀 琀栀攀 瀀甀爀瀀漀猀攀 漀昀 瘀攀爀椀昀礀椀渀最 the functional compatibility of the WAP 2.0 markup language with the existing i-mode HTML, the scope of 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 椀猀 氀椀洀椀琀攀搀 琀漀 琀栀攀 猀甀戀猀攀琀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 琀栀愀琀 昀甀渀挀琀椀漀渀愀氀氀礀 挀漀爀爀攀猀瀀漀渀搀猀 to the i-mode HTML. Figure 5 shows the software configuration for transforming i-mode HTML content 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀ 吀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 瀀爀漀挀攀猀猀 挀漀渀猀椀猀琀猀 洀愀椀渀氀礀 漀昀 琀栀爀攀攀 猀琀攀瀀猀㨀 (a) formatting, (b) XSLT transformation, and (c) validation. As the prototype software, a number of existing 猀漀昀琀眀愀爀攀 眀愀猀 甀猀攀搀 琀漀 爀攀搀甀挀攀 琀栀攀 搀攀瘀攀氀漀瀀洀攀渀琀 琀椀洀攀 挀漀猀琀猀⸀ 吀愀戀氀攀 猀栀漀眀猀 琀栀攀 攀砀椀猀琀椀渀最 猀漀昀琀眀愀爀攀 甀猀攀搀 椀渀 琀栀攀 瀀爀漀琀漀琀礀瀀攀 software. The rules for transforming i-mode HTML content into the WAP 2.0 markup language content ⠀椀⸀攀⸀ 堀匀䰀吀 猀琀礀氀攀猀栀攀攀琀⤀ 眀愀猀 渀攀眀氀礀 搀攀昀椀渀攀搀 甀猀椀渀最 琀栀攀 猀琀愀渀搀愀爀搀 昀甀渀挀琀椀漀渀猀 漀昀 堀匀䰀吀 戀愀猀攀搀 漀渀 琀栀攀 猀瀀攀挀椀昀椀挀愀琀椀漀渀猀 of i-mode HTML and the WAP 2.0 markup language.
The transformation steps are as follows. Firstly, the content is formatted after converting 琀栀攀 昀甀氀氀ⴀ眀椀搀琀栀 欀愀渀愀 挀栀愀爀愀挀琀攀爀猀 愀渀搀 栀愀氀昀ⴀ眀椀搀琀栀 欀愀渀愀 挀栀愀爀愀挀琀攀爀猀 戀愀猀攀搀 漀渀 匀栀椀昀琀 䨀愀瀀愀渀 䤀渀搀甀猀琀爀椀愀氀 匀琀愀渀搀愀爀搀 ⠀匀䨀䤀匀⤀ in the i-mode HTML content into 10-decimal character codes, because the formatting tool (i.e. HTML Tidy) 搀漀攀猀 渀漀琀 猀甀瀀瀀漀爀琀 匀䨀䤀匀⸀ 匀攀挀漀渀搀氀礀Ⰰ 愀昀琀攀爀 昀漀爀洀愀琀琀椀渀最 椀ⴀ洀漀搀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 甀猀椀渀最 䠀吀䴀䰀 吀椀搀礀Ⰰ 琀栀攀 昀甀氀氀ⴀ眀椀搀琀栀 欀愀渀愀 characters and the half-width kana characters shown in the form of characters codes in the formatted i-mode HTML 挀漀渀琀攀渀琀 愀爀攀 挀漀渀瘀攀爀琀攀搀 戀愀挀欀 椀渀琀漀 匀䨀䤀匀Ⰰ 愀渀搀 愀渀 堀䴀䰀 搀攀挀氀愀爀愀琀椀漀渀 椀猀 愀搀搀攀搀Ⰰ 眀栀椀挀栀 椀猀 渀攀挀攀猀猀愀爀礀 昀漀爀 琀栀攀 堀匀䰀吀 攀渀最椀渀攀 瀀爀漀挀攀猀猀⸀ Finally, the formatted i-mode HTML content is transformed into the WAP 2.0 markup language content using 琀栀攀 堀匀䰀吀 攀渀最椀渀攀Ⰰ 愀渀搀 琀栀攀 琀爀愀渀猀昀漀爀洀攀搀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀 椀猀 瘀攀爀椀昀椀攀搀⸀ 吀栀攀 愀戀漀瘀攀ⴀ洀攀渀琀椀漀渀攀搀 匀䨀䤀匀 conversion steps are not needed in case of English characters.
For the reverse-transformation of content, that is, the transformation of the WAP 2.0 markup language 挀漀渀琀攀渀琀 椀渀琀漀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀Ⰰ 愀 猀攀瀀愀爀愀琀攀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 爀甀氀攀 ⠀椀⸀攀⸀ 堀匀䰀吀 匀琀礀氀攀猀栀攀攀琀⤀ 眀愀猀 搀攀昀椀渀攀搀 in a similar manner. The reverse transformation involves only the XSLT transformation process. 䄀猀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 椀猀 椀渀栀攀爀攀渀琀氀礀 椀渀 挀漀洀瀀氀椀愀渀挀攀 眀椀琀栀 堀䴀䰀Ⰰ 昀漀爀洀愀琀琀椀渀最 椀猀 渀漀琀 爀攀焀甀椀爀攀搀⸀ Validation is also unnecessary because i-mode HTML is not in compliance with XML and therefore has no DTD.
Figure 5. Software Configuration.
㰀⼀搀椀瘀㸀 㰀栀㈀㸀㘀⸀ 䌀漀渀琀攀渀琀 吀爀愀渀猀昀漀爀洀愀琀椀漀渀 䔀砀瀀攀爀椀洀攀渀琀 愀渀搀 䄀渀愀氀礀猀椀猀㰀⼀栀㈀㸀 㰀栀㌀㸀㘀⸀ 伀瘀攀爀瘀椀攀眀 漀昀 䌀漀渀琀攀渀琀 吀爀愀渀猀昀漀爀洀愀琀椀漀渀 䔀砀瀀攀爀椀洀攀渀琀㰀⼀栀㌀㸀 ऀ㰀瀀㸀吀栀攀 攀砀瀀攀爀椀洀攀渀琀 漀昀 琀爀愀渀猀昀漀爀洀椀渀最 椀ⴀ洀漀搀攀 䠀吀䴀䰀 挀漀渀琀攀渀琀 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀 was performed with respect to two types of content: static content, which is already stored as a file 椀渀 琀栀攀 挀漀渀琀攀渀琀 猀攀爀瘀攀爀㬀 愀渀搀 搀礀渀愀洀椀挀 挀漀渀琀攀渀琀Ⰰ 眀栀椀挀栀 椀猀 最攀渀攀爀愀琀攀搀 戀礀 䌀䜀䤀 愀渀搀 匀攀爀瘀攀爀 匀椀搀攀 䤀渀挀氀甀搀攀 ⠀匀匀䤀⤀ in response to the user’s request. As part of the experiment using static content, a test was performed 眀椀琀栀 爀攀猀瀀攀挀琀 琀漀 爀攀瘀攀爀猀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 椀⸀攀⸀ 琀栀攀 爀攀ⴀ琀爀愀渀猀昀漀爀洀愀琀椀漀渀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀 that had resulted from transformation, back into i-mode HTML content.The transformation experiment using static content involved the measurement of: the success 爀愀琀攀 漀昀 琀栀攀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 瀀爀漀挀攀猀猀 椀琀猀攀氀昀㬀 琀栀攀 猀甀挀挀攀猀猀 爀愀琀攀 漀昀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 爀攀氀愀琀椀渀最 琀漀 琀愀最猀 and attributes; changes in the content size before and after transformation; and the time consumed 愀琀 攀愀挀栀 猀琀攀瀀 椀渀 琀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 瀀爀漀挀攀猀猀⸀ 吀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 攀砀瀀攀爀椀洀攀渀琀 甀猀椀渀最 搀礀渀愀洀椀挀 挀漀渀琀攀渀琀 椀渀瘀漀氀瘀攀搀㨀 the measurement of the transformation processing time by dividing it into the time consumed in acquiring 琀栀攀 挀漀渀琀攀渀琀 愀渀搀 琀栀攀 琀椀洀攀 挀漀渀猀甀洀攀搀 椀渀 琀爀愀渀猀昀漀爀洀椀渀最 琀栀攀 挀漀渀琀攀渀琀㬀 愀渀搀 琀栀攀 愀渀愀氀礀猀椀猀 漀昀 琀爀攀渀搀猀 椀渀 琀栀攀 挀漀爀爀攀氀愀琀椀漀渀 between the content size and the transformation processing time.
As the content subject to evaluation, i-mode’s flagship utility content called Eki-mae Tanken Club ⠀栀琀琀瀀㨀⼀⼀攀欀椀琀愀渀⸀挀漀洀⼀ 椀渀 䨀愀瀀愀渀攀猀攀 昀漀爀 倀䌀 戀爀漀眀猀攀爀⤀ 眀愀猀 甀猀攀搀⸀ 䔀欀椀ⴀ洀愀攀 吀愀渀欀攀渀 䌀氀甀戀 椀猀 漀渀攀 漀昀 琀栀攀 漀昀昀椀挀椀愀氀 猀椀琀攀猀 of i-mode, which gives information about station in Japan. We selected several contents of Eki-mae Tanken Club 椀渀 琀栀攀 瘀椀挀椀渀椀琀礀 漀昀 琀栀攀 吀漀欀礀漀 洀攀琀爀漀瀀漀氀椀琀愀渀 愀爀攀愀 ⠀愀戀漀甀琀 猀琀愀琀椀漀渀猀⤀⸀ Table 2 shows the contents used in the experiment that are classified into 5 service types; 1) guidance 漀渀 栀漀眀 琀漀 琀爀愀渀猀昀攀爀 昀爀漀洀 猀琀愀琀椀漀渀 琀漀 猀琀愀琀椀漀渀Ⰰ ㈀⤀ 眀栀攀渀 琀栀攀 氀愀猀琀 琀爀愀椀渀 氀攀愀瘀攀猀 琀栀攀 猀琀愀琀椀漀渀Ⰰ ㌀⤀ 琀栀攀 琀爀愀椀渀 猀挀栀攀搀甀氀攀Ⰰ 4) the weather at the station and 5) the directions to certain places in the vicinity. There are 249 contents 琀栀愀琀 椀渀挀氀甀搀攀 琀栀攀 搀礀渀愀洀椀挀愀氀氀礀 最攀渀攀爀愀琀攀搀 挀漀渀琀攀渀琀猀 愀渀搀 㜀 猀琀愀琀椀挀 挀漀渀琀攀渀琀猀 ⠀椀⸀攀⸀ 琀栀攀 琀漀瀀 瀀愀最攀猀 漀昀 攀愀挀栀 猀攀爀瘀椀挀攀⤀⸀ The content of Eki-mae Tanken Club also omitted some end tags to reduce the size of the content. Therefore, 琀栀攀猀攀 挀漀渀琀攀渀琀猀 愀爀攀 渀漀琀 愀氀眀愀礀猀 椀渀 挀漀洀瀀氀椀愀渀挀攀 眀椀琀栀 琀栀攀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 猀瀀攀挀椀昀椀挀愀琀椀漀渀 猀琀爀椀挀琀氀礀Ⰰ 戀甀琀 椀ⴀ洀漀搀攀 瀀栀漀渀攀猀 can display these contents properly.
The dynamic content transformation process is as follows. At first, the client sends an HTTP request 琀漀 琀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 猀攀爀瘀攀爀⸀ 吀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 猀攀爀瘀攀爀 爀攀氀愀礀猀 琀栀攀 䠀吀吀倀 爀攀焀甀攀猀琀 琀漀 琀栀攀 挀漀渀琀攀渀琀 猀攀爀瘀攀爀 琀漀 最攀琀 the i-mode HTML content (This process is called “fetch”). The transformation server writes the received content 椀渀琀漀 愀 琀攀洀瀀漀爀愀爀礀 昀椀氀攀 ⠀吀栀椀猀 瀀爀漀挀攀猀猀 椀猀 挀愀氀氀攀搀 ᰀ椠渀瀀甀琀ᴀ⤠⸀ 吀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 猀攀爀瘀攀爀 椀渀瘀漀欀攀猀 琀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 software and executes the transformation from the i-mode HTML content into the WAP 2.0 markup language content ⠀吀栀椀猀 瀀爀漀挀攀猀猀 椀猀 挀愀氀氀攀搀 ᰀ琠爀愀渀猀昀漀爀洀ᴀ⤠⸀ 吀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 猀攀爀瘀攀爀 猀攀渀搀猀 琀栀攀 琀爀愀渀猀昀漀爀洀攀搀 挀漀渀琀攀渀琀 琀漀 琀栀攀 挀氀椀攀渀琀 (This is called “output”). The response time taken when the client accesses the content server via the transformation 猀攀爀瘀攀爀 椀猀 琀栀攀 琀漀琀愀氀 愀洀漀甀渀琀 漀昀 琀椀洀攀 漀昀 琀栀攀 昀攀琀挀栀Ⰰ 椀渀瀀甀琀Ⰰ 琀爀愀渀猀昀漀爀洀 愀渀搀 漀甀琀瀀甀琀⸀㰀⼀瀀㸀 㰀搀椀瘀 挀氀愀猀猀㴀∀椀洀愀最攀∀㸀
6.3 Experiment Results and Analysis
6.3.1 Success Rate of Content Transformation
Measurements were taken so as to determine the success rate of the content transformation process itself 愀渀搀 琀栀攀 猀甀挀挀攀猀猀 爀愀琀攀 漀昀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 眀椀琀栀 爀攀最愀爀搀 琀漀 椀渀搀椀瘀椀搀甀愀氀 琀愀最猀 愀渀搀 愀琀琀爀椀戀甀琀攀猀⸀ 䄀猀 昀漀爀 琀栀攀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 process, transformation was deemed successful when all processes —formatting, XSLT transformation and validation— 眀攀爀攀 挀愀爀爀椀攀搀 漀甀琀⸀ 吀愀戀氀攀 ㌀ 猀栀漀眀猀 琀栀攀 爀攀猀甀氀琀 漀昀 琀栀攀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 攀砀瀀攀爀椀洀攀渀琀⸀ 䄀挀挀漀爀搀椀渀最 琀漀 琀栀攀 洀攀愀猀甀爀攀洀攀渀琀 results of transformation processes performed with respect to 249 contents, the success rate of transformation was 100%, 瀀爀漀瘀椀搀攀搀 琀栀愀琀 琀栀攀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 眀愀猀 眀椀琀栀椀渀 琀栀攀 猀挀漀瀀攀 漀昀 琀愀最猀 愀渀搀 愀琀琀爀椀戀甀琀攀猀 猀瀀攀挀椀昀椀攀搀 椀渀 琀栀攀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 猀瀀攀挀椀昀椀挀愀琀椀漀渀⸀㰀⼀瀀㸀 ऀ㰀瀀㸀圀栀攀渀 琀爀愀渀猀昀漀爀洀椀渀最 ㈀㐀㤀 挀漀渀琀攀渀琀猀Ⰰ 琀栀攀 昀漀爀洀愀琀琀椀渀最 琀漀漀氀 椀猀猀甀攀搀 渀漀 攀爀爀漀爀 洀攀猀猀愀最攀Ⰰ 戀甀琀 㘀㜀㜀㔀 眀愀爀渀椀渀最 洀攀猀猀愀最攀猀 were issued. Table 4 shows the nature of the warning messages that were actually issued. The process associated 眀椀琀栀 攀愀挀栀 眀愀爀渀椀渀最 洀攀猀猀愀最攀 椀猀 愀猀 昀漀氀氀漀眀猀⸀㰀⼀瀀㸀 㰀漀氀 琀礀瀀攀㴀∀愀∀㸀
Table 4. Warning Message
Figure 8 compares the size of tag, which includes the attributes, between i-mode HTML and the WAP 2.0 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 爀攀猀瀀攀挀琀椀瘀攀氀礀⸀ 吀栀攀 瀀氀漀琀琀椀渀最 搀愀琀愀 椀猀 爀攀漀爀搀攀爀攀搀 戀礀 琀栀攀 搀椀昀昀攀爀攀渀挀攀 漀昀 琀愀最 猀椀稀攀 椀渀 琀栀攀 椀渀挀爀攀愀猀椀渀最 漀爀搀攀爀⸀ As Figure 8 shows, with respect to the difference of tag size, there seems to be several typical characteristics. 圀栀攀渀 愀 琀愀最 猀椀稀攀 搀漀攀猀 渀漀琀 栀愀瘀攀 愀渀礀 愀琀琀爀椀戀甀琀攀猀Ⰰ 琀栀攀 琀愀最 猀椀稀攀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 椀猀 攀焀甀愀氀 琀漀 琀栀愀琀 of i-mode HTML. When a tag in the WAP 2.0 markup language has an attribute defined by WAP CSS, 眀栀椀挀栀 栀愀猀 愀 氀愀爀最攀 愀洀漀甀渀琀 漀昀 挀栀愀爀愀挀琀攀爀猀Ⰰ 琀栀攀 琀愀最 猀椀稀攀 漀昀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 椀猀 氀愀爀最攀爀 琀栀愀渀 琀栀愀琀 漀昀 椀ⴀ洀漀搀攀 䠀吀䴀䰀⸀ As compared with the WAP 2.0 markup language against i-mode HTML, the tag size of the WAP 2.0 markup language, 椀渀挀氀甀搀攀猀 愀琀琀爀椀戀甀琀攀猀 椀猀 愀戀漀甀琀 㠀 戀礀琀攀猀 氀愀爀最攀爀 琀栀愀渀 琀栀愀琀 漀昀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 漀渀 琀栀攀 愀瘀攀爀愀最攀⸀ 䔀焀甀愀琀椀漀渀 椀猀 愀 猀椀洀瀀氀攀 approximate expression of the increased size (Y) after the transformation. In this equation, it is assumed 琀栀愀琀 琀栀攀 椀渀挀爀攀愀猀攀搀 猀椀稀攀 漀昀 挀漀渀琀攀渀琀 椀猀 瀀爀漀瀀漀爀琀椀漀渀愀氀 琀漀 琀栀攀 渀甀洀戀攀爀 漀昀 琀愀最猀 椀渀 挀漀渀琀攀渀琀⸀ 圀栀攀爀攀 堀 搀攀渀漀琀攀猀 “the number of tags”.
Y = 8X + 156 (1)
㰀搀椀瘀 挀氀愀猀猀㴀∀椀洀愀最攀∀㸀
Figure 9 compares the increased size of the transformed WAP 2.0 markup language content between 琀栀攀 攀砀瀀攀爀椀洀攀渀琀愀氀 瘀愀氀甀攀猀 愀渀搀 琀栀攀 挀愀氀挀甀氀愀琀攀搀 瘀愀氀甀攀猀 漀昀 䔀焀甀愀琀椀漀渀 ⸀ 䄀猀 䘀椀最甀爀攀 㤀 猀栀漀眀猀Ⰰ 琀栀攀 攀砀瀀攀爀椀洀攀渀琀愀氀 瘀愀氀甀攀 is not necessarily to be equal to the calculated value. The content that had increased a little in size after 戀攀椀渀最 琀爀愀渀猀昀漀爀洀攀搀 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀 ⠀愀戀漀甀琀 ㌀ 戀礀琀攀猀 漀爀 氀攀猀猀⤀ 琀攀渀搀攀搀 琀漀 甀猀攀 琀栀攀 琀愀最猀 that have no attribute. With respect to the dynamically generated content, the CGI program adds some attributes 愀甀琀漀洀愀琀椀挀愀氀氀礀 爀攀最愀爀搀氀攀猀猀 漀昀 琀栀攀 攀砀椀猀琀攀渀挀攀 漀昀 琀栀攀椀爀 瘀愀氀甀攀猀⸀ 䤀昀 琀栀攀 愀琀琀爀椀戀甀琀攀 搀漀攀猀渀ᤀ琠 栀愀瘀攀 愀渀 愀瘀愀椀氀愀戀氀攀 瘀愀氀甀攀Ⰰ the transformation software will delete the attribute. This is a reason for the size decrement of the transformed 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀⸀ 伀渀 琀栀攀 漀琀栀攀爀 栀愀渀搀Ⰰ 琀栀攀 挀漀渀琀攀渀琀 琀栀愀琀 栀愀搀 椀渀挀爀攀愀猀攀搀 猀椀最渀椀昀椀挀愀渀琀氀礀 椀渀 猀椀稀攀 愀昀琀攀爀 being transformed into the WAP 2.0 markup language content (500 bytes or more) tended to omit the end tag 愀渀搀 栀愀瘀攀 愀 氀愀爀最攀 渀甀洀戀攀爀 漀昀 ᰀ☠愀洀瀀㬀ᴀ†椀渀 琀栀攀 愀琀琀爀椀戀甀琀攀 瘀愀氀甀攀⸀㰀⼀瀀㸀 㰀搀椀瘀 挀氀愀猀猀㴀∀椀洀愀最攀∀㸀
6.3.3 Transformation Processing Time of Static Content
Figure 10 shows the time consumed in processing the transformation of static content. 吀栀攀 昀漀爀洀愀琀琀椀渀最 瀀爀漀挀攀猀猀 愀挀挀漀甀渀琀猀 昀漀爀 愀戀漀甀琀 ─ 漀昀 琀栀攀 琀漀琀愀氀 琀椀洀攀 椀渀挀氀甀搀椀渀最 琀栀攀 匀䨀䤀匀 瀀爀漀挀攀猀猀椀渀最Ⰰ while the XSLT transformation process and the validation process accounted for approximately 45% each, 眀栀椀挀栀 椀猀 愀 猀椀最渀椀昀椀挀愀渀琀 瀀漀爀琀椀漀渀⸀ 吀栀攀 瀀爀漀挀攀猀猀椀渀最 琀椀洀攀 琀攀渀搀攀搀 琀漀 椀渀挀爀攀愀猀攀 搀攀瀀攀渀搀椀渀最 漀渀 攀椀琀栀攀爀 琀栀攀 挀漀渀琀攀渀琀 猀椀稀攀 or the number of tags and attributes in the content.
Figure 10. Breakdown of Transformation Processing Time.
㰀⼀搀椀瘀㸀 㰀栀㐀㸀㘀⸀㌀⸀㐀 吀爀愀渀猀昀漀爀洀愀琀椀漀渀 倀爀漀挀攀猀猀椀渀最 吀椀洀攀 漀昀 䐀礀渀愀洀椀挀 䌀漀渀琀攀渀琀㰀⼀栀㐀㸀 ऀ㰀瀀㸀䘀椀最甀爀攀 椀猀 琀栀攀 戀爀攀愀欀搀漀眀渀 漀昀 琀栀攀 瀀爀漀挀攀猀猀椀渀最 琀椀洀攀 挀氀愀猀猀椀昀椀攀搀 椀渀 琀栀攀 愀戀漀瘀攀 洀攀渀琀椀漀渀攀搀 㔀 猀攀爀瘀椀挀攀 渀愀洀攀猀⸀ Figure 11 shows that the fetch time, the time taken for the transformation server to acquire the content 昀爀漀洀 琀栀攀 挀漀渀琀攀渀琀 猀攀爀瘀攀爀Ⰰ 愀挀挀漀甀渀琀猀 昀漀爀 洀漀爀攀 漀瘀攀爀 㔀 ─ 漀昀 琀栀攀 爀攀猀瀀漀渀猀攀 琀椀洀攀⸀ 吀栀攀 爀攀猀瀀漀渀猀攀 琀椀洀攀 搀攀瀀攀渀搀猀 栀攀愀瘀椀氀礀 on the fetch time against the transform time. The fetch time seems to depend on a sort of content 戀攀挀愀甀猀攀 琀栀攀 挀漀渀琀攀渀琀 眀愀猀 最攀渀攀爀愀琀攀搀 戀礀 䌀䜀䤀 瀀爀漀最爀愀洀⸀ 䘀漀爀 椀渀猀琀愀渀挀攀Ⰰ 琀栀攀 搀椀爀攀挀琀椀漀渀猀 挀漀渀琀攀渀琀 琀愀欀攀猀 琀栀攀 琀椀洀攀 琀漀 最攀渀攀爀愀琀攀 map image attachments dynamically, so it takes a long time to perform the fetch process. The other way around, 琀栀攀 琀爀愀渀猀昀攀爀 最甀椀搀愀渀挀攀 ⠀倀漀猀猀椀戀椀氀椀琀椀攀猀⤀ 挀漀渀琀攀渀琀 琀愀欀攀猀 瘀攀爀礀 猀栀漀爀琀 搀攀氀愀礀 琀椀洀攀 戀攀挀愀甀猀攀 椀琀猀 最攀渀攀爀愀琀椀渀最 瀀爀漀挀攀猀猀 is very simple.Consequently, it is verified that our transformation software provides sufficient function 愀渀搀 瀀攀爀昀漀爀洀愀渀挀攀 挀栀愀爀愀挀琀攀爀椀猀琀椀挀猀 椀渀 挀愀猀攀 漀昀 琀栀攀 搀礀渀愀洀椀挀 挀漀渀琀攀渀琀 愀渀搀 琀栀攀 猀琀愀琀椀挀 挀漀渀琀攀渀琀⸀ 伀渀 琀栀攀 漀琀栀攀爀 栀愀渀搀Ⰰ with respect to the dynamic content, as the fetch time taken to acquire the content accounts for a large portion 漀昀 琀栀攀 琀漀琀愀氀 爀攀猀瀀漀渀猀攀 琀椀洀攀Ⰰ 椀琀 猀攀攀洀猀 琀漀 戀攀 攀昀昀攀挀琀椀瘀攀 琀漀 挀愀挀栀攀 琀栀攀 琀爀愀渀猀昀漀爀洀攀搀 挀漀渀琀攀渀琀 愀渀搀 爀攀甀猀攀 椀琀 昀漀爀 猀甀戀猀攀焀甀攀渀琀 requests. And it seems to be important to omit the validation process in the transformation, 戀攀挀愀甀猀攀 琀栀攀 瘀愀氀椀搀愀琀椀漀渀 瀀爀漀挀攀猀猀 琀椀洀攀 戀攀挀漀洀攀猀 氀愀爀最攀爀 椀渀 瀀爀漀瀀漀爀琀椀漀渀 琀漀 琀栀攀 猀椀稀攀 漀昀 挀漀渀琀攀渀琀 愀渀搀 琀栀攀 渀甀洀戀攀爀 漀昀 䠀吀䴀䰀 琀愀最猀⸀ As we applied the existing commercial server to the experiment, the feasibility of system reconstructions was verified, 戀甀琀 琀栀攀 猀礀猀琀攀洀 瀀攀爀昀漀爀洀愀渀挀攀 洀椀最栀琀 渀漀琀 戀攀 椀洀瀀爀漀瘀攀搀⸀ 吀栀攀 昀攀琀挀栀 琀椀洀攀 琀栀愀琀 愀挀栀椀攀瘀攀搀 昀爀漀洀 琀栀攀 攀砀瀀攀爀椀洀攀渀琀 洀椀最栀琀 be strongly dependent on the system configuration.
Figure 11. Processing Time by Content.
㰀⼀搀椀瘀㸀 㰀栀㈀㸀㜀⸀ 䌀漀渀挀氀甀猀椀漀渀㰀⼀栀㈀㸀 ऀ㰀瀀㸀吀栀椀猀 瀀愀瀀攀爀 搀椀猀挀甀猀猀攀搀 琀栀攀 爀攀猀甀氀琀猀 漀昀 琀栀攀 愀甀琀漀洀愀琀椀挀 挀漀渀琀攀渀琀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 攀砀瀀攀爀椀洀攀渀琀 挀漀渀挀攀爀渀椀渀最 i-mode HTML content and the WAP 2.0 markup language content. We confirmed that 100% of i-mode HTML content 挀漀甀氀搀 戀攀 琀爀愀渀猀昀漀爀洀攀搀 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀 挀漀渀琀攀渀琀Ⰰ 愀猀 昀愀爀 愀猀 琀栀攀 挀漀渀琀攀渀琀 䔀欀椀ⴀ洀愀攀 吀愀渀欀攀渀 䌀氀甀戀 provided by Toshiba iValue Creation Company is concerned. This content transformation experiment is conducted 漀渀氀礀 漀渀 琀栀攀 戀愀猀攀 漀昀 㔀 琀礀瀀攀猀 漀昀 猀攀爀瘀椀挀攀猀 昀漀爀 琀爀愀椀渀 琀爀愀渀猀瀀漀爀琀 渀愀瘀椀最愀琀椀漀渀⸀ 吀栀攀爀攀昀漀爀攀Ⰰ 椀琀 椀猀 渀攀挀攀猀猀愀爀礀 琀栀攀 昀甀爀琀栀攀爀 experiment with much more sample contents to verify the feasibility of content transformation for the general 甀猀攀 瀀甀爀瀀漀猀攀⸀ 䤀渀 琀栀攀 昀甀琀甀爀攀Ⰰ 眀攀 瀀氀愀渀 琀漀 瘀攀爀椀昀礀 琀栀攀 昀攀愀猀椀戀椀氀椀琀礀 漀昀 琀栀椀猀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 琀攀挀栀渀漀氀漀最礀 戀愀猀攀搀 on the evaluation of a wider range of content, and work on the development of transformation software tools 琀漀眀愀爀搀 椀琀猀 挀漀洀洀攀爀挀椀愀氀 甀猀攀⸀ Several logical contradictions depended on the ambiguous grammar syntax of the i-mode HTML might be happened 愀昀琀攀爀 琀爀愀渀猀昀漀爀洀愀琀椀漀渀 昀爀漀洀 琀栀攀 椀ⴀ洀漀搀攀 䠀吀䴀䰀 椀渀琀漀 琀栀攀 圀䄀倀 ㈀⸀ 洀愀爀欀甀瀀 氀愀渀最甀愀最攀⸀ The contradictions are, for instance, the lack of the indispensable elements, no li element in the ol element, 琀栀攀 爀攀搀甀渀搀愀渀挀礀 漀昀 琀栀攀 吀䤀吀䰀䔀 攀氀攀洀攀渀琀 琀栀愀琀 猀栀漀甀氀搀 戀攀 漀渀氀礀 漀渀攀 椀渀 愀 搀漀挀甀洀攀渀琀Ⰰ 愀 戀氀漀挀欀 氀攀瘀攀氀 攀氀攀洀攀渀琀 挀愀洀攀 into an inline element’s section after the transformation had executed, etc. It might be hard for the XSLT 琀漀 猀漀氀瘀攀 琀栀攀 挀漀渀琀爀愀搀椀挀琀椀漀渀猀⸀ 䤀琀 椀猀 瘀攀爀礀 椀洀瀀漀爀琀愀渀琀 琀漀 挀甀猀琀漀洀椀稀攀 琀栀攀 昀漀爀洀愀琀琀椀渀最 琀漀漀氀 昀漀爀 琀栀攀 瀀甀爀瀀漀猀攀 漀昀 爀攀挀漀瘀攀爀礀 of the contradictions.8. Acknowledgments
We would like to thank Dr. Hirotaka Nakano and Mr. Osamu Takahashi, DoCoMo Multimedia Laboratories, 昀漀爀 愀氀氀漀眀椀渀最 甀猀 琀漀 瀀甀琀 椀渀琀漀 瀀爀愀挀琀椀挀攀 琀栀椀猀 樀漀椀渀琀 爀攀猀攀愀爀挀栀 愀渀搀 攀砀瀀攀爀椀洀攀渀琀⸀ 吀栀椀猀 眀漀爀欀 眀愀猀 瀀愀爀琀椀愀氀氀礀 猀甀瀀瀀漀爀琀攀搀 by TOSHIBA CORPORATION e-SOLUTIONS COMPANY, TOSHIBA IT-SOLUTIONS CORPORATION and DoCoMo i-mode Business Department.
[5] :
[7] :
[8] :
[9] :
[10] :