JP2003036223A - Markup document conversion method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that in converting a document described in a markup language including a procedural script language, into a document of a different markup language, it is difficult to completely convert the procedural script language itself if the specifications of the script languages in the markup languages are different between before and after conversion. SOLUTION: In conversion of markup languages, scripts, which are included in a document to be converted, are executed in a conversion device. This enables a browser, which displays markup languages that do not support script languages, to reproduce operations described with scripts in the document to be converted.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention executes a document described in a content description language including a procedural script language on a browser that does not have a procedural script language or uses a different procedural script language. Markup document conversion method for.

[0002]

2. Description of the Related Art Most of documents on the Internet and Intranet are described in HTML (Hyper Text Markup Language) format documents used in the World Wide Web (WWW). HTML is SGM
Although it was developed as a markup language based on L, information can be sent from a client browser to a server (web server) that distributes HTML documents by a mechanism called a form. By placing a program that sends back an HTML document corresponding to the sent information to the browser on the web server,
You can create interactive content.

Form elements in HTML are f
These are the orm element and the input element. The input element can represent various input components depending on the value of the type attribute. name attribute and val in the input element
The ue attribute can be set, and "submi" is set as the type attribute.
When an input element having a value of “t” is clicked, a pair of the value of the value of the value attribute and the value of the value of the value attribute of all the input elements within the form element including the input element is transmitted to the server side.

As HTML has become more sophisticated, HTM
Java, which is a procedural script language in L documents
The method of embedding (registered trademark) Script has been generalized, and has been recognized as an official specification in HTML 4.0.
When Java Script is used, the information input by the user can be processed on the browser without being sent to the web server, and a screen corresponding to the input information can be displayed on the browser.

Java Script is described in a script element. The written script is HTML
Runs when the document is loaded. Also, a script that is activated when an element is clicked can be described as the onclick attribute of the element.
An event such as onclick is called a unique event. Scripts can be used to describe interactive operations using unique events.

[0006] B established as a markup language for digital data broadcasting by the Association of Radio Industries and Businesses (ARIB)
ML (Broadcast Markup Langu
(age) is a markup language based on XML, and like HTML, a script described in ECMAScript can be embedded. ECMAScr
ipt is a scripting language that standardizes Java Script. In BS digital data broadcasting that started in December 2000, BML according to a profile called "operation guideline for basic service" is used. Since the form is not operated in the operation guideline for the basic service, it is necessary to describe all interactive contents by using ECMAScript.

On the other hand, the i-mode of NTT Docomo and the J Sky Web of J-Phone only support the display of restricted HTML documents. Both support forms, but Java Sc
It does not support embedding scripting languages such as ript. Therefore, interactive content should be described using forms only. Hereinafter, in order to distinguish the HTML document having such restrictions from the latest HTML that supports the script language, the HTML for mobile terminals is described.
Call.

[0008] WML (Wireless) was established by WAP Forum as a markup language for mobile terminals.
In Markup Language), postf
With the field element, it is possible to realize an interactive operation similar to the HTML form. Also, unlike portable HTML,
Scripts with unique events and WMLScript are also supported, but the language specification is ECMAScript.
And Java Script.

Java Scri used in HTML
Although the language specifications of ECMAScript used in pt and BML are almost the same, an interface for operating the document body from the script language (DOM "Document O
"bject Model")
Even if the HTML part of the document described in 4.0 is rewritten to BML, it cannot be executed on the BML browser because the script specifications are different.

Although there is a strong demand for mutual conversion of WWW documents, digital data broadcasting documents, and mobile terminal documents, as mentioned above, the languages used in each document are:
There is a big difference in creating interactive contents with a procedural script language.

In Japanese Patent Laid-Open No. 2000-194612,
An HTML document can be converted into a wireless application protocol (WA
P), a method of converting into a document described in a wireless markup language (WML) or the like is disclosed. This method converts only the markup language part according to the device settings,
Does not convert the script language. Therefore, when the HTML document including the script language is converted, the information described in the script language is lost. The method of ignoring the script language in this way is called Conventional Example 1.

In Japanese Patent Laid-Open No. 2001-5716, HT
A method for converting an ML document into an MHEG document is disclosed. This method is not only for converting markup languages,
The script language described in the HTML document is converted into the corresponding MHEG action. But HT
Since the description ability of Java Script and the description ability of MHEG action used in the ML document are different,
It is not possible to transfer all the information described in the script language in the TML document into the MHEG document. A method of converting each script language as described above is called Conventional Example 2.

[0013]

In Conventional Example 1, the script language included in the markup language is ignored, so that important information described in the script language is not reflected in the conversion result. In this method, even if a BML document that realizes a dialog with a user is converted into an HTML document for a mobile terminal by using a script language, the HTML document generated as a result of the conversion lacks a dialog operation.

In Conventional Example 2, the script language included in the markup language is converted for each script language, so that the information described in the script language is reflected to some extent in the conversion result. However, the specifications of script language and DOM vary depending on the language and browser,
There are rare cases where it can be completely converted. Further, when converted to an HTML document for a mobile terminal which originally does not support the script language, the information described in the script language will be lost as in the first conventional example.

In any case, even if an HTML document or a BML document which interacts with a user using a script language is converted into an HTML for a mobile terminal, the conversion result shows the interaction process of the original document. I can't reproduce it.

However, since the interactive process is an essential function for many contents, it is desirable to convert the markup language while reproducing the interactive process of the script described in the markup language of the conversion source.

Therefore, according to the present invention, a markup language including a procedural script language is reproduced by a browser supporting a markup language different from the markup language while reproducing the interactive operation of the script included in the original document. It is an object to provide a markup document conversion method for enabling display. It is another object of the present invention to provide a markup document conversion method in which the conversion result can be manually corrected.

[0018]

A markup document conversion method according to the present invention executes a script included in a markup language of a conversion source on a server program for conversion to convert the markup document of the conversion source. The feature is that the language is dynamically changed, and then it is converted into the markup language of the conversion destination according to the conversion rule between the markup languages and sent to the browser.

According to the markup document conversion method of the present invention, the script language processing system supported by the conversion source markup language operates on the server program so that the script language and the script language can be processed independently of the browser specifications. It enables the server side to prepare a processing system that closely conforms to the DOM specifications, and reliably realizes the operation that can be realized by the browser in the script description included in the conversion source document.

[0020]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below. (Embodiment 1) FIG. 1 shows a block diagram of a markup document conversion method according to the first embodiment. Source document 11
Is written in a markup language LB including a procedural script language LA. The browser 13 is a device that displays a document described in the markup language LC.

The conversion device 12 is means for displaying the conversion source document on the browser. The conversion device 12 includes a conversion source document reading unit 14, a script execution unit 17, an event conversion unit 18, a markup language conversion unit 19, and an event processing unit 22. The conversion source document reading means 14
The conversion source document is read and divided into a script portion 16 and a markup portion 15 included in the conversion source document 11. The script execution means 17 is a language processing system that supports the script language LA. This script execution means 17
Is divided by the conversion source document reading means 14,
The script portion 16 is read and executed. If there is a description to change the document content in the script, the content of the markup part is changed as described in the script.

The markup portion 15 is converted into a converted document 21 described in the markup language LC by the event conversion means 18 and the markup language conversion means 19. Here, the event conversion unit 18 converts the unique event in the conversion source document into an element (input element in the case of HTML) that sends information to the server. At this time, the script set as the handler of the unique event is set as the information to be sent to the server.
The markup language conversion means 19 uses the markup language L.
A means for converting A into a markup language LC. The converted document is sent to the browser and displayed to the user. When an element that transmits information to the server is activated by the user pressing a button on the browser, the event processing unit 22 extracts the set script from the transmitted data and executes the script. The conversion processing is executed by the means 17, and then the event conversion means 18 and the markup language conversion means 19 are executed to update the converted document,
Send it to the browser again. By repeating the above, the interactive operation in the script language described in the conversion source markup language can be converted into the interactive operation in the form of the conversion destination markup language.

FIG. 2 and FIG. 3 are explanatory diagrams of the conversion of the interactive operation. FIG. 2 is a diagram when a document including a script is directly displayed / browsed by a browser that supports the document. When a user tries to view a document,
The browser 32 receives the document 33 from the server 31 and displays it on the screen. When the user makes an input such as pressing a button, the script described as the unique event handler in the document is executed on the browser, and the document update 35
Is executed.

FIG. 3 is a diagram when the markup document conversion method of the first embodiment is used to convert a document including a script so that it can be displayed / browsed by a browser that does not support the document. When a user tries to view a document, the browser sends a conversion device 4 from the server.
The document converted by 1 is received and displayed on the screen.
Next, when the user makes an input such as pressing a button, the button is converted into an element for transmitting data to the server, and therefore data transmission 38 is performed to the server. Since the transmitted data is the script associated with the unique event, the conversion device 41 in the server executes this script to update the document 39. Then, the result of converting the updated document is sent to the browser, and the document reception 4
0 is performed. As described above, the apparent dialogue operation of the user from FIG. 3 is the same as the dialogue operation of FIG.

In the first conventional example, only the markup language was converted on the server program, but the markup document conversion method of the first embodiment can reproduce the interactive operation described by the script. In addition, since the script language processing system supported by the conversion source markup language runs on the server program, a processing system faithfully conforming to the script language and DOM specifications is executed on the server side regardless of the browser specifications. Can be prepared at. Therefore, unlike the method of converting each script language as in the second conventional example, the operation that can be realized by the browser in the script description included in the conversion source document can be surely realized.

Next, a specific example of this markup document conversion method will be described. Here, the BML document described according to the operation guideline for the basic service,
HTML for i-mode (Compact HTML, CH
A specific example of conversion to TML (hereinafter, referred to as Example 1-1)
That)). Although the conversion destination document is CHTML, in this embodiment 1-1, even if the conversion destination markup language is the latest HTML 4.0, J-Sky is used.
It can be applied even to HTML for the Web.

FIG. 4 shows an example of a BML document which is a conversion source. A script described in ECMAScript can be embedded in a BML document by using a Script element. In the example of FIG. 4, the 12th to 18th lines are scripts. This document operates as shown in FIG. 5 on the BML browser. First, as shown on the left of Fig. 5,
The texts "user registration" and "input completed" and the area for entering the password are displayed. When the user enters the password and presses the "Enter" button,
Script function sho described in the script element
wNext is executed. The showNext function is D
By manipulating the visibility style property through the OM, the previously unseen text "next" is displayed (Fig. 5, right).

The details of each means shown in FIG. 1 in the embodiment 1-1 will be described below. Conversion source document reading means 14
Checks the script element in the BML document and
When the ipt element is present, the inside of the script element is output as the document (conversion source document script portion) 16 and the one without the script element is output as the document (conversion source document markup portion) 15. here,
The documents 15 and 16 do not necessarily have to take the form of files, and may be held as data expanded on the memory. Document 15 at this point is shown in FIG. 6, and document 16 is shown in FIG.
Shown in.

Next, the script executing means 17 executes the script shown in FIG. In this embodiment, the script executing means 17 uses the BML ECMAScript.
Supports t and DOM interfaces. In the case of the script in FIG. 7, only the function definition statement is described in the script, and therefore, at this stage, there is no change to the document 15 even after the script is executed.

Next, the event conversion means 18 converts the description of the unique event included in the BML document shown in FIG. 6 into the description of the CHTML form. The event converting means 18 in this Embodiment 1-1 is shown in FIG. The event converting means 18 is applied to all the elements in the BML document. First, the element is onc
It is checked whether the lick attribute is set, and if it is set, inp is performed by the method described in step S15.
Convert to ut element. Therefore, the id attribute in FIG. 6 is ok
The p element of is converted to an input element. onclic
If the k attribute is not set, the element is input
Check whether it is an element, and if it is an input element, i
The value set in the d attribute is added as the name attribute (step S14). Therefore, the id attribute in FIG.
In the input element of "pass", n called "pass"
The ame attribute is added. Next, it is checked whether the element is a body element, and if it is a body element, f
The orm element is output as a child element (step S1)
6).

The document having the unique event description converted by the event conversion means 18 is converted into a CHTML document (FIG. 8) by the markup language conversion means 19. Markup language conversion means 19 in the embodiment 1-1
Is realized by interpreting the conversion table shown in FIG. 10 in order from the top for all the elements in the document.

First, the style of the element is examined, and vis
If the ibilty property is hidden, that element is ignored. Because the visibility characteristic is h
This is because the element of idden is not displayed on the original BML. For example, in the p element (“next”) whose id attribute is next in FIG. 6, the visibility is hidden
Since it is set to, it is not output in FIG. Next, if the element is a bml element, the tag name is changed to the html element and the element is output. Then the element is sty
If it is a le element, that element is ignored. Because C
This is because HTML does not support style sheets. Similarly, the case of the object element is also ignored. This is because the image / moving image / sound indicated by the object element is not displayed on the CHTML browser. Here, an example in which the image format is converted into the img element by performing file format conversion or size conversion without ignoring the image can be considered. Similarly, beite
The m element and the event element are also ignored. These are CHT
This is because it cannot be expressed in an ML document. For other elements, the style attribute, the id attribute, and the class attribute are deleted, and the element is output as it is in the CHTML document. styl
The e attribute and the like are deleted because these attributes are not supported in CHTML.

The CHTML document output as a result of the markup language converting means 19 is as shown in FIG. The CHTML document in FIG. 8 is displayed on the CHTML browser as shown in the left part of FIG. Here, when the user inputs the password and presses the input button, the form data shown in FIG. 12 is returned. This information is passed to the event processing means 20.

The event processing means 20 is represented by the procedure shown in FIG. Name, va passed as form data
The procedure shown in steps S31 to S33 is executed for each pair of lues. First, nam
It is determined whether the beginning of e is @ (step S
31). Since the character @ cannot be used in the id attribute of BML described according to the operation guideline for basic services, if @ is at the beginning, step S
Oncl of the conversion source element that generated the input element in 14
Since it can be specified as the ick attribute, the name without @ from the beginning is interpreted as a script, and the script executing means 17 is activated (step S32). @
If is not at the beginning, it can be specified as the input element generated in step S17, and therefore the process of step S33 is executed. When the above process is completed for all name and value pairs, the markup language conversion means 1
9 is started and the process ends (step S34).

For example, when the form data of FIG. 12 is returned, first, regarding name = “pass”, the value attribute value of the input element whose id attribute value in the conversion source document 15 is “pass” is determined in step S33. 12
34 ". Also, name =""@ showNe.
xt (); ”, sh
Run the script owNext () ;. From FIG. 7, when showNext () ;; is executed, the function showNext is executed, and i is called pass.
The value attribute value of the element having d is acquired in the variable pw (C1). In the case of this example, "1" is obtained in step S33.
Since it is set to 234 ", pw is" 1234 "
Is substituted. Next, the length of pw is examined (C
2). Since the length of pw is 4, the code in the if statement is executed, and the visibil of the element with the id next
The property “ty” is changed to “visible”.

After that, the converted document output by the markup language conversion means being activated is as shown in FIG.
The CHTML browser displays as shown on the right side of FIG.

Next, an embodiment in which the conversion destination document is WML (hereinafter referred to as Embodiment 1-2) will be described. In the embodiment 1-2, the event converting means 18 and the markup language converting means 19 among the respective means constituting FIG. 1 are different from those of the embodiment 1-1.

The event converting means 18 is shown in FIGS.
Indicated by. Step S44 of FIG. 15 is different from the event converting means in the embodiment 1-1 shown in FIG. in
CHTML (HTM) that sends a form using the put element
Unlike L), in WML, do element, go element, pos
This is because the form is sent out by a combination of tfield elements. The markup language conversion means 19
This is realized by interpreting the conversion table shown in FIG. 17 in order from the top for all the elements in the document.

FIG. 18 shows an example in which the BML document shown in FIG. 4 is converted into a WML document according to the embodiment 1-2. This document is displayed on the WML browser as shown in the left part of FIG. Here, when the user inputs the password and presses the input button, the form data shown in FIG. 19 is returned. This information is passed to the event processing means 20. The event processing means 20 in the embodiment 1-2 is the same as that in the embodiment 1-1. The WML document output after execution of the event processing means is as shown in FIG. This document is displayed on the WML browser as shown on the right side of FIG.

As described above, according to the first embodiment, the CH that does not support the script language does not support the screen transition of the BML document whose screen is changed by using the script language.
A markup language that includes a procedural script language, such as can be implemented on a TML browser or WML browser, is reproduced by a browser that supports a different markup language than the markup language. While there is an effect that can be displayed.

(Second Embodiment) Next, a second embodiment of the present invention will be described. In the second embodiment, by dividing the function of the conversion device 12 described in the first embodiment into a pre-conversion device and a modified document conversion device, the operation of the script included in the conversion source markup language is executed. While reproducing, it is also possible to manually correct the conversion result. FIG. 27 shows a conversion method using the pre-conversion device and the modified document conversion device. The conversion source document 11 is once converted by the pre-conversion device 51. The converted result is stored as the corrected converted document 52. The converted document for correction 52 is manually modified by the user or modified by another program by the document editing device 53. The changed document is saved as the corrected document 54. The corrected document 54 is distributed to the browser by the corrected document conversion / distribution device 55.

The structure of the pre-conversion device 51 is shown in FIG. The pre-conversion device 51 is a conversion source document reading means 1
4, event conversion means 18, static format conversion means 56. The conversion source document reading means 14 and the event conversion means 18 are the same as those of the conversion device 12 shown in FIG. The static format conversion means 56 is the markup language conversion means 19 except for the conversion rules that may cause loss of information depending on the conversion conditions. It should be noted that the conversion rule that may cause information loss depending on the conversion condition is included in the dynamic format conversion means 63 described later. For example, the rule for converting a tag of a certain element of the conversion source document 11 into another tag is included in the static format conversion unit 56 because information is not lost due to the conversion condition. On the other hand, when the number of child elements of a certain element of the conversion source document 11 is less than or equal to a certain number, the rule to ignore the element (not output as the conversion result) causes information loss due to the condition at the time of conversion. , Included in the dynamic format conversion means 63. Since the conversion that causes information loss is excluded depending on the conversion condition, the contents of the corrected converted document 52 are different from the converted document 21 and are not affected by the execution result of the script, and are suitable for manual correction. Will be things.
The document editing device 53 is any means capable of editing a document described in the markup language LC.

The structure of the corrected document conversion / delivery device 55 is shown in FIG. The corrected document conversion / delivery device 55 includes a conversion source document reading unit 14, a difference reflection unit 61, a dynamic format conversion unit 63, an event processing unit 22, a script execution unit 17, and a difference generation unit 65. Here, the conversion source document reading means 14 and the event processing means 2
2. The script execution means 17 is the same as the means constituting the conversion device 12. Dynamic format conversion means 63
As described above, is a conversion rule extracted from the markup language conversion means 19 that may cause information loss depending on the conversion condition. The bidirectional server communication means 66 in FIG. 29 is not an essential function for the conversion method using the pre-conversion device 51 and the corrected document conversion / delivery device 55.
The two-way server communication means 66 is used in the second embodiment described later.
This will be explained in Section 4. The corrected document 54 includes the difference reflection means 6
1 reflects the contents of the difference information 62 generated by executing the script. Next, the dynamic format conversion means 63 performs conversion that was not considered by the static format conversion means 56. As a result, the converted document 64 that reproduces the document change generated by the execution of the script while storing the change to the corrected document made by the document editing device 53 is generated and transmitted to the browser.

Next, a specific example of this markup document conversion method will be described. Here, the BML document described according to the operation guideline for the basic service,
HTML for i-mode (CompAct HTML, CH
A specific example of conversion into TML (hereinafter, referred to as Example 2-1)
That)). Although the conversion destination document is CHTML, in this embodiment 2-1, even if the conversion destination markup language is the latest HTML 4.0, J Sky
It can be applied even to HTML for the Web. FIG. 4 is an example of a BML document that is a conversion source. For BML documents, E
Script the script described in CMASscript
It can be embedded using the t element. In the example of FIG. 4, the 12th to 18th lines are scripts. This document operates as shown in FIG. 5 on the BML browser. First, as shown in the left side of FIG. 5, the texts "user registration" and "input completed" and the area for entering the password are displayed between them. User enters password,
When the "input complete" button is pressed, the script function showNext described in the script element is executed. The showNext function is
By manipulating the ability style property, the text "next" which was not visible until then is displayed (Fig. 5, right).

The details of each means of FIG. 1 in the embodiment 2-1 will be described below. Conversion source document reading means 14
Checks the script element in the BML document and
When the ipt element is present, the inside of the script element is output as the document (conversion source document script portion) 16 and the one without the script element is output as the document (conversion source document markup portion) 15. here,
The documents 15 and 16 do not necessarily have to take the form of files, and may be held as data expanded on the memory. Document 15 at this point is shown in FIG. 6, and document 16 is shown in FIG.
Shown in. Next, the script execution means 17 executes the script shown in FIG. In this embodiment 2-1, the script execution means 17 uses the BML ECMAScript.
And DOM interface support. In the case of the script in FIG. 7, only the function definition statement is described in the script, and therefore, at this stage, there is no change to the document 15 even after the script is executed.

Next, the event conversion means 18 converts the description of the unique event contained in the BML document shown in FIG. 6 into the description of the CHTML form. The event converting means 18 in this Embodiment 2-1 is shown in FIG. The event converting means 18 is applied to all the elements in the BML document. First, the element is onc
It is checked whether the lick attribute is set, and if it is set, inp is performed by the method described in step S15.
Convert to ut element. Therefore, the id attribute in FIG. 6 is ok
The p element of is converted to an input element. onclic
If the k attribute is not set, the element is input
Check whether it is an element, and if it is an input element, i
The value set in the d attribute is added as the name attribute (step S14). Therefore, the id attribute in FIG.
The input element of "pass" is "pass" na
The me attribute is added. Next, it checks whether the element is a body element, and if it is a body element, fo
The rm element is output as a child element (step S16).

The document whose unique event description has been converted by the event converting means 18 is converted into a CHTML document (FIG. 8) by the markup language converting means 19. The markup language conversion means 19 in this embodiment is realized by sequentially interpreting the conversion table shown in FIG. 10 from the top for all the elements in the document. First, the style of the element is examined, and if the visibility property is hidden, the element is ignored. This is because the element whose visibility property is hidden is not displayed on the original BML. For example, the p element (“next”) whose id attribute is next in FIG.
Since sibility is set to hidden, it is not output in FIG. Then the element is BML
If it is an element, the tag name is changed to an HTML element and output. Next, if the element is a style element, the element is ignored. This is because style sheets are not supported in CHTML. Similarly, obj
Ignore the case of ect element. Because the object
This is to prevent the image, moving image, and sound indicated by the element from being displayed on the CHTML browser. Here, an example in which the image format is converted into the img element by performing file format conversion or size conversion without ignoring the image can be considered. Similarly, beitem element and event
Ignore the element as well. This is because these cannot be expressed in the CHTML document. Other elements are style attributes,
Delete the id attribute and class attribute and leave CHT
Output in ML document. The reason why the style attribute and the like are deleted is that these attributes are not supported in CHTML. The CHTML document output as a result of the markup language conversion means 19 is as shown in FIG. 8C
The HTML document is displayed on the CHTML browser as shown on the left side of FIG. Here, when the user inputs the password and presses the input button, the form data shown in FIG. 12 is returned. This information is passed to the event processing means 22.

The event processing means 22 is represented by the procedure shown in FIG. Name, va passed as form data
The procedure shown in steps S31 to S33 is executed for each pair of lues. First, nam
It is determined whether the beginning of e is @ (step S
31). Since the character @ cannot be used in the id attribute of BML described according to the operation guideline for BS digital broadcasting, if @ is at the beginning, step S1
Oncli of the conversion source element that generated the input element in 8.
Since it can be specified as the ck attribute, the name without @ from the beginning is interpreted as a script, and the script execution means 17 is activated (step S32). If @ is not at the beginning, i generated in step S14
Since it can be specified as an nput element, the process of step S33 is executed. When the above process is completed for all name and value pairs, the markup language conversion means 19
Is started and terminated (step S34).

For example, when the form data of FIG. 12 is returned, first, regarding name = “pass”, the value attribute value of the input element whose id attribute value in the conversion source document 15 is “pass” is determined in step S33. 12
34 ". Also, name =""@ showNe.
xt (); ”, sh
Run the script owNext () ;. From FIG. 7, when showNext (); is executed, the function showNext is executed, and i is called pass.
The value attribute value of the element having d is acquired in the variable pw (C1). In the case of this example, "1" is obtained in step S33.
Since it is set to 234 ", pw is" 1234 "
Is substituted. Next, the length of pw is examined (C
2). Since the length of pw is 4, the code in the if statement is executed, and the visibil of the element with the id next
The property “ty” is changed to “visible”. After that, the converted document output by the markup language conversion means being activated is as shown in FIG. 14, and displayed on the CHTML browser as shown on the right in FIG.

Next, the embodiment 2-2 in the case where the conversion destination document is WML will be described. In the embodiment 2-2, the event converting means 18 and the markup language converting means 19 among the means constituting FIG. 1 are different from those of the embodiment 2-1. The event converting means 18 is shown in FIGS. Step S44 in FIG. 15 is different from the event converting means in the embodiment 2-1 shown in FIG. input
Unlike CHTML (HTML) which sends a form by element, in WML, do element, go element, postfi
This is because the form is sent out by combining the eld elements. The markup language conversion means 19 is realized by sequentially interpreting the conversion table shown in FIG. 17 from the top for all the elements in the document.

FIG. 18 shows an example in which the BML document shown in FIG. 4 is converted into a WML document according to the embodiment 2-2. This document is displayed on the WML browser as shown in the left part of FIG. Here, when the user inputs the password and presses the input button, the form data shown in FIG. 19 is returned. This information is passed to the event processing means 22. The event processing means 22 in the embodiment 2-2 is the same as that in the embodiment 2-1. The WML document output after execution of the event processing means is as shown in FIG. This document is displayed on the WML browser as shown on the right side of FIG.

Next, the conversion destination document is JavaScript.
And CSS2 (Cascading Style Shee)
Example 2-3 in the case of HTML 4.0 supporting ts Level2) will be described. This Example 2
In No. 3, by using Java Script and CSS2, it is possible to reproduce a screen configuration closer to that of the original document than in Example 2-1. In the example 2-3, the event converting means 18 and the markup language converting means 19 of the respective means constituting FIG. 1 are different from those of the example 2-1 and the example 2-2. The event converting means 18 is shown in FIG. Step S55, step S56, and step S57 in FIG. 21 are different from the event converting means in the embodiment 2-1 shown in FIG. In Example 2-1, the onclic
The event firing was converted to form transmission to the server by converting the element in which the k attribute was set to the input element. However, in this embodiment 2-3, onclic is used.
Event firing is converted to form submission to the server by replacing the script set in the k attribute with a script that submits the form. Since the element in which the onclick attribute is set is not changed to the input element, the screen configuration close to that of the original document can be reproduced.

The script for submitting the form is as shown in FIG. This script temporarily enables the disabled attribute of the input element passed to the first argument x by setting it to false, and sends out the form element passed to the second argument y. Therefore, the transmitted data includes a pair of the name attribute and the value attribute set in the input element passed to the first argument x.
The script of FIG. 22 is converted to the HTM in step S57.
It is output during L. Also, i passed as the first argument x
The nput element is output in step S55. onc
The value of the lick attribute is converted into a function call statement that activates the script function of FIG. 22 (step S56). The markup language conversion means 19 interprets the conversion table shown in FIG. 23 in order from the top for all the elements in the document. Further, the style attribute of each element and the conversion table shown in FIG. 24 are applied to the inside of the style element.

FIG. 25 shows an example in which the BML document shown in FIG. 4 is converted into an HTML document by the embodiment 2-3. This document is displayed as shown on the left side of FIG. 5 in the HTML browser that supports Javascript and CSS2. Here, when the user inputs the password and presses the input button, the form data shown in FIG. 19 is returned. This information is passed to the event processing means 22. This example 2-3
The event processing means 22 in is the same as that in the embodiment 2-1. The HTML document output after execution of the event processing means is as shown in FIG. This document is displayed on the HTML browser as shown on the right side of FIG.

Next, a description will be given of the embodiment 2-4 in the case of using the pre-translation device and having the bidirectional server communication means. In this embodiment 2-4, similar to the above-mentioned embodiment 2-1, it is assumed that the BML document is converted into CHTML, but the present invention can be applied to the case where the conversion source document or the conversion destination document is different from this. Further, the communication function with the bidirectional server by the bidirectional server communication means can be applied to the conversion device shown in FIG. 1 if the conversion source document is BML. In Example 2-4, B shown in FIG. 30 is used as the conversion source document.
Assume an ML document. This BML document first displays a screen as shown on the left in FIG. On this screen, the text "Please enter the answer", the area for entering the answer, and the input completion button are displayed. When the user inputs the answer and presses the input completion button, the script function enter described in the script element is executed. The enter function uses the two-way communication function of BML to input the answer to the telephone number "00-0000-0".
000 "to the bidirectional server. The bidirectional server returns the character string" ok "if the transmitted data is correct, and returns the character string" ng "otherwise.

In the Enterer function, if the character string returned from the bidirectional server is "ok", I called msg
In the text area indicated by D, the character string "correct answer" is inserted, and otherwise, the character string "disappear" is inserted. As a result, when the input answer is correct, the screen display is as shown in the upper right of FIG. 31, and when it is incorrect, the screen as shown in the lower right of FIG. 31 is displayed. This document is first read by the pre-conversion device 51 shown in FIG. The pre-conversion device 51 includes a conversion source document reading unit 14, an event conversion unit 18, and a static format conversion unit 56. The conversion source document reading unit 14 and the event conversion unit 18 are
Same as Example 2-1. Therefore, the conversion source document reading unit 14 reads the markup portion of the conversion source document shown in FIG. 30, and converts the p element having the onclick attribute and the id attribute “ok” into the input element. Next, the static format conversion means 56 interprets the conversion table shown in FIG. 36 in order from the top for all the elements in the document. Comparing this with the markup language conversion means shown in FIG. 10, there is no processing of “not outputting elements whose visibility style characteristic is hidden” and processing of “ignoring id attribute”. These two processes are executed by the dynamic format conversion means 63. As a result, the corrected converted document 52 generated by the pre-conversion device 51 is as shown in FIG.

Then, the document editing apparatus 53 edits the corrected converted document. The document editing device 53 is a general-purpose HTM.
L authoring tool and text editor. Since the modified converted document is a normal HTML document, it can be edited with a general-purpose HTML authoring tool or a text editor. FIG. 33 is an example of the corrected document 54 generated as a result of editing. Here, FIG.
For the second document, shorten the text "Please enter answer" to "Enter answer" (4th line in Fig. 33),
I changed the p element with id attribute "msg" to the font element, added the color attribute with the value "red", and moved it to the beginning of the document.

Next, with reference to FIG. 29, the process of sending this corrected document to the CHTML browser will be described. The corrected document is first processed by the difference reflecting means 61. The difference reflecting means is means for reflecting the difference information 62 on the corrected document. The difference information 62 is generated by the difference generation means 65. When the difference reflection means 61 is executed for the first time, the difference generation means 65 has never been executed,
The difference information is empty. Therefore, the output from the difference reflection means 61 is the same as that of the corrected document. Difference reflection means 6
The output from 1 is processed by the dynamic format conversion means 63. The dynamic format conversion means is executed by interpreting the conversion table shown in FIG. 37 in order from the top. When FIG. 37 is applied to the document shown in FIG. 33, “ms
The font element with id "g" is deleted (in the source document markup part, the visibility style characteristic of the element with id "msg" is "hidd").
en ") and i described in each element
The d attribute is deleted. Therefore, the converted document 64 output as a result is as shown in FIG.

The CHTML content of FIG. 34 is CHT.
38 is displayed on the ML browser. Here, when the user inputs the answer and presses the input completion button, the form data shown in FIG. 39 is returned. This information is passed to the event processing means 22. The operation of the event processing means 22 is the same as that in the embodiment 2-1. Figure 3
When the form data of 9 is returned, the script called enter (); is executed in step S32.
In this embodiment 2-4, the script execution means 17 uses D
When writing to the OM, the difference generation means 65 is called, and the connect, s of the browser object
endTextData, receiveTextDa
At the time of calling each method of ta and disconnect, the method of the same name prepared in the bidirectional server communication means 66 is called.

The bidirectional server communication means 66 has the method shown in FIG. Since each method has the same function as the bidirectional communication function implemented in the BML browser, it is possible to communicate with the bidirectional server through the telephone line.
The bidirectional server communication unit 66 does not need to have the same function as the bidirectional communication function implemented in the BML browser. For example, if the interactive server is divided into a part that receives a call from the telephone line and a part that processes the received data, and the latter is connected to a higher speed network, the interactive server communication means connect, s
A method call such as endTextData can also be implemented so as to be converted into communication for the latter.

The difference generating means 65 is D by a script.
This is a means for saving the contents of changes in the OM tree as difference information. In Example 2-4, the value of the attribute of the element is changed, the content of the text node is changed, and the style is changed (“Atrat”, element id, attribute name, changed attribute value) and (“ "text", id of parent element, appearance position of text node in parent element, changed text)
, ("Style", i of the style-changed element
Save as a list of d, style property name, new style property value).

The processing of the script executing means 17 when the enter function is executed is as follows. 1st line: The value attribute of the element whose id is answer is acquired. The value attribute is an event processing means (see FIG. 1).
Since it is set to "1" in step S33) of 3,
“1” is substituted for ans. Second line: connect of the bidirectional server communication means 66
The function is called to establish a means of communication with the bidirectional server. Third line: sendTex of the bidirectional server communication means 66
The tData function is called and the character string "1" is sent to the bidirectional server. 4th line: receive of the bidirectional server communication means 66
The TextData function is called to receive the string "ok" or "ng" from the interactive server. Line 5: discon of the bidirectional server communication means 66
The ect function is called to disconnect the communication means with the bidirectional server. Lines 6-10: When the received character string is "ok", the difference generation means 65 causes ("text", "ms").
The change information "g", 1, "correct answer") is stored.
In the case of "ng", ("text", "msg", 1,
The difference information of “out” is stored. 11th line: By the difference generation means 65 (("styl"
e ”,“ msg, ”“ visibility ”,“ vis ”
The difference information "ible") is saved. Next, the generated difference information is reflected in the corrected document by the difference reflecting unit 61. The difference reflecting unit 61 is the difference information ("text") of the text node. , "Msg", 1, "correct answer"), the content of the first text node of the font element having the id attribute "msg" in the corrected document is changed to "correct answer" (the entered answer is correct) If).
In addition, style difference information (“style”, “ms”
g ”,“ visibility ”,“ visibl ”
e)), a font having an id attribute "msg"
Change the visibility property of the element to visible.

The changed corrected document is converted by the dynamic format conversion means 63, and as a result, the converted document shown in FIG. 35 is generated. CHT in FIG.
The ML document is displayed in the CHMTL browser as shown in the upper right of FIG.

According to the second embodiment, the screen transition of the BML document whose screen is changed by using the script language,
A markup language that includes a procedural scripting language, such as can be implemented on a CHTML or WML browser that does not support a scripting language, is a browser that supports a different markup language than the one included in the original document. There is an effect that the interactive operation can be displayed while being reproduced. For example, the screen transition of a BML document that changes the screen by using a script language is performed on a CHTML browser or a WML browser that does not support the script language, or an HTM having a script language with different specifications.
It can be realized on the L browser. In addition, the communication function with the bidirectional server described in the BML document with a script can be reproduced. Further, even when the conversion result needs to be manually corrected, it is possible to realize the document conversion and distribution in which the content manually corrected is saved and the document change by the script is also reflected.

[0065]

According to the present invention, a markup language including a procedural script language is reproduced by a browser supporting a markup language different from the markup language, and the interactive operation of the script included in the original document is reproduced. While there is an effect that can be displayed. For example, the screen transition of a BML document whose screen is changed by using a script language is displayed on a CHTML browser that does not support the script language or W
It can be realized on an ML browser or an HTML browser having a script language with different specifications. Further, there is an effect that the communication function with the bidirectional server described by the script in the BML document can be reproduced. Further, even when the conversion result needs to be manually corrected, there is an effect that it is possible to realize the document conversion and distribution in which the content manually corrected is saved and the document change by the script is also reflected.

[Brief description of drawings]

FIG. 1 is a block diagram showing a markup document conversion system according to an embodiment of the present invention.

FIG. 2 is an explanatory diagram of conversion of a dialogue operation by the markup document conversion method according to the embodiment of the present invention, and an explanation showing an operation when a document including a script is executed on a browser supporting the document. It is a figure.

FIG. 3 is an explanatory diagram of conversion of an interactive operation by the markup document conversion method according to the embodiment of the present invention, in which a document including a script is converted so that it can be displayed / viewed by a browser that does not support the document. It is explanatory drawing which shows a case.

FIG. 4 is a diagram showing an example of a BML document that is a conversion source in the markup document conversion method according to the embodiment of the present invention.

FIG. 5 is a diagram showing a display example of a BML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 6 is a diagram showing an example of a markup document extracted by a conversion source document reading unit in the markup document conversion method according to the exemplary embodiment of the present invention.

FIG. 7 is a diagram showing an example of a script extracted by a conversion source document reading unit in the markup document conversion system according to the embodiment of the present invention.

FIG. 8 is a diagram showing an example of a converted CHTML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 9 is a flowchart showing the operation of the event conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 10 is a diagram showing a conversion table used by the markup language conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 11 is a diagram showing a display example of a converted CHTML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 12 is a diagram showing an example of form data transmitted in the markup document conversion system according to the embodiment of the present invention.

FIG. 13 is a flowchart showing the operation of the event processing means in the markup document conversion system according to the embodiment of the present invention.

FIG. 14 is a diagram showing an example of a CHTML document after executing the event processing means in the markup document conversion system according to the embodiment of the present invention.

FIG. 15 is a flowchart showing an operation of an event conversion unit in the markup document conversion system according to the exemplary embodiment of the present invention.

FIG. 16 is a postfield in the event converting means in the markup document converting system according to the embodiment of the present invention.
It is a figure which shows the production | generation means of d element.

FIG. 17 is a diagram showing a conversion table used by markup language conversion means data in the markup document conversion system according to the embodiment of the present invention.

FIG. 18 is a diagram showing a display example of a WML document after conversion in the markup document conversion system according to the embodiment of the present invention.

FIG. 19 is a diagram showing an example of form data transmitted in the markup document conversion system according to the embodiment of the present invention.

FIG. 20 is a diagram showing an example of a WML document after execution of event processing means in the markup document conversion system according to the embodiment of the present invention.

FIG. 21 is a flowchart showing the operation of the event conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 22 is a diagram showing an example of a form transmission script in the markup document conversion system according to the embodiment of the present invention.

FIG. 23 is an explanatory diagram showing conversion rules (element conversion) of the markup language conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 24 is an explanatory diagram showing conversion rules (style conversion) of the markup language conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 25 is a diagram showing an example of an HTML document after conversion in the markup document conversion system according to the embodiment of the present invention.

FIG. 26 is a diagram showing an example of an HTML document after execution of event processing means in the markup document conversion system according to the embodiment of the present invention.

FIG. 27 is a block diagram showing a configuration of a conversion server including a pre-conversion device in the markup document conversion system according to the embodiment of the present invention.

FIG. 28 is a block diagram showing a configuration of a pre-conversion device in the markup document conversion system according to the embodiment of the present invention.

FIG. 29 is a block diagram showing the configuration of a corrected document conversion device in the markup document conversion system according to the embodiment of the present invention.

FIG. 30 is a diagram showing an example of a BML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 31 is a diagram showing a display example of a BML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 32 is a diagram showing an example of a corrected converted document in the markup document conversion system according to the embodiment of the present invention.

FIG. 33 is a diagram showing an example of a corrected document in the markup document conversion system according to the embodiment of the present invention.

FIG. 34 is a diagram showing an example of a converted CHTML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 35 is a diagram showing an example of a CHTML document after executing the event processing means in the markup document conversion system according to the embodiment of the present invention.

FIG. 36 is an explanatory diagram showing conversion rules of the static format conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 37 is an explanatory diagram showing conversion rules of the dynamic format conversion means in the markup document conversion system according to the embodiment of the present invention.

FIG. 38 is a diagram showing a display example of a converted CHTML document in the markup document conversion system according to the embodiment of the present invention.

FIG. 39 is a diagram showing an example of form data transmitted in the markup document conversion system according to the embodiment of the present invention.

FIG. 40 is an explanatory diagram showing an interface of a bidirectional server communication unit in the markup document conversion system according to the embodiment of the present invention.

[Explanation of symbols]

11 ... conversion source document, 12 ... conversion device, 13 ... browser, 14 ... conversion source document reading means, 17 ... script execution means, 18 ... event conversion means, 19 ...
Markup language conversion means, 22 ... Event processing means, 51 ... Prior conversion device, 53 ... Document editing device, 5
5 ... Corrected document conversion / delivery device, 61 ... Difference reflecting means, 65 ... Difference generating means, 66 ... Bidirectional server communication means.

Claims (15)

[Claims] 1. A markup document conversion method for converting a document described in a markup language including a procedural script language into a document described in a different markup language, wherein the document is described in the different markup language. A markup document conversion method in which a procedural script language included in a markup language of a conversion source is executed by a conversion device on a server that distributes the document when the document is converted into a converted document. 2. The markup language of the conversion source is BML (markup language for broadcasting), and the markup language after conversion is H.
The markup document conversion method according to claim 1, wherein the markup document conversion method is TML (Hypertext Markup Language). 3. The conversion source markup language is BML (broadcast markup language), and the converted markup language is i.
The markup document conversion method according to claim 1, wherein the markup document conversion method is HTML for mode. 4. The markup language of the conversion source is BML (markup language for broadcasting), and the markup language after conversion is J.
The markup document conversion method according to claim 1, wherein the markup document conversion method is HTML for Sky Web. 5. The markup language of the conversion source is BML (markup language for broadcasting), and the markup language after conversion is W.
The markup document conversion method according to claim 1, wherein the markup document conversion method is ML. 6. Included in the markup language of the conversion source
5. The markup document conversion method according to claim 2, wherein a unique event such as an nclick attribute is converted into an HTML form element and an input element which are target conversion markup languages. 7. The o included in the markup language of the conversion source
Unique events such as the nclick attribute are converted to the markup language WML do element, go element, post
The markup document conversion method according to claim 5, wherein conversion is performed into a field element. 8. When converting a unique event into an input element, a script described as an attribute of the unique event with a character that is not used in the id attribute of the input element is set as the value of the name attribute and set by the user. 7. The markup document conversion system according to claim 6, wherein the conversion device side determines the script started by the. 9. When converting a unique event into a postfield attribute, a character described as an attribute of the unique event with a character not used in the id attribute of the input element is set as the value of the name attribute, and the user is set. 8. The markup document conversion method according to claim 7, wherein the script started by is determined on the conversion device side. 10. The conversion device reads a conversion source document and divides it into a script part and a markup part included in the conversion source document, and the conversion source document reading part. Script execution means for reading and executing a script part or a script part extracted from data sent from a user, and event conversion means and markup for converting the markup part into a converted document described in a different markup language. In the language conversion means and the converted document sent to the browser and displayed to the user, when the element for transmitting information from the user is activated, the script part set from the data transmitted from the user is displayed. Take out the script part with the script execution means 10. An event processing means for executing the event, and subsequently executing the event conversion means and the markup language conversion means to update the converted document and send again to the browser. The markup document conversion method described in any of 1. 11. The markup document conversion according to claim 2, wherein the value of the unique event included in the conversion source markup language is replaced with a script that posts form data that specifies that the event has been fired. method. 12. A script-based external device that calls a program that implements an interface for operating an external device / external program in a script language included in the conversion source markup language from a conversion device on a server that distributes a document. 6. The markup document conversion system according to claim 2, wherein the operation of the device / external program is also reproduced. 13. The conversion source markup language is BML, and bidirectional server communication means for implementing a communication interface with a bidirectional server included in a BML document is provided in the conversion device. 13. The markup document conversion method according to claim 12, wherein the operation of the bidirectional function described in the script is reproduced. 14. The conversion device does not automatically convert and distribute the conversion source markup language, but a pre-conversion device generates a correction converted document in advance, and the correction converted document is converted by the document editing device. 14. The conversion result can be corrected manually or by another program by providing a corrected document conversion device that corrects and delivers the corrected document obtained by the correction. Markup document conversion method described in crab. 15. The modified document conversion apparatus has a difference generation means, a difference reflection means, and a script execution means, and stores the content of the modified part generated by the pre-conversion apparatus in the modified document while converting the conversion source. 15. The markup document conversion method according to claim 14, wherein the script included in the document is executed to reproduce the operation of the conversion source document.